Geo-EOP
view release on metacpan or search on metacpan
lib/Geo/EOP/xsd/eop1.1/gmlSubset.xsd view on Meta::CPAN
<group ref="gml:timeLength" minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- ================================================= -->
<complexType name="AbstractTimeGeometricPrimitiveType" abstract="true">
<annotation>
<documentation xml:lang="en">The abstract supertype for temporal geometric primitives.
A temporal geometry must be associated with a temporal reference system via URI.
The Gregorian calendar with UTC is the default reference system, following ISO
8601. Other reference systems in common use include the GPS calendar and the
Julian calendar.</documentation>
</annotation>
<complexContent>
<extension base="gml:AbstractTimePrimitiveType">
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
</extension>
</complexContent>
</complexType>
<!-- ================================================= -->
<complexType name="TimePositionType" final="#all">
<annotation>
<documentation xml:lang="en">Direct representation of a temporal position.
Indeterminate time values are also allowed, as described in ISO 19108. The indeterminatePosition
attribute can be used alone or it can qualify a specific value for temporal position (e.g. before
2002-12, after 1019624400).
For time values that identify position within a calendar, the calendarEraName attribute provides
the name of the calendar era to which the date is referenced (e.g. the Meiji era of the Japanese calendar).</documentation>
</annotation>
<simpleContent>
<extension base="gml:TimePositionUnion">
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
<attribute name="calendarEraName" type="string" use="optional"/>
<attribute name="indeterminatePosition" type="gml:TimeIndeterminateValueType" use="optional"/>
</extension>
</simpleContent>
</complexType>
<!-- ================================================= -->
<simpleType name="TimePositionUnion">
<annotation>
<documentation xml:lang="en">The ISO 19108:2002 hierarchy of subtypes for temporal position are collapsed
by defining a union of XML Schema simple types for indicating temporal position relative
to a specific reference system.
Dates and dateTime may be indicated with varying degrees of precision.
dateTime by itself does not allow right-truncation, except for fractions of seconds.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
An ordinal position may be referenced via URI identifying the definition of an ordinal era.
A time coordinate value is indicated as a decimal (e.g. UNIX time, GPS calendar).</documentation>
</annotation>
<union memberTypes="gml:CalDate time dateTime anyURI decimal"/>
</simpleType>
<!-- ================================================= -->
<simpleType name="CalDate">
<annotation>
<documentation xml:lang="en">Calendar dates may be indicated with varying degrees of precision,
using year, year-month, date.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
time is used for a position that recurs daily (see clause 5.4.4.2 of ISO 19108:2002).</documentation>
</annotation>
<union memberTypes="date gYearMonth gYear"/>
</simpleType>
<!-- ================================================= -->
<!-- ================================================= -->
<!-- ================================================= -->
<!-- ================================================= -->
lib/Geo/EOP/xsd/eop1.2.1/gmlSubset.xsd view on Meta::CPAN
</xsd:choice>
<xsd:group minOccurs="0" ref="gml:timeLength" />
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="AbstractTimeGeometricPrimitiveType" abstract="true">
<xsd:annotation>
<xsd:documentation xml:lang="en">The abstract supertype for temporal geometric primitives.
A temporal geometry must be associated with a temporal reference system via URI.
The Gregorian calendar with UTC is the default reference system, following ISO
8601. Other reference systems in common use include the GPS calendar and the
Julian calendar.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent mixed="false">
<xsd:extension base="gml:AbstractTimePrimitiveType">
<xsd:attribute default="#ISO-8601" name="frame" type="xsd:anyURI" use="optional" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TimePositionType" final="#all">
<xsd:annotation>
<xsd:documentation xml:lang="en">Direct representation of a temporal position.
Indeterminate time values are also allowed, as described in ISO 19108. The indeterminatePosition
attribute can be used alone or it can qualify a specific value for temporal position (e.g. before
2002-12, after 1019624400).
For time values that identify position within a calendar, the calendarEraName attribute provides
the name of the calendar era to which the date is referenced (e.g. the Meiji era of the Japanese calendar).</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="gml:TimePositionUnion">
<xsd:attribute default="#ISO-8601" name="frame" type="xsd:anyURI" use="optional" />
<xsd:attribute name="calendarEraName" type="xsd:string" use="optional" />
<xsd:attribute name="indeterminatePosition" type="gml:TimeIndeterminateValueType" use="optional" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="TimePositionUnion">
<xsd:annotation>
<xsd:documentation xml:lang="en">The ISO 19108:2002 hierarchy of subtypes for temporal position are collapsed
by defining a union of XML Schema simple types for indicating temporal position relative
to a specific reference system.
Dates and dateTime may be indicated with varying degrees of precision.
dateTime by itself does not allow right-truncation, except for fractions of seconds.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
An ordinal position may be referenced via URI identifying the definition of an ordinal era.
A time coordinate value is indicated as a decimal (e.g. UNIX time, GPS calendar).</xsd:documentation>
</xsd:annotation>
<xsd:union memberTypes="gml:CalDate xsd:time xsd:dateTime xsd:anyURI xsd:decimal" />
</xsd:simpleType>
<xsd:simpleType name="CalDate">
<xsd:annotation>
<xsd:documentation xml:lang="en">Calendar dates may be indicated with varying degrees of precision,
using year, year-month, date.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
time is used for a position that recurs daily (see clause 5.4.4.2 of ISO 19108:2002).</xsd:documentation>
</xsd:annotation>
<xsd:union memberTypes="xsd:date xsd:gYearMonth xsd:gYear" />
</xsd:simpleType>
<xsd:simpleType name="TimeIndeterminateValueType">
<xsd:annotation>
<xsd:documentation xml:lang="en">This enumerated data type specifies values for indeterminate positions.</xsd:documentation>
</xsd:annotation>
lib/Geo/EOP/xsd/hma1.0/gmlSubset.xsd view on Meta::CPAN
<group ref="gml:timeLength" minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- ================================================= -->
<complexType name="AbstractTimeGeometricPrimitiveType" abstract="true">
<annotation>
<documentation xml:lang="en">The abstract supertype for temporal geometric primitives.
A temporal geometry must be associated with a temporal reference system via URI.
The Gregorian calendar with UTC is the default reference system, following ISO
8601. Other reference systems in common use include the GPS calendar and the
Julian calendar.</documentation>
</annotation>
<complexContent>
<extension base="gml:AbstractTimePrimitiveType">
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
</extension>
</complexContent>
</complexType>
<!-- ================================================= -->
<complexType name="TimePositionType" final="#all">
<annotation>
<documentation xml:lang="en">Direct representation of a temporal position.
Indeterminate time values are also allowed, as described in ISO 19108. The indeterminatePosition
attribute can be used alone or it can qualify a specific value for temporal position (e.g. before
2002-12, after 1019624400).
For time values that identify position within a calendar, the calendarEraName attribute provides
the name of the calendar era to which the date is referenced (e.g. the Meiji era of the Japanese calendar).</documentation>
</annotation>
<simpleContent>
<extension base="gml:TimePositionUnion">
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
<attribute name="calendarEraName" type="string" use="optional"/>
<attribute name="indeterminatePosition" type="gml:TimeIndeterminateValueType" use="optional"/>
</extension>
</simpleContent>
</complexType>
<!-- ================================================= -->
<simpleType name="TimePositionUnion">
<annotation>
<documentation xml:lang="en">The ISO 19108:2002 hierarchy of subtypes for temporal position are collapsed
by defining a union of XML Schema simple types for indicating temporal position relative
to a specific reference system.
Dates and dateTime may be indicated with varying degrees of precision.
dateTime by itself does not allow right-truncation, except for fractions of seconds.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
An ordinal position may be referenced via URI identifying the definition of an ordinal era.
A time coordinate value is indicated as a decimal (e.g. UNIX time, GPS calendar).</documentation>
</annotation>
<union memberTypes="gml:CalDate time dateTime anyURI decimal"/>
</simpleType>
<!-- ================================================= -->
<simpleType name="CalDate">
<annotation>
<documentation xml:lang="en">Calendar dates may be indicated with varying degrees of precision,
using year, year-month, date.
When used with non-Gregorian calendars based on years, months, days,
the same lexical representation should still be used, with leading zeros added if the
year value would otherwise have fewer than four digits.
time is used for a position that recurs daily (see clause 5.4.4.2 of ISO 19108:2002).</documentation>
</annotation>
<union memberTypes="date gYearMonth gYear"/>
</simpleType>
<!-- ================================================= -->
<!-- ================================================= -->
<!-- ================================================= -->
<!-- ================================================= -->
( run in 0.687 second using v1.01-cache-2.11-cpan-5dc5da66d9d )