Definition Type: ComplexType
Name: TimeOrdinalEraType
Namespace: http://www.opengis.net/gml
Type: gml:DefinitionType
Containing Schema: temporalReferenceSystems.xsd
Abstract
Documentation:
Ordinal temporal reference systems are often hierarchically structured such that an ordinal era at a given level of the hierarchy includes a sequence of shorter, coterminous ordinal eras. This captured using the member/group properties. Note that in this schema, TIme Ordinal Era is patterned on TimeEdge, which is a variation from ISO 19108. This is in order to fulfill the requirements of ordinal reference systems based on eras delimited by named points or nodes, which are common in geology, archeology, etc. This change is subject of a change proposal to ISO
Collapse XSD Schema Diagram:
Drilldown into group in schema temporalreferencesystems_xsd Drilldown into member in schema temporalreferencesystems_xsd Drilldown into extent in schema temporalreferencesystems_xsd Drilldown into end in schema temporalreferencesystems_xsd Drilldown into start in schema temporalreferencesystems_xsd Drilldown into relatedTime in schema temporalreferencesystems_xsd Drilldown into name in schema gmlbase_xsd Drilldown into description in schema gmlbase_xsd Drilldown into metaDataProperty in schema gmlbase_xsd Drilldown into StandardObjectProperties in schema gmlbase_xsd Drilldown into id in schema gmlbase_xsd Drilldown into DefinitionType in schema dictionary_xsdXSD Diagram of TimeOrdinalEraType in schema temporalreferencesystems_xsd (Geography Markup Language)
Collapse XSD Schema Code:
<complexType name="TimeOrdinalEraType">
    <annotation>
        <documentation xml:lang="en">Ordinal temporal reference systems are often hierarchically structured 
      such that an ordinal era at a given level of the hierarchy includes a 
      sequence of shorter, coterminous ordinal eras. This captured using the member/group properties.  
      
      Note that in this schema, TIme Ordinal Era is patterned on TimeEdge, which is a variation from ISO 19108.  
      This is in order to fulfill the requirements of ordinal reference systems based on eras delimited by 
      named points or nodes, which are common in geology, archeology, etc.  
      
      This change is subject of a change proposal to ISO</documentation>
    </annotation>
    <complexContent>
        <extension base="gml:DefinitionType">
            <sequence>
                <element name="relatedTime" type="gml:RelatedTimeType" minOccurs="0" maxOccurs="unbounded" />
                <element name="start" type="gml:TimeNodePropertyType" />
                <element name="end" type="gml:TimeNodePropertyType" />
                <element name="extent" type="gml:TimePeriodPropertyType" minOccurs="0" />
                <element name="member" type="gml:TimeOrdinalEraPropertyType" minOccurs="0" maxOccurs="unbounded">
                    <annotation>
                        <documentation>An Era may be composed of several member Eras. The "member" element implements the association to the Era at the next level down the hierarchy.  "member" follows the standard GML property pattern whereby its (complex) value may be either described fully inline, or may be the target of a link carried on the member element and described fully elsewhere, either in the same document or from another service.</documentation>
                    </annotation>
                </element>
                <element name="group" type="gml:ReferenceType" minOccurs="0">
                    <annotation>
                        <documentation>In a particular Time System, an Era may be a member of a group.  The "group" element implements the back-pointer to the Era at the next level up in the hierarchy. 

If the hierarchy is represented by describing the nested components fully in the their nested position inside "member" elements, then the parent can be easily inferred, so the group property is unnecessary.  

However, if the hierarchy is represented by links carried on the "member" property elements, pointing to Eras described fully elsewhere, then it may be useful for a child (member) era to carry an explicit pointer back to its parent (group) Era.</documentation>
                    </annotation>
                </element>
            </sequence>
        </extension>
    </complexContent>
</complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
metaDataProperty gml:metaDataProperty 0 unbounded
description gml:description 0 (1)
name gml:name 0 unbounded
metaDataProperty gml:metaDataProperty 0 unbounded
description gml:description 0 (1)
name gml:name (1) unbounded
relatedTime gml:relatedTime 0 unbounded
start gml:start (1) (1)
end gml:end (1) (1)
extent gml:extent 0 (1)
member gml:member 0 unbounded
group gml:group 0 (1)
<xs:group> gml:StandardObjectProperties (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
id gml:id Required
Collapse Derivation Tree:
Collapse References:
gml:TimeOrdinalEra