Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OMXML: Add OGC Name for SWE*Observations #15

Open
KathiSchleidt opened this issue Aug 18, 2019 · 10 comments
Open

OMXML: Add OGC Name for SWE*Observations #15

KathiSchleidt opened this issue Aug 18, 2019 · 10 comments
Labels
missing/incomplete content OGC CRP Originates from an OGC Standards Tracker change request proposal xml XML encoding related

Comments

@KathiSchleidt
Copy link
Contributor

Arne Broering:
Mappings of SWE*Observation types to OGC names and result types are missing in Table 6.
Add OGC names and result types in Table 6 for SWE Array Observation and SWE Scalar Observation.
Pertains to section 6.4

@ilkkarinne
Copy link
Contributor

Which document is this issue referring to?

@KathiSchleidt
Copy link
Contributor Author

@ilkkarinne ilkkarinne added missing/incomplete content OGC CRP Originates from an OGC Standards Tracker change request proposal xml XML encoding related labels Aug 24, 2019
@ilkkarinne
Copy link
Contributor

This is related to whether the 19156 should have additional specialized observation types for Array and Scalar Observations, see #27

@ilkkarinne
Copy link
Contributor

Actually, I think the original issue is about the need to have OGC Names (http://www.opengis.net/def/observationType/*) defined and listed in the O&M XML Implementation (OGC 10-025r1). The current Table 6 only contains the mapping from the 19156 specialized observations type names to the OGC Names and result property content types to be used for each of them. There should also be mappings from SWE Common Observation types "ScalarObservation" and "ArrayObservation" to OGC def names in the revised version of the OGC O&M XML Implementation, with the result types as defined in Requirements classes http://www.opengis.net/spec/OMXML/2.0/req/SWEScalarObservation and http://www.opengis.net/spec/OMXML/2.0/req/SWEArrayObservation

@KathiSchleidt
Copy link
Contributor Author

I checked through O&M, couldn't find any mention of these SWE types within the O&M text, nor could I find them defined within SWE.
I now contacted Arne Bröring as the reporter - he also can't remember what the real issue was, is OK with us ignoring it

@ilkkarinne
Copy link
Contributor

I pretty sure this issue is about the Table 6 on the page 12 of the O&M XML Implementation (10-025r1, http://portal.opengeospatial.org/files/?artifact_id=41510) only, so we can handle that when revising that standard.

@dr-shorthair
Copy link

Indeed - they only relate to the XML implementation. SWE Common was not judged to be an abstract model, merely an implementation artefact.

@KathiSchleidt
Copy link
Contributor Author

Unclear requirement, not really relevant (also according to the reporter), thus closed

@dr-shorthair
Copy link

Arne is (or was) with 52N who are responsible for the main implementation of SOS and thus have a stake in the current state.

@KathiSchleidt
Copy link
Contributor Author

OK, while Arne has moved on (no longer at 52°N), think I finally figured this one (as well as an error we made in INSPIRE due to confusion between O&M V1 & V2! ;) )
In the XSD V2 soft typing was introduced, at the same time we continued to derive new observation types in UML&XSD instead of just providing this info in the type attribute with a link to an entry from http://www.opengis.net/def/observationType/OGC-OM/2.0/
While the list provided covers all basic Observation Result types also covered in the UML, it does not account for the provision of a SWE Result type such as swe:DataArray
Fear this one must be reopened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
missing/incomplete content OGC CRP Originates from an OGC Standards Tracker change request proposal xml XML encoding related
Projects
None yet
Development

No branches or pull requests

3 participants