xsd-xml-rules : Public <<RequirementsClass>> Package
Created: 9/04/2015 1:29:21 PM
Modified: 13/05/2015 7:33:45 PM
Project:
Advanced:
This requirements class contains a set of general rules applicable to the XML encoding.
Constraint Type Status
http://www.w3.org/TR/xmlschema-2 Invariant Approved
Details:
 
http://standards.iso.org/iso/8601/2004/4 Invariant Approved
Details:
 
http://www.opengis.net/doc/IS/GML/3.2#clause-2.4 Invariant Approved
Details:
 
http://www.opengis.net/spec/GML/3.3/req/definitions Invariant Approved
Details:
 
http://www.opengis.net/spec/SWE/2.0/req/xsd-simple-components Invariant Approved
Details:
 
Scenario Type
/req/xsd-xml-rules/iso8601-time Basic Path
Details:
All date-time elements shall be encoded using ISO8601 extended time format.
Steps:
1. Verify that all time instants are valid according to the XML Schema implementation of ISO8601.
/req/xsd-xml-rules/time-zone Alternate
Details:
The value of each time element (defined in the TimeValuePairType ‘time’ element) shall include a time zone definition using a signed 4 digit character or a ‘Z’ to represent Zulu or Greenwich Mean Time (GMT). This is defined by the following regular expression: <br /></p><p>(Z|[+-]HH:MM)<br /></p>
Steps:
1. Verify that all time instants include a time zone specifier.
/req/xsd-xml-rules/unit-of-measure Alternate
Details:
All units of measure shall use the appropriate code from the The Unified Code for Units of Measure (UCUM) code system. The unit of measure shall be identified by encoding the UCUM code<sup>1</sup> in the ‘code’ attribute of the tsml:uom element. -------------------------<br /></p><p><sup>1</sup> The UCUM base codes are available in XML form here: <br /></p><p><a href="file://http://aurora.regenstrief.org/~ucum/ucum-essence.xml"><font color="#0000ff"><u>http://unitsofmeasure.org/ucum-essence.xml</u></font></a>. <br /></p>
Steps:
1. Verify that all time units are specified using the UCUM units system.
/req/xsd-xml-rules/swe-types Alternate
Details:
When using the SWE Common types, the following elements shall not be used: swe:quality (<i>AbstractSimpleComponentType)</i>, swe:nilValues (<i>AbstractSimpleComponentType)</i>, swe:constraint (<i>QuantityType</i>, <i>QuantityRangeType</i>, <i>CategoryType</i>). The attributes ‘<i>optional’</i> and ‘<i>updatable’</i> from the base type ‘<i>AbstractDataComponent’ </i>shall also not be used.
Steps:
1. Ensure that only applicable SWE types are used. Some SWE types are related specifically to the SWE encoding style, which is not used.

Verify that following SWE elements are not used in the encoding:
- swe:quality(AbstractSimpleComponentType)
- swe:nilValues (AbstractSimpleComponentType)
- swe:constraint (QuantityType, QuantityRangeType, CategoryType)

Verify the following SWE attributes are not used:
- ‘optional’ and ‘updatable’ from the base type ‘AbstractDataComponent’
/rec/xsd-xml-rules/xlink-title Alternate
Details:
If an xlink:href is used to reference a controlled vocabulary item, the element should encode the xlink:title attribute with a text description of the referenced item. 
Steps:
1. Verify that an element using a xlink:href to encode reference a controlled vocabulary item also encodes a xlink:title attribute with a text description of the referenced item.
/rec/xsd-xml-rules/vocabulary-references Alternate
Details:
When specifying references to vocabulary (code) items using an xlink:href, a resolvable HTTP URL should be used which, when resolved, should provide suitable description of the concept being referenced. 
/rec/xsd-xml-rules/xlink-valid-local-reference Alternate
Details:
If an xlink:href is a local reference then the referenced element must exist.
Steps:
1. Verfity that the element referenced by a local xlink:href reference exists.