complexType "gml:TimePositionType"
Namespace:
Content:
simple, 3 attributes
Final:
"#all" (blocks all further derivations of this type)
Defined:
globally in temporal.xsd; see XML source
Includes:
definitions of 3 attributes
Used:
XML Representation Summary
<...
   
 = 
string
 = 
anyURI : "#ISO-8601"
 = 
("after" | "before" | "now" | "unknown")
   
>
   
Content: 
{ (date | gYearMonth | gYear) | time | dateTime | anyURI | decimal }
</...>
All Direct / Indirect Based Elements (4):
Known Usage Locations
Annotation
The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108. Values based on calendars and clocks use lexical formats that are based on ISO 8601, as described in XML Schema Part 2:2001. A decimal value may be used with coordinate systems such as GPS time or UNIX time. A URI may be used to provide a reference to some era in an ordinal reference system . In common with many of the components modelled as data types in the ISO 19100 series of International Standards, the corresponding GML component has simple content. However, the content model gml:TimePositionType is defined in several steps. Three XML attributes appear on gml:TimePositionType: A time value shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. Components for describing temporal reference systems are described in 14.4, but it is not required that the reference system be described in this, as the reference may refer to anything that may be indentified with a URI. For time values using a calendar containing more than one era, the (optional) calendarEraName attribute provides the name of the calendar era. Inexact temporal positions may be expressed using the optional indeterminatePosition attribute. This takes a value from an enumeration.
Type Definition Detail
Type Derivation Tree
union of (gml:CalDate | time | dateTime | anyURI | decimal)
  gml:TimePositionUnion (extension)
      gml:TimePositionType
Derivation:
XML Source (see within schema source)
<complexType final="#all" name="TimePositionType">
<annotation>
<documentation>
The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108.
Values based on calendars and clocks use lexical formats that are based on ISO 8601, as described in XML Schema Part 2:2001. A decimal value may be used with coordinate systems such as GPS time or UNIX time. A URI may be used to provide a reference to some era in an ordinal reference system .
In common with many of the components modelled as data types in the ISO 19100 series of International Standards, the corresponding GML component has simple content. However, the content model gml:TimePositionType is defined in several steps.
Three XML attributes appear on gml:TimePositionType:
A time value shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. Components for describing temporal reference systems are described in 14.4, but it is not required that the reference system be described in this, as the reference may refer to anything that may be indentified with a URI.
For time values using a calendar containing more than one era, the (optional) calendarEraName attribute provides the name of the calendar era.
Inexact temporal positions may be expressed using the optional indeterminatePosition attribute. This takes a value from an enumeration.
</documentation>
</annotation>
<simpleContent>
<extension base="gml:TimePositionUnion">
<attribute default="#ISO-8601" name="frame" type="anyURI"/>
<attribute name="calendarEraName" type="string"/>
</extension>
</simpleContent>
</complexType>
Attribute Detail (all declarations; 3/3)
calendarEraName
Type:
string, predefined
Use:
optional
Defined:
locally within (this) gml:TimePositionType complexType
XML Source (see within schema source)
<attribute name="calendarEraName" type="string"/>

frame
Type:
anyURI, predefined
Use:
optional
Default:
"#ISO-8601"
Defined:
locally within (this) gml:TimePositionType complexType
XML Source (see within schema source)
<attribute default="#ISO-8601" name="frame" type="anyURI"/>

indeterminatePosition
Type:
Use:
optional
Defined:
locally within (this) gml:TimePositionType complexType
XML Source (see within schema source)

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/