complexType TimeOrdinalEraType

diagram
namespace	http://www.opengis.net/gml
type	extension of gml:DefinitionType
properties	base  gml:DefinitionType
children	gml:metaDataProperty gml:description gml:name gml:relatedTime gml:start gml:end gml:extent gml:member gml:group
used by	element  TimeOrdinalEra
attributes	Name   Type   Use   Default   Fixed   annotation id required         documentation Database handle for the object.  It is of XML type ID, so is constrained to be unique in the XML document within which it occurs.  An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.  This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
annotation	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
source	<xs:complexType name="TimeOrdinalEraType">   <xs:annotation>     <xs: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</xs:documentation>   </xs:annotation>   <xs:complexContent>     <xs:extension base="gml:DefinitionType">       <xs:sequence>         <xs:element name="relatedTime" type="gml:RelatedTimeType" minOccurs="0" maxOccurs="unbounded"/>         <xs:element name="start" type="gml:TimeNodePropertyType"/>         <xs:element name="end" type="gml:TimeNodePropertyType"/>         <xs:element name="extent" type="gml:TimePeriodPropertyType" minOccurs="0"/>         <xs:element name="member" type="gml:TimeOrdinalEraPropertyType" minOccurs="0" maxOccurs="unbounded">           <xs:annotation>             <xs: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.</xs:documentation>           </xs:annotation>         </xs:element>         <xs:element name="group" type="gml:ReferenceType" minOccurs="0">           <xs:annotation>             <xs: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.</xs:documentation>           </xs:annotation>         </xs:element>       </xs:sequence>     </xs:extension>   </xs:complexContent> </xs:complexType>

element TimeOrdinalEraType/relatedTime

diagram
namespace	http://www.opengis.net/gml
type	gml:RelatedTimeType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	gml:_TimePrimitive
attributes	Name   Type   Use   Default   Fixed   annotation type       simple   href          role          arcrole          title          show          actuate          remoteSchema optional         documentation Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the XML Schema Section 4.14 Referencing Schemas from Elsewhere. relativePosition derived by: xs:string
source	<xs:element name="relatedTime" type="gml:RelatedTimeType" minOccurs="0" maxOccurs="unbounded"/>

element TimeOrdinalEraType/start

diagram
namespace	http://www.opengis.net/gml
type	gml:TimeNodePropertyType
properties	isRef  0 content  complex
children	gml:TimeNode
attributes	Name   Type   Use   Default   Fixed   annotation type       simple   href          role          arcrole          title          show          actuate          remoteSchema optional         documentation Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the XML Schema Section 4.14 Referencing Schemas from Elsewhere.
source	<xs:element name="start" type="gml:TimeNodePropertyType"/>

element TimeOrdinalEraType/end

diagram
namespace	http://www.opengis.net/gml
type	gml:TimeNodePropertyType
properties	isRef  0 content  complex
children	gml:TimeNode
attributes	Name   Type   Use   Default   Fixed   annotation type       simple   href          role          arcrole          title          show          actuate          remoteSchema optional         documentation Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the XML Schema Section 4.14 Referencing Schemas from Elsewhere.
source	<xs:element name="end" type="gml:TimeNodePropertyType"/>

element TimeOrdinalEraType/extent

diagram
namespace	http://www.opengis.net/gml
type	gml:TimePeriodPropertyType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	gml:TimePeriod
attributes	Name   Type   Use   Default   Fixed   annotation type       simple   href          role          arcrole          title          show          actuate          remoteSchema optional         documentation Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the XML Schema Section 4.14 Referencing Schemas from Elsewhere.
source	<xs:element name="extent" type="gml:TimePeriodPropertyType" minOccurs="0"/>

element TimeOrdinalEraType/member

diagram
namespace	http://www.opengis.net/gml
type	gml:TimeOrdinalEraPropertyType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	gml:TimeOrdinalEra
used by	complexType  BagType
attributes	Name   Type   Use   Default   Fixed   annotation type       simple   href          role          arcrole          title          show          actuate          remoteSchema optional         documentation Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the XML Schema Section 4.14 Referencing Schemas from Elsewhere.
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.
source	<xs:element name="member" type="gml:TimeOrdinalEraPropertyType" minOccurs="0" maxOccurs="unbounded">   <xs:annotation>     <xs: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.</xs:documentation>   </xs:annotation> </xs:element>

element TimeOrdinalEraType/group

diagram
namespace	http://www.opengis.net/gml
type	gml:ReferenceType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
attributes	Name   Type   Use   Default   Fixed   annotation type       simple   href          role          arcrole          title          show          actuate          remoteSchema optional         documentation Reference to an XML Schema fragment that specifies the content model of the propertys value. This is in conformance with the XML Schema Section 4.14 Referencing Schemas from Elsewhere.
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.
source	<xs:element name="group" type="gml:ReferenceType" minOccurs="0">   <xs:annotation>     <xs: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.</xs:documentation>   </xs:annotation> </xs:element>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy