Geo-GML
view release on metacpan or search on metacpan
lib/Geo/GML/xsd/gml-3.0.0/base/temporal.xsd view on Meta::CPAN
<documentation xml:lang="en">
This abstract element acts as the head of the substitution group for temporal primitives and complexes.
</documentation>
</annotation>
</element>
<!-- ===================================== -->
<complexType name="AbstractTimeType" abstract="true">
<annotation>
<documentation xml:lang="en">
A temporal object 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:AbstractGMLType">
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
</extension>
</complexContent>
</complexType>
<!-- ================================================================== -->
<element name="_TimePrimitive" type="gml:TimePrimitiveType" abstract="true" substitutionGroup="gml:_TimeObject">
lib/Geo/GML/xsd/gml-3.0.0/base/temporal.xsd view on Meta::CPAN
<annotation>
<documentation xml:lang="en">
Here we have collapsed the hierarchy of subtypes for temporal position in 19108
by defining a union of simple types for indicating temporal position relative to a
specific reference system.
Date and time may be indicated with varying degrees of precision:
year, year-month, date, or dateTime (all ISO 8601 format). Note
that the dateTime type does not allow right-truncation (i.e. omitting
seconds). An ordinal era may be referenced via URI, and a decimal value
can be used to indicate the distance from the scale origin (e.g. UNIX time,
GPS calendar).
</documentation>
</annotation>
<union memberTypes="dateTime date gYearMonth gYear anyURI decimal"/>
</simpleType>
<!-- ================================================================== -->
<element name="timePosition" type="gml:TimePositionType">
<annotation>
<documentation>Direct representation of a temporal position. </documentation>
</annotation>
</element>
<!-- ===================================== -->
<complexType name="TimePositionType" final="#all">
<annotation>
<documentation xml:lang="en">
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:TemporalPositionType">
<attribute name="indeterminatePosition" type="gml:TimeIndeterminateValueType" use="optional"/>
<attribute name="calendarEraName" type="string" use="optional"/>
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
</extension>
</simpleContent>
</complexType>
<!-- ================================================================== -->
<simpleType name="TimeIndeterminateValueType">
<annotation>
<documentation xml:lang="en">
This enumerated data type specifies values for indeterminate positions.
</documentation>
lib/Geo/GML/xsd/gml-3.0.0/base/temporal.xsd view on Meta::CPAN
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================ types for defining temporal reference systems ============ -->
<element name="TimeReferenceSystem" type="gml:TimeReferenceSystemType" substitutionGroup="gml:_GML"/>
<!-- ===================================== -->
<complexType name="TimeReferenceSystemType">
<annotation>
<documentation xml:lang="en">
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, e.g. UNIX time).
</documentation>
</annotation>
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="domainOfValidity" type="string"/>
</sequence>
</extension>
</complexContent>
lib/Geo/GML/xsd/gml-3.0.1/base/temporal.xsd view on Meta::CPAN
<documentation xml:lang="en">
This abstract element acts as the head of the substitution group for temporal primitives and complexes.
</documentation>
</annotation>
</element>
<!-- ===================================== -->
<complexType name="AbstractTimeType" abstract="true">
<annotation>
<documentation xml:lang="en">
A temporal object 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:AbstractGMLType">
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
</extension>
</complexContent>
</complexType>
<!-- ================================================================== -->
<element name="_TimePrimitive" type="gml:TimePrimitiveType" abstract="true" substitutionGroup="gml:_TimeObject">
lib/Geo/GML/xsd/gml-3.0.1/base/temporal.xsd view on Meta::CPAN
<annotation>
<documentation xml:lang="en">
Here we have collapsed the hierarchy of subtypes for temporal position in 19108
by defining a union of simple types for indicating temporal position relative to a
specific reference system.
Date and time may be indicated with varying degrees of precision:
year, year-month, date, or dateTime (all ISO 8601 format). Note
that the dateTime type does not allow right-truncation (i.e. omitting
seconds). An ordinal era may be referenced via URI, and a decimal value
can be used to indicate the distance from the scale origin (e.g. UNIX time,
GPS calendar).
</documentation>
</annotation>
<union memberTypes="dateTime date gYearMonth gYear anyURI decimal"/>
</simpleType>
<!-- ================================================================== -->
<element name="timePosition" type="gml:TimePositionType">
<annotation>
<documentation>Direct representation of a temporal position. </documentation>
</annotation>
</element>
<!-- ===================================== -->
<complexType name="TimePositionType" final="#all">
<annotation>
<documentation xml:lang="en">
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:TemporalPositionType">
<attribute name="indeterminatePosition" type="gml:TimeIndeterminateValueType" use="optional"/>
<attribute name="calendarEraName" type="string" use="optional"/>
<attribute name="frame" type="anyURI" use="optional" default="#ISO-8601"/>
</extension>
</simpleContent>
</complexType>
<!-- ================================================================== -->
<simpleType name="TimeIndeterminateValueType">
<annotation>
<documentation xml:lang="en">
This enumerated data type specifies values for indeterminate positions.
</documentation>
lib/Geo/GML/xsd/gml-3.0.1/base/temporal.xsd view on Meta::CPAN
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================ types for defining temporal reference systems ============ -->
<element name="TimeReferenceSystem" type="gml:TimeReferenceSystemType" substitutionGroup="gml:_GML"/>
<!-- ===================================== -->
<complexType name="TimeReferenceSystemType">
<annotation>
<documentation xml:lang="en">
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, e.g. UNIX time).
</documentation>
</annotation>
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="domainOfValidity" type="string"/>
</sequence>
</extension>
</complexContent>
lib/Geo/GML/xsd/gml-3.1.0/base/temporal.xsd view on Meta::CPAN
This abstract element acts as the head of the substitution group for temporal geometric primitives.
</documentation>
</annotation>
</element>
<!-- ===================================== -->
<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="TimeGeometricPrimitivePropertyType">
lib/Geo/GML/xsd/gml-3.1.0/base/temporal.xsd view on Meta::CPAN
<documentation>Direct representation of a temporal position</documentation>
</annotation>
</element>
<!-- ================================================================== -->
<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>
<!-- ================================================================== -->
<simpleType name="TimeIndeterminateValueType">
<annotation>
lib/Geo/GML/xsd/gml-3.1.0/base/temporalReferenceSystems.xsd view on Meta::CPAN
<element name="_TimeReferenceSystem" type="gml:AbstractTimeReferenceSystemType" abstract="true" substitutionGroup="gml:_GML">
<annotation>
<documentation>Abstract element serves primarily as the head of a substitution group for temporal reference systems.</documentation>
</annotation>
</element>
<!-- ===================================== -->
<complexType name="AbstractTimeReferenceSystemType" abstract="true">
<annotation>
<documentation xml:lang="en">
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, e.g. UNIX time).
</documentation>
</annotation>
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="domainOfValidity" type="string" minOccurs="0"/>
</sequence>
</extension>
</complexContent>
lib/Geo/GML/xsd/gml-3.1.0/base/temporalReferenceSystems.xsd view on Meta::CPAN
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================================================================== -->
<!-- == Calendar == -->
<!-- ================================================================== -->
<element name="TimeCalendar" type="gml:TimeCalendarType" substitutionGroup="gml:_TimeReferenceSystem"/>
<!-- ===================================== -->
<complexType name="TimeCalendarType">
<annotation>
<documentation xml:lang="en">A calendar is a discrete temporal reference system
that provides a basis for defining temporal position to a resolution of one day.
A single calendar may reference more than one calendar era.</documentation>
</annotation>
<complexContent>
<extension base="gml:AbstractTimeReferenceSystemType">
<sequence>
<element name="referenceFrame" type="gml:TimeCalendarEraPropertyType" maxOccurs="unbounded">
<annotation>
<documentation>Link to the CalendarEras that it uses as a reference for dating.</documentation>
</annotation>
</element>
</sequence>
lib/Geo/GML/xsd/gml-3.1.0/base/temporalReferenceSystems.xsd view on Meta::CPAN
<element ref="gml:TimeCalendar"/>
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================================================================== -->
<element name="TimeCalendarEra" type="gml:TimeCalendarEraType"/>
<!-- ===================================== -->
<complexType name="TimeCalendarEraType">
<annotation>
<documentation xml:lang="en">
In every calendar, years are numbered relative to the date of a
reference event that defines a calendar era.
In this implementation, we omit the back-pointer "datingSystem". </documentation>
</annotation>
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType">
<annotation>
<documentation>Name or description of a mythical or historic event which fixes the position of the base scale of the calendar era.</documentation>
</annotation>
</element>
<element name="referenceDate" type="date" default="0001-01-01" minOccurs="0">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="julianReference" type="decimal">
<annotation>
<documentation>Julian date that corresponds to the reference date.
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.
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.</documentation>
</annotation>
</element>
<element name="epochOfUse" type="gml:TimePeriodPropertyType">
<annotation>
<documentation>Period for which the calendar era was used as a basis for dating.</documentation>
</annotation>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- ================================================================== -->
<complexType name="TimeCalendarEraPropertyType">
<sequence minOccurs="0">
<element ref="gml:TimeCalendarEra"/>
lib/Geo/GML/xsd/gml-3.1.0/base/temporalReferenceSystems.xsd view on Meta::CPAN
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================================================================== -->
<!-- == Clock == -->
<!-- ================================================================== -->
<element name="TimeClock" type="gml:TimeClockType" substitutionGroup="gml:_TimeReferenceSystem"/>
<!-- ===================================== -->
<complexType name="TimeClockType" final="#all">
<annotation>
<documentation xml:lang="en">A clock provides a basis for defining temporal position within a day.
A clock must be used with a calendar in order to provide a complete description of a temporal position
within a specific day. </documentation>
</annotation>
<complexContent>
<extension base="gml:AbstractTimeReferenceSystemType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType">
<annotation>
<documentation>Name or description of an event, such as solar noon or sunrise,
which fixes the position of the base scale of the clock.</documentation>
</annotation>
lib/Geo/GML/xsd/gml-3.1.1/base/temporal.xsd view on Meta::CPAN
<element name="_TimeGeometricPrimitive" type="gml:AbstractTimeGeometricPrimitiveType" abstract="true" substitutionGroup="gml:_TimePrimitive">
<annotation>
<documentation xml:lang="en">This abstract element acts as the head of the substitution group for temporal geometric primitives.</documentation>
</annotation>
</element>
<!-- ===================================== -->
<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="TimeGeometricPrimitivePropertyType">
<sequence minOccurs="0">
lib/Geo/GML/xsd/gml-3.1.1/base/temporal.xsd view on Meta::CPAN
<documentation>Direct representation of a temporal position</documentation>
</annotation>
</element>
<!-- ================================================================== -->
<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>
<!-- ================================================================== -->
<simpleType name="TimeIndeterminateValueType">
<annotation>
<documentation xml:lang="en">This enumerated data type specifies values for indeterminate positions.</documentation>
lib/Geo/GML/xsd/gml-3.1.1/base/temporalReferenceSystems.xsd view on Meta::CPAN
<!-- ================================================================== -->
<element name="_TimeReferenceSystem" type="gml:AbstractTimeReferenceSystemType" abstract="true" substitutionGroup="gml:Definition">
<annotation>
<documentation>Abstract element serves primarily as the head of a substitution group for temporal reference systems.</documentation>
</annotation>
</element>
<!-- ===================================== -->
<complexType name="AbstractTimeReferenceSystemType" abstract="true">
<annotation>
<documentation xml:lang="en">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, e.g. UNIX time).</documentation>
</annotation>
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="domainOfValidity" type="string" minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
lib/Geo/GML/xsd/gml-3.1.1/base/temporalReferenceSystems.xsd view on Meta::CPAN
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================================================================== -->
<!-- == Calendar == -->
<!-- ================================================================== -->
<element name="TimeCalendar" type="gml:TimeCalendarType" substitutionGroup="gml:_TimeReferenceSystem"/>
<!-- ===================================== -->
<complexType name="TimeCalendarType">
<annotation>
<documentation xml:lang="en">A calendar is a discrete temporal reference system
that provides a basis for defining temporal position to a resolution of one day.
A single calendar may reference more than one calendar era.</documentation>
</annotation>
<complexContent>
<extension base="gml:AbstractTimeReferenceSystemType">
<sequence>
<element name="referenceFrame" type="gml:TimeCalendarEraPropertyType" maxOccurs="unbounded">
<annotation>
<documentation>Link to the CalendarEras that it uses as a reference for dating.</documentation>
</annotation>
</element>
</sequence>
lib/Geo/GML/xsd/gml-3.1.1/base/temporalReferenceSystems.xsd view on Meta::CPAN
<sequence minOccurs="0">
<element ref="gml:TimeCalendar"/>
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================================================================== -->
<element name="TimeCalendarEra" type="gml:TimeCalendarEraType" substitutionGroup="gml:Definition"/>
<!-- ===================================== -->
<complexType name="TimeCalendarEraType">
<annotation>
<documentation xml:lang="en">In every calendar, years are numbered relative to the date of a
reference event that defines a calendar era.
In this implementation, we omit the back-pointer "datingSystem".</documentation>
</annotation>
<complexContent>
<extension base="gml:DefinitionType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType">
<annotation>
<documentation>Name or description of a mythical or historic event which fixes the position of the base scale of the calendar era.</documentation>
</annotation>
</element>
<element name="referenceDate" type="date" default="0001-01-01" minOccurs="0">
<annotation>
<documentation>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.</documentation>
</annotation>
</element>
<element name="julianReference" type="decimal">
<annotation>
<documentation>Julian date that corresponds to the reference date.
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.
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.</documentation>
</annotation>
</element>
<element name="epochOfUse" type="gml:TimePeriodPropertyType">
<annotation>
<documentation>Period for which the calendar era was used as a basis for dating.</documentation>
</annotation>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- ================================================================== -->
<complexType name="TimeCalendarEraPropertyType">
<sequence minOccurs="0">
<element ref="gml:TimeCalendarEra"/>
lib/Geo/GML/xsd/gml-3.1.1/base/temporalReferenceSystems.xsd view on Meta::CPAN
<attributeGroup ref="gml:AssociationAttributeGroup"/>
</complexType>
<!-- ================================================================== -->
<!-- == Clock == -->
<!-- ================================================================== -->
<element name="TimeClock" type="gml:TimeClockType" substitutionGroup="gml:_TimeReferenceSystem"/>
<!-- ===================================== -->
<complexType name="TimeClockType" final="#all">
<annotation>
<documentation xml:lang="en">A clock provides a basis for defining temporal position within a day.
A clock must be used with a calendar in order to provide a complete description of a temporal position
within a specific day.</documentation>
</annotation>
<complexContent>
<extension base="gml:AbstractTimeReferenceSystemType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType">
<annotation>
<documentation>Name or description of an event, such as solar noon or sunrise,
which fixes the position of the base scale of the clock.</documentation>
</annotation>
lib/Geo/GML/xsd/gml-3.1.1/profiles/gmlJP2Profile/1.0.0/gmlJP2Profile.xsd view on Meta::CPAN
</sequence>
</extension>
</complexContent>
</complexType>
<!-- ================================================= -->
<complexType name="AbstractTimeGeometricPrimitiveType" abstract="true">
<annotation>
<documentation xml:lang="en">
The abstract supertype for temporal geometric primitives.
A temporal geometry shall 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="AbstractTimePrimitiveType" abstract="true">
lib/Geo/GML/xsd/gml-3.1.1/profiles/gmlJP2Profile/1.0.0/gmlJP2Profile.xsd view on Meta::CPAN
</documentation>
</annotation>
</element>
<!-- ================================================= -->
<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/GML/xsd/gml-3.2.1/temporal.xsd view on Meta::CPAN
</annotation>
</element>
<complexType name="AbstractTimeComplexType" abstract="true">
<complexContent>
<extension base="gml:AbstractTimeObjectType"/>
</complexContent>
</complexType>
<element name="AbstractTimeGeometricPrimitive" type="gml:AbstractTimeGeometricPrimitiveType" abstract="true" substitutionGroup="gml:AbstractTimePrimitive">
<annotation>
<documentation>gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives.
A temporal geometry 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 defa...
The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows.</documentation>
</annotation>
</element>
<complexType name="AbstractTimeGeometricPrimitiveType" abstract="true">
<complexContent>
<extension base="gml:AbstractTimePrimitiveType">
<attribute name="frame" type="anyURI" default="#ISO-8601"/>
</extension>
</complexContent>
</complexType>
lib/Geo/GML/xsd/gml-3.2.1/temporal.xsd view on Meta::CPAN
</annotation>
<sequence minOccurs="0">
<element ref="gml:TimePeriod"/>
</sequence>
<attributeGroup ref="gml:AssociationAttributeGroup"/>
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
</complexType>
<complexType name="TimePositionType" final="#all">
<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 t...
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 ref...
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 name="frame" type="anyURI" default="#ISO-8601"/>
<attribute name="calendarEraName" type="string"/>
<attribute name="indeterminatePosition" type="gml:TimeIndeterminateValueType"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="TimeIndeterminateValueType">
<annotation>
<documentation>These values are interpreted as follows:
- "unknown" indicates that no specific value for temporal position is provided.
- "now" indicates that the specified value shall be replaced with the current temporal position whenever the value is accessed.
- "before" indicates that the actual temporal position is unknown, but it is known to be before the specified value.
lib/Geo/GML/xsd/gml-3.2.1/temporal.xsd view on Meta::CPAN
<enumeration value="after"/>
<enumeration value="before"/>
<enumeration value="now"/>
<enumeration value="unknown"/>
</restriction>
</simpleType>
<simpleType name="TimePositionUnion">
<annotation>
<documentation>The simple type gml:TimePositionUnion is a union of XML Schema simple types which instantiate the subtypes for temporal position described in ISO 19108.
An ordinal era may be referenced via URI. A decimal value may be used to indicate the distance from the scale origin . time is used for a position that recurs daily (see ISO 19108:2002 5.4.4.2).
Finally, calendar and clock forms that support the representation of time in systems based on years, months, days, hours, minutes and seconds, in a notation following ISO 8601, are assembled by gml:CalDate</documentation>
</annotation>
<union memberTypes="gml:CalDate time dateTime anyURI decimal"/>
</simpleType>
<simpleType name="CalDate">
<union memberTypes="date gYearMonth gYear"/>
</simpleType>
<element name="timePosition" type="gml:TimePositionType">
<annotation>
<documentation>This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas.</documentation>
</annotation>
lib/Geo/GML/xsd/gml-3.2.1/temporalReferenceSystems.xsd view on Meta::CPAN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://www.opengis.net/gml/3.2" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" version="3.2.1.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 tem...
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"/>
lib/Geo/GML/xsd/gml-3.2.1/temporalReferenceSystems.xsd view on Meta::CPAN
<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" type="gml:TimeCalendarType" substitutionGroup="gml:TimeReferenceSystem">
<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.<...
</annotation>
</element>
<complexType name="TimeCalendarType">
<complexContent>
<extension base="gml:TimeReferenceSystemType">
<sequence>
<element name="referenceFrame" type="gml:TimeCalendarEraPropertyType" maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="TimeCalendarEra" type="gml:TimeCalendarEraType">
<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 dat...
- 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"/>
lib/Geo/GML/xsd/gml-3.2.1/temporalReferenceSystems.xsd view on Meta::CPAN
<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" type="gml:TimeClockType" substitutionGroup="gml:TimeReferenceSystem">
<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 name="TimeClockType" final="#all">
<complexContent>
<extension base="gml:TimeReferenceSystemType">
<sequence>
<element name="referenceEvent" type="gml:StringOrRefType"/>
<element name="referenceTime" type="time"/>
<element name="utcReference" type="time"/>
<element name="dateBasis" type="gml:TimeCalendarPropertyType" minOccurs="0" maxOccurs="unbounded"/>
( run in 0.335 second using v1.01-cache-2.11-cpan-5dc5da66d9d )