XML Schema "temporalReferenceSystems.xsd"
Target Namespace:
Version:
3.2.1.2
Defined Components:
elements (7 global + 20 local), complexTypes (11)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://schemas.opengis.net/gml/3.2.1/temporalReferenceSystems.xsd; see XML source
Includes Schemas (3):
Included in Schemas (1):
Annotation
See ISO/DIS 19136 15.5. A value in the time domain is measured relative to a temporal reference system. Common types of reference systems include calendars, ordinal temporal reference systems, and temporal coordinate systems (time elapsed since some epoch). The primary temporal reference system for use with geographic information is the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC), but special applications may entail the use of alternative reference systems. The Julian day numbering system is a temporal coordinate system that has an origin earlier than any known calendar, at noon on 1 January 4713 BC in the Julian proleptic calendar, and is useful in transformations between dates in different calendars. In GML seven concrete elements are used to describe temporal reference systems: gml:TimeReferenceSystem, gml:TimeCoordinateSystem, gml:TimeCalendar, gml:TimeCalendarEra, gml:TimeClock, gml:TimeOrdinalReferenceSystem, and gml:TimeOrdinalEra. GML is an OGC Standard. Copyright (c) 2007,2010 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
All Element Summary (local elements unified by type)
Type:
Content:
complex, 10 attributes, 1 element
Defined:
Type:
Content:
complex, 10 attributes, 1 element
Defined:
locally within gml:TimeClockType complexType; see XML source
gml:domainOfValidity (type string)
Type:
string
Content:
simple
Defined:
Type:
Content:
complex, 10 attributes, 1 element
Defined:
locally at 2 locations
Type:
Content:
complex, 10 attributes, 1 element
Defined:
Type:
Content:
complex, 10 attributes, 1 element
Defined:
locally at 2 locations
Type:
Content:
empty, 10 attributes
Defined:
locally within gml:TimeOrdinalEraType complexType; see XML source
Type:
Content:
simple, 3 attributes
Defined:
Type:
decimal
Content:
simple
Defined:
Type:
Content:
complex, 10 attributes, 1 element
Defined:
locally within gml:TimeOrdinalEraType complexType; see XML source
Type:
Content:
complex, 10 attributes, 1 element
Defined:
Type:
Content:
simple, 3 attributes
Defined:
Type:
Content:
simple
Defined:
Type:
Content:
simple, 9 attributes
Defined:
locally at 2 locations
Type:
Content:
complex, 10 attributes, 1 element
Defined:
locally within gml:TimeCalendarType complexType; see XML source
Type:
time
Content:
simple
Defined:
locally within gml:TimeClockType complexType; see XML source
Type:
Content:
complex, 11 attributes, 1 element
Defined:
locally at 2 locations
Type:
Content:
complex, 10 attributes, 1 element
Defined:
locally at 2 locations
A calendar is a discrete temporal reference system that provides a basis for defining temporal position to a resolution of one day. gml:TimeCalendar adds one property to those inherited from gml:TimeReferenceSystem.
Type:
Content:
complex, 1 attribute, 8 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
gml:TimeCalendarEra inherits basic properties from gml:DefinitionType and has the following additional properties: - gml:referenceEvent is the name or description of a mythical or historic event which fixes the position of the base scale of the calendar era.
Type:
Content:
complex, 1 attribute, 10 elements
Defined:
globally; see XML source
Used:
A clock provides a basis for defining temporal position within a day.
Type:
Content:
complex, 1 attribute, 11 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
A temporal coordinate system shall be based on a continuous interval scale defined in terms of a single time interval.
Type:
Content:
complex, 1 attribute, 10 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
never
Its content model follows the pattern of gml:TimeEdge, inheriting standard properties from gml:DefinitionType, and adding gml:start, gml:end and gml:extent properties, a set of gml:member properties which indicate ordered gml:TimeOrdinalEra elements, and a gml:group property which points to the parent era.
Type:
Content:
complex, 1 attribute, 12 elements
Defined:
globally; see XML source
Used:
In some applications of geographic information — such as geology and archaeology — relative position in time is known more precisely than absolute time or duration.
Type:
Content:
complex, 1 attribute, 8 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
never
A reference system is characterized in terms of its domain of validity: the spatial and temporal extent over which it is applicable.
Type:
Content:
complex, 1 attribute, 7 elements
Subst.Gr:
may substitute for elements: gml:Definition, gml:AbstractGML, gml:AbstractObject; may be substituted with 4 elements
Defined:
globally; see XML source
Used:
Type:
time
Content:
simple
Defined:
locally within gml:TimeClockType complexType; see XML source
Complex Type Summary
gml:TimeCalendarEraPropertyType provides for associating a gml:TimeCalendarEra with an object.
Content:
complex, 10 attributes, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 1 attribute, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
gml:TimeCalendarPropertyType provides for associating a gml:TimeCalendar with an object.
Content:
complex, 10 attributes, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 1 attribute, 8 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
gml:TimeClockPropertyType provides for associating a gml:TimeClock with an object.
Content:
complex, 10 attributes, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
never
Content:
complex, 1 attribute, 11 elements
Final:
"#all" (blocks all further derivations of this type)
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Content:
complex, 1 attribute, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
gml:TimeOrdinalEraPropertyType provides for associating a gml:TimeOrdinalEra with an object.
Content:
complex, 10 attributes, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 1 attribute, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Content:
complex, 1 attribute, 8 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 1 attribute, 7 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<schema elementFormDefault="qualified" targetNamespace="http://www.opengis.net/gml/3.2" version="3.2.1.2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml/3.2">
<annotation>
<appinfo source="urn:x-ogc:specification:gml:schema-xsd:temporalReferenceSystems:3.2.1">temporalReferenceSystems.xsd</appinfo>
<documentation>
See ISO/DIS 19136 15.5.
A value in the time domain is measured relative to a temporal reference system. Common types of reference systems include calendars, ordinal temporal reference systems, and temporal coordinate systems (time elapsed since some epoch). The primary temporal reference system for use with geographic information is the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC), but special applications may entail the use of alternative reference systems. The Julian day numbering system is a temporal coordinate system that has an origin earlier than any known calendar, at noon on 1 January 4713 BC in the Julian proleptic calendar, and is useful in transformations between dates in different calendars.
In GML seven concrete elements are used to describe temporal reference systems: gml:TimeReferenceSystem, gml:TimeCoordinateSystem, gml:TimeCalendar, gml:TimeCalendarEra, gml:TimeClock, gml:TimeOrdinalReferenceSystem, and gml:TimeOrdinalEra.

GML is an OGC Standard.
Copyright (c) 2007,2010 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
</documentation>
</annotation>
<include schemaLocation="gml.xsd"/>
<include schemaLocation="temporalTopology.xsd"/>
<include schemaLocation="dictionary.xsd"/>
<element name="TimeReferenceSystem" substitutionGroup="gml:Definition" type="gml:TimeReferenceSystemType">
<annotation>
<documentation>
A reference system is characterized in terms of its domain of validity: the spatial and temporal extent over which it is applicable. The basic GML element for temporal reference systems is gml:TimeReferenceSystem. Its content model extends gml:DefinitionType with one additional property, gml:domainOfValidity.
</documentation>
</annotation>
</element>
<complexType name="TimeReferenceSystemType">
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="domainOfValidity" type="string"/>
</sequence>
</extension>
</complexContent>
</complexType>
<annotation>
<documentation>
A temporal coordinate system shall be based on a continuous interval scale defined in terms of a single time interval.
The differences to ISO 19108 TM_CoordinateSystem are:
- the origin is specified either using the property gml:originPosition whose value is a direct time position, or using the property gml:origin whose model is gml:TimeInstantPropertyType; this permits more flexibility in representation and also supports referring to a value fixed elsewhere;
- the interval uses gml:TimeIntervalLengthType.
</documentation>
</annotation>
</element>
<complexType name="TimeCoordinateSystemType">
<complexContent>
<extension base="gml:TimeReferenceSystemType">
<sequence>
<choice>
<element name="originPosition" type="gml:TimePositionType"/>
<element name="origin" type="gml:TimeInstantPropertyType"/>
</choice>
<element name="interval" type="gml:TimeIntervalLengthType"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="TimeCalendar" substitutionGroup="gml:TimeReferenceSystem" type="gml:TimeCalendarType">
<annotation>
<documentation>
A calendar is a discrete temporal reference system that provides a basis for defining temporal position to a resolution of one day.
gml:TimeCalendar adds one property to those inherited from gml:TimeReferenceSystem. A gml:referenceFrame provides a link to a gml:TimeCalendarEra that it uses. A gml:TimeCalendar may reference more than one calendar era.
The referenceFrame element follows the standard GML property model, allowing the association to be instantiated either using an inline description using the gml:TimeCalendarEra element, or a link to a gml:TimeCalendarEra which is explicit elsewhere.
</documentation>
</annotation>
</element>
<complexType name="TimeCalendarType">
<complexContent>
<extension base="gml:TimeReferenceSystemType">
<sequence>
<element maxOccurs="unbounded" name="referenceFrame" type="gml:TimeCalendarEraPropertyType"/>
</sequence>
</extension>
</complexContent>
</complexType>
<annotation>
<documentation>
gml:TimeCalendarEra inherits basic properties from gml:DefinitionType and has the following additional properties:
- gml:referenceEvent is the name or description of a mythical or historic event which fixes the position of the base scale of the calendar era. This is given as text or using a link to description held elsewhere.
- gml:referenceDate specifies the date of the referenceEvent expressed as a date in the given calendar. In most calendars, this date is the origin (i.e., the first day) of the scale, but this is not always true.
- gml:julianReference specifies the Julian date that corresponds to the reference date. The Julian day number is an integer value; the Julian date is a decimal value that allows greater resolution. Transforming calendar dates to and from Julian dates provides a relatively simple basis for transforming dates from one calendar to another.
- gml:epochOfUse is the period for which the calendar era was used as a basis for dating.
</documentation>
</annotation>
</element>
<complexType name="TimeCalendarEraType">
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType"/>
<element name="referenceDate" type="gml:CalDate"/>
<element name="julianReference" type="decimal"/>
<element name="epochOfUse" type="gml:TimePeriodPropertyType"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="TimeCalendarPropertyType">
<annotation>
<documentation>
gml:TimeCalendarPropertyType provides for associating a gml:TimeCalendar with an object.
</documentation>
</annotation>
<sequence minOccurs="0">
<element ref="gml:TimeCalendar"/>
</sequence>
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<complexType name="TimeCalendarEraPropertyType">
<annotation>
<documentation>
gml:TimeCalendarEraPropertyType provides for associating a gml:TimeCalendarEra with an object.
</documentation>
</annotation>
<sequence minOccurs="0">
<element ref="gml:TimeCalendarEra"/>
</sequence>
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<element name="TimeClock" substitutionGroup="gml:TimeReferenceSystem" type="gml:TimeClockType">
<annotation>
<documentation>
A clock provides a basis for defining temporal position within a day. A clock shall be used with a calendar in order to provide a complete description of a temporal position within a specific day.
gml:TimeClock adds the following properties to those inherited from gml:TimeReferenceSystemType:
- gml:referenceEvent is the name or description of an event, such as solar noon or sunrise, which fixes the position of the base scale of the clock.
- gml:referenceTime specifies the time of day associated with the reference event expressed as a time of day in the given clock. The reference time is usually the origin of the clock scale.
- gml:utcReference specifies the 24 hour local or UTC time that corresponds to the reference time.
- gml:dateBasis contains or references the calendars that use this clock.
</documentation>
</annotation>
</element>
<complexType final="#all" name="TimeClockType">
<complexContent>
<extension base="gml:TimeReferenceSystemType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType"/>
<element name="referenceTime" type="time"/>
<element name="utcReference" type="time"/>
<element maxOccurs="unbounded" minOccurs="0" name="dateBasis" type="gml:TimeCalendarPropertyType"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="TimeClockPropertyType">
<annotation>
<documentation>
gml:TimeClockPropertyType provides for associating a gml:TimeClock with an object.
</documentation>
</annotation>
<sequence minOccurs="0">
<element ref="gml:TimeClock"/>
</sequence>
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<annotation>
<documentation>
In some applications of geographic information &#8212; such as geology and archaeology &#8212; relative position in time is known more precisely than absolute time or duration. The order of events in time can be well established, but the magnitude of the intervals between them cannot be accurately determined; in such cases, the use of an ordinal temporal reference system is appropriate. An ordinal temporal reference system is composed of a sequence of named coterminous eras, which may in turn be composed of sequences of member eras at a finer scale, giving the whole a hierarchical structure of eras of verying resolution.
An ordinal temporal reference system whose component eras are not further subdivided is effectively a temporal topological complex constrained to be a linear graph. An ordinal temporal reference system some or all of whose component eras are subdivided is effectively a temporal topological complex with the constraint that parallel branches may only be constructed in pairs where one is a single temporal ordinal era and the other is a sequence of temporal ordinal eras that are called "members" of the "group". This constraint means that within a single temporal ordinal reference system, the relative position of all temporal ordinal eras is unambiguous.
The positions of the beginning and end of a given era may calibrate the relative time scale.
gml:TimeOrdinalReferenceSystem adds one or more gml:component properties to the generic temporal reference system model.
</documentation>
</annotation>
</element>
<complexType name="TimeOrdinalReferenceSystemType">
<complexContent>
<extension base="gml:TimeReferenceSystemType">
<sequence>
<element maxOccurs="unbounded" name="component" type="gml:TimeOrdinalEraPropertyType"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="TimeOrdinalEra" type="gml:TimeOrdinalEraType">
<annotation>
<documentation>
Its content model follows the pattern of gml:TimeEdge, inheriting standard properties from gml:DefinitionType, and adding gml:start, gml:end and gml:extent properties, a set of gml:member properties which indicate ordered gml:TimeOrdinalEra elements, and a gml:group property which points to the parent era.
The recursive inclusion of gml:TimeOrdinalEra elements allow the construction of an arbitrary depth hierarchical ordinal reference schema, such that an ordinal era at a given level of the hierarchy includes a sequence of shorter, coterminous ordinal eras.
</documentation>
</annotation>
</element>
<complexType name="TimeOrdinalEraType">
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element maxOccurs="unbounded" minOccurs="0" name="relatedTime" type="gml:RelatedTimeType"/>
<element minOccurs="0" name="start" type="gml:TimeNodePropertyType"/>
<element minOccurs="0" name="end" type="gml:TimeNodePropertyType"/>
<element minOccurs="0" name="extent" type="gml:TimePeriodPropertyType"/>
<element maxOccurs="unbounded" minOccurs="0" name="member" type="gml:TimeOrdinalEraPropertyType"/>
<element minOccurs="0" name="group" type="gml:ReferenceType"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="TimeOrdinalEraPropertyType">
<annotation>
<documentation>
gml:TimeOrdinalEraPropertyType provides for associating a gml:TimeOrdinalEra with an object.
</documentation>
</annotation>
<sequence minOccurs="0">
<element ref="gml:TimeOrdinalEra"/>
</sequence>
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
</schema>

This XML schema documentation has been generated with DocFlex/XML 1.11 using DocFlex/XML XSDDoc 2.8.3 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/