Copyright © 2011 Open Geospatial Consortium
25 not contains{codeListValuePattern}, and document{codeListValuePattern}
or contains{codeListValuePattern}, and documentsubstring- before{codeListValuePattern},idsubstring-after{codeListValuePattern},
In addition, we can assert that the remote resource has the correct element based on its representation.
For applicationgml+xml;version=3.2 the default we expect a gml:Definition: not contains{codeListValuePattern}, and document{codeListValuePattern}
gml:Definition or contains{codeListValuePattern}, and documentsubstring- before{codeListValuePattern},idsubstring-after{codeListValuePattern},
[local-name=Definiton and namespace-uri=http:www.opengis.netgml3.2]
For applicationrdf+xml we expect a skos:Concept see the OWS-8 Semantic Mediation ER:
not contains{codeListValuePattern}, and document{codeListValuePattern} skos:Concept or contains{codeListValuePattern}, and documentsubstring-
before{codeListValuePattern},idsubstring-after{codeListValuePattern}, [local-name=Concept and namespace-uri=
http:www.w3.org200402skoscore]
6.4.6.3 Target encding: ISOTS 19139
The Schematron assertions for code list values in properties encoded according to ISOTS 19139 is similar to the GML 3.2 encoding. The differences are described in 6.4.2.
To verify the codeSpace attribute, the following assertion is added to the Schematron schema in the context of the property, if the tagged value {codeList} has been provided:
codeList={codeList} To test the existence of the code list value the following assertion is added to the
Schematron schema in the context of the property. In {codeListValuePattern} we replace {codeList} by {codeList} and {value} by codeListValue:
not contains{codeListValuePattern}, and document{codeListValuePattern} or contains{codeListValuePattern}, and documentsubstring-
before{codeListValuePattern},idsubstring-after{codeListValuePattern},
In addition, we can assert that the remote resource has the correct element based on its representation.
For applicationgml+xml;version=3.2 the default we expect a gml:Definition: not contains{codeListValuePattern}, and document{codeListValuePattern}
gml:Definition or contains{codeListValuePattern}, and documentsubstring-
26
Copyright © 2011 Open Geospatial Consortium
before{codeListValuePattern},idsubstring-after{codeListValuePattern}, [local-name=Definiton and namespace-uri=http:www.opengis.netgml3.2]
For applicationrdf+xml we expect a skos:Concept see the OWS-8 Semantic Mediation ER:
not contains{codeListValuePattern}, and document{codeListValuePattern} skos:Concept or contains{codeListValuePattern}, and documentsubstring-
before{codeListValuePattern},idsubstring-after{codeListValuePattern}, [local-name=Concept and namespace-uri=
http:www.w3.org200402skoscore]
6.4.7 Additional assertions on units of measure references
If the schema package has the tagged value uomResourceURI {uomResourceURI} and an attribute has the tagged values
Case 1: physicalQuantity {physicalQuantity} and recommendedMeasure {recommendedMeasure}, or
Case 2: noncomparableMeasure {noncomparableMeasure} then the following assertion is added to the Schematron schema in the context of the
property. NOTE All assertions assume the default values for the tagged values
uomResourceValuePattern and uomResourceRepresentation listed in Table 2. If these differ, the assertions have to be adapted accordingly.
Case 1: uom={uomResourceURI}{physicalQuantity}{recommendedMeasure} Case 2: uom={uomResourceURI}noncomparable{noncomparableMeasure}
To test the existence of the unit the following assertion is added to the Schematron schema in the context of the property:
Case 12: documentuom In addition, we can assert that the remote resource has the correct element based on its
representation. I.e., for a GML representation we expect a gml:BaseUnit, gml:Derived or gml:ConventionalUnit:
Case 12: Agml:BaseUnit|Agml:Derived|Agml:ConventionalUnit with a let expression to set A=documentuom
6.5 Conclusions from testing the improvements
The planned improvements have been specified, implemented and tested.
