diff --git a/23-049/.asciidoctor/diagram/diag-4da99f3ea39256fc98680ea621a08c02.png.cache b/23-049/.asciidoctor/diagram/diag-4da99f3ea39256fc98680ea621a08c02.png.cache new file mode 100644 index 00000000..7b5c8b6c --- /dev/null +++ b/23-049/.asciidoctor/diagram/diag-4da99f3ea39256fc98680ea621a08c02.png.cache @@ -0,0 +1 @@ +{"checksum":"4da99f3ea39256fc98680ea621a08c02","options":{"size_limit":"4096"},"width":957,"height":902} \ No newline at end of file diff --git a/23-049/23-049.adoc b/23-049/23-049.adoc index 39fb7c0f..85e756ea 100644 --- a/23-049/23-049.adoc +++ b/23-049/23-049.adoc @@ -7,7 +7,7 @@ :docnumber: 23-049 :received-date: 2023-05-23 :issued-date: 2023-05-23 -:published-date: 2023-08-29 +:published-date: 2023-09-23 :external-id: http://www.opengis.net/doc/AS/temporal-conceptual-model/1.0 :referenceURLID: http://docs.opengeospatial.org/as/23-049/23-049.html :fullname: Chris Little diff --git a/23-049/23-049.doc b/23-049/23-049.doc index 09115f40..39e7adcb 100644 --- a/23-049/23-049.doc +++ b/23-049/23-049.doc @@ -1,7 +1,7 @@ MIME-Version: 1.0 -Content-Type: multipart/related; boundary="----=_NextPart_83e25b7b.71b6.4878" +Content-Type: multipart/related; boundary="----=_NextPart_b610fa7b.50e0.4664" -------=_NextPart_83e25b7b.71b6.4878 +------=_NextPart_b610fa7b.50e0.4664 Content-ID: <23-049.htm> Content-Disposition: inline; filename="23-049.htm" Content-Type: text/html; charset="utf-8" @@ -2299,7 +2299,7 @@ span.AdmittedLabel {
- Publication Date: 2023-08-26 + Publication Date: 2023-09-23
@@ -2500,22 +2500,22 @@ span.AdmittedLabel {
TOC \o "1-2" \h \z \u -Copyright notice +Copyright notice . - PAGEREF _Toc820855761 \h + PAGEREF _Toc746972309 \h 1
-Note
+Note
.
- PAGEREF _Toc920214063 \h
+ PAGEREF _Toc389653804 \h
1
@@ -2524,11 +2524,11 @@ span.AdmittedLabel {
-License Agreement
+License Agreement
.
- PAGEREF _Toc626208185 \h
+ PAGEREF _Toc856694849 \h
1
@@ -2537,11 +2537,11 @@ span.AdmittedLabel {
-Notice
+Notice
.
- PAGEREF _Toc585868975 \h
+ PAGEREF _Toc091238690 \h
1
@@ -2550,11 +2550,11 @@ span.AdmittedLabel {
-I. Abstract
+I. Abstract
.
- PAGEREF _Toc628817076 \h
+ PAGEREF _Toc138523233 \h
1
@@ -2563,11 +2563,11 @@ span.AdmittedLabel {
-II. Keywords
+II. Keywords
.
- PAGEREF _Toc502234599 \h
+ PAGEREF _Toc661898275 \h
1
@@ -2576,11 +2576,11 @@ span.AdmittedLabel {
-III. Preface
+III. Preface
.
- PAGEREF _Toc807213939 \h
+ PAGEREF _Toc067643696 \h
1
@@ -2589,11 +2589,11 @@ span.AdmittedLabel {
-IV. Security Considerations
+IV. Security Considerations
.
- PAGEREF _Toc650410328 \h
+ PAGEREF _Toc192946020 \h
1
@@ -2602,11 +2602,11 @@ span.AdmittedLabel {
-V. Submitting Organizations
+V. Submitting Organizations
.
- PAGEREF _Toc413358153 \h
+ PAGEREF _Toc541911555 \h
1
@@ -2615,11 +2615,11 @@ span.AdmittedLabel {
-VI. Submitters
+VI. Submitters
.
- PAGEREF _Toc314099192 \h
+ PAGEREF _Toc664451356 \h
1
@@ -2628,11 +2628,11 @@ span.AdmittedLabel {
-VII. Introduction
+VII. Introduction
.
- PAGEREF _Toc627405251 \h
+ PAGEREF _Toc895918339 \h
1
@@ -2641,11 +2641,11 @@ span.AdmittedLabel {
-1. Scope
+1. Scope
.
- PAGEREF _Toc581474769 \h
+ PAGEREF _Toc270800117 \h
1
@@ -2654,11 +2654,11 @@ span.AdmittedLabel {
-2. Conformance
+2. Conformance
.
- PAGEREF _Toc830545567 \h
+ PAGEREF _Toc405020074 \h
1
@@ -2667,11 +2667,11 @@ span.AdmittedLabel {
-3. Normative references
+3. Normative references
.
- PAGEREF _Toc882103979 \h
+ PAGEREF _Toc019224753 \h
1
@@ -2680,11 +2680,11 @@ span.AdmittedLabel {
-4. Terms and definitions
+4. Terms and definitions
.
- PAGEREF _Toc311423494 \h
+ PAGEREF _Toc415645805 \h
1
@@ -2693,11 +2693,11 @@ span.AdmittedLabel {
-5. Conventions
+5. Conventions
.
- PAGEREF _Toc812137963 \h
+ PAGEREF _Toc037933005 \h
1
@@ -2706,11 +2706,11 @@ span.AdmittedLabel {
-5.1. Abbreviated terms
+5.1. Abbreviated terms
.
- PAGEREF _Toc492055487 \h
+ PAGEREF _Toc845490289 \h
1
@@ -2719,11 +2719,11 @@ span.AdmittedLabel {
-5.2. Identifiers
+5.2. Identifiers
.
- PAGEREF _Toc102331826 \h
+ PAGEREF _Toc793725140 \h
1
@@ -2732,11 +2732,11 @@ span.AdmittedLabel {
-6. Characteristics of an Abstract Conceptual Model
+6. Characteristics of an Abstract Conceptual Model
.
- PAGEREF _Toc252811123 \h
+ PAGEREF _Toc416809295 \h
1
@@ -2745,11 +2745,11 @@ span.AdmittedLabel {
-7. Temporal Abstract Conceptual Model
+7. Temporal Abstract Conceptual Model
.
- PAGEREF _Toc312963842 \h
+ PAGEREF _Toc126982528 \h
1
@@ -2758,11 +2758,11 @@ span.AdmittedLabel {
-8. Temporal regimes
+8. Temporal regimes
.
- PAGEREF _Toc040411945 \h
+ PAGEREF _Toc498080000 \h
1
@@ -2771,11 +2771,11 @@ span.AdmittedLabel {
-8.1. General
+8.1. General
.
- PAGEREF _Toc941539265 \h
+ PAGEREF _Toc985956626 \h
1
@@ -2784,11 +2784,11 @@ span.AdmittedLabel {
-8.2. Events and Operators
+8.2. Events and Operators
.
- PAGEREF _Toc652136398 \h
+ PAGEREF _Toc107390850 \h
1
@@ -2797,11 +2797,11 @@ span.AdmittedLabel {
-8.3. Simple Clocks and Discrete Timescales
+8.3. Simple Clocks and Discrete Timescales
.
- PAGEREF _Toc990556298 \h
+ PAGEREF _Toc468574370 \h
1
@@ -2810,11 +2810,11 @@ span.AdmittedLabel {
-8.4. CRS and Continuous Timescales
+8.4. CRS and Continuous Timescales
.
- PAGEREF _Toc457332282 \h
+ PAGEREF _Toc637681915 \h
1
@@ -2823,11 +2823,11 @@ span.AdmittedLabel {
-8.5. Calendars
+8.5. Calendars
.
- PAGEREF _Toc137739798 \h
+ PAGEREF _Toc420864414 \h
1
@@ -2836,11 +2836,11 @@ span.AdmittedLabel {
-8.6. Other Regimes
+8.6. Other Regimes
.
- PAGEREF _Toc293664554 \h
+ PAGEREF _Toc138420442 \h
1
@@ -2849,11 +2849,11 @@ span.AdmittedLabel {
-9. Notation
+9. Notation
.
- PAGEREF _Toc276832709 \h
+ PAGEREF _Toc497781760 \h
1
@@ -2862,11 +2862,11 @@ span.AdmittedLabel {
-10. Attributes of the Regimes/Classes
+10. Attributes of the Classes
.
- PAGEREF _Toc680786147 \h
+ PAGEREF _Toc646801110 \h
1
@@ -2875,11 +2875,11 @@ span.AdmittedLabel {
-10.1. Attributes of Events and Ordinal Temporal Reference Systems
+10.1. Reference Systems
.
- PAGEREF _Toc656079525 \h
+ PAGEREF _Toc592577210 \h
1
@@ -2888,11 +2888,11 @@ span.AdmittedLabel {
-10.2. Attributes of simple Clock and Discrete Timescale
+10.2. Ordinal Temporal Reference Systems
.
- PAGEREF _Toc138191688 \h
+ PAGEREF _Toc003541314 \h
1
@@ -2901,11 +2901,11 @@ span.AdmittedLabel {
-10.3. Attributes of Clocks
+10.3. Temporal Coordinate Reference System
.
- PAGEREF _Toc696404592 \h
+ PAGEREF _Toc643166818 \h
1
@@ -2914,11 +2914,11 @@ span.AdmittedLabel {
-10.4. Attributes of Timescales
+10.4. Calendar Reference Systems
.
- PAGEREF _Toc153354595 \h
+ PAGEREF _Toc846987760 \h
1
@@ -2927,11 +2927,11 @@ span.AdmittedLabel {
-10.5. Attributes of Units of Measure
+10.5. Discrete and Continuous Time Scales
.
- PAGEREF _Toc143151581 \h
+ PAGEREF _Toc543159092 \h
1
@@ -2940,24 +2940,24 @@ span.AdmittedLabel {
-10.6. Attributes of a CRS and Continuous Timescales
+10.6. Supporting Classes
.
- PAGEREF _Toc771140532 \h
+ PAGEREF _Toc545166341 \h
1
+
-10.7. Attributes of Calendars
+11. Synchronisation of clocks
.
- PAGEREF _Toc839968290 \h
+ PAGEREF _Toc784940870 \h
1
@@ -2966,11 +2966,11 @@ span.AdmittedLabel {
-11. Synchronisation of clocks
+12. Temporal Geometry
.
- PAGEREF _Toc248518933 \h
+ PAGEREF _Toc221743189 \h
1
@@ -2979,11 +2979,11 @@ span.AdmittedLabel {
-Annex A (informative) Glossary
+Annex A (informative) Glossary
.
- PAGEREF _Toc949197814 \h
+ PAGEREF _Toc998403818 \h
1
@@ -2992,11 +2992,11 @@ span.AdmittedLabel {
-Bibliography
+Bibliography
.
- PAGEREF _Toc970963250 \h
+ PAGEREF _Toc545027926 \h
1
@@ -3035,7 +3035,7 @@ span.AdmittedLabel {
This document is consistent with ISO 19111 and W3C Time Ontology in OWL. The aim of this document is to establish clear concepts and terminology. The following are keywords to be used by search engines and
document catalogues. No security considerations have been made for this document. The following organizations submitted this Document to the
Open Geospatial Consortium (OGC): IETF: RFC 3339 Date and Time on the Internet: Timestamps. https://www.rfc-editor.org/rfc/rfc3339 ISO/TC 211: 8601:2004 Data elements and interchange formats — Information interchange — Representation of dates and times, 2004, https://www.iso.org/standard/40874.html ISO/TC 211: ISO 19111:2019, Geographic information – Referencing by coordinates, 2019, https://www.iso.org/standard/74039.html Allen, J. F. Maintaining Knowledge about Temporal IntervalsCommunications of the ACM, 1983, vol. 26 pp. 832-843. Allen, J. F. Maintaining Knowledge about Temporal Intervals Communications of the ACM, 1983, vol. 26 pp. 832-843. OGC: 18-005, OGC Abstract Specification Topic 2: Referencing by coordinates Corrigendum, 2021, https://docs.ogc.org/as/18-005r5/18-005r5.html W3C: Time Ontology in OWL, 2017, https://www.w3.org/TR/2017/REC-owl-time-20171019/ This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2. This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec. For the purposes of this document, the following additional terms and definitions apply. description of common concepts and their relationships, particularly in order to facilitate exchange of information between parties within a specific domain. A conceptual model is explicitly chosen to be independent of design or implementation concerns. one of a sequence of numbers designating the position of a point [SOURCE: CEN ENV 1613:1995] 4.2. coordinate reference system coordinate system that is related to an object by a datum Note 1 to entry: In many coordinate reference systems, the coordinate numbers are qualified by units. [SOURCE: ISO 19111] 4.3. coordinate reference system coordinate system that is related to an object by a datum Note 2 to entry: For geodetic and vertical reference frames, the object will be the Earth. In planetary applications, geodetic and vertical reference frames may be applied to other celestial bodies. [SOURCE: ISO 19111] set of mathematical rules for specifying how coordinates are to be assigned to points Note 2 to entry: For geodetic and vertical reference frames, the object will be the Earth. In planetary applications, geodetic and vertical reference frames may be applied to other celestial bodies. [SOURCE: ISO 19111] set of mathematical rules for specifying how coordinates are to be assigned to points [SOURCE: ISO 19111] reference frame ADMITTED [SOURCE: ISO 19111] reference frame ADMITTED parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a coordinate system parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a coordinate system [SOURCE: ISO 19111] [SOURCE: ISO 19111] Note 1 to entry: In this document an epoch is expressed in the Gregorian calendar as a decimal year. Example [SOURCE: ISO 19111] datum ADMITTED Note 1 to entry: In this document an epoch is expressed in the Gregorian calendar as a decimal year. Example [SOURCE: ISO 19111] datum ADMITTED parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a coordinate system parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a coordinate system [SOURCE: ISO 19111] 4.7. temporal coordinate reference system coordinate reference system based on a temporal datum [SOURCE: ISO 19111] 4.8. temporal coordinate reference system coordinate reference system based on a temporal datum [SOURCE: ISO 19111] 4.8. temporal coordinate system [SOURCE: ISO 19111] 4.9. temporal coordinate system <geodesy> one-dimensional coordinate system where the axis is time <geodesy> one-dimensional coordinate system where the axis is time [SOURCE: ISO 19111] datum describing the relationship of a temporal coordinate system to an object [SOURCE: ISO 19111] datum describing the relationship of a temporal coordinate system to an object [SOURCE: ISO 19111] [SOURCE: ISO 19111] This attempt at a Temporal Abstract Conceptual Model follows ISO 19111, which is the ISO adoption of OGC_18-005r4. The model is also informed by the W3C Time Ontology. NOTE This Mermaid diagram should be converted to PlantUML for Metanorma, by replacing
-the Mermaid container with the following. This Temporal Abstract Conceptual Model follows ISO 19111, which is the ISO adoption of OGC_18-005r4. The model is also informed by the W3C Time Ontology.
- [plantuml] @startuml . . @enduml
- classDiagram Figure 1 One set of events may be completely ordered with respect to each other, but another set of similar internally consistent events cannot be cross-referenced until extra information is available. Even then, only partial orderings may be possible. In this regime, the Allen Operators can be used. If A occurs before B and B occurs before C, then we can correctly deduce that A occurs before C. The full set of operators also covers pairs of intervals. So in our example, B occurs in the interval (A,C). However, we cannot perform arithmetic operations like (B-A) or (C-A) as we have not defined any timescale or measurements. For example, in geology, ‘subtracting’ Ordovician from Jurassic is meaningless; or in archeology, ‘subtracting’ a layer with a certain type of pottery remains from the layer containing burnt wood and bones is again not meaningful. Only the ordering can be deduced. In this regime, the Allen Operators can be used. If A occurs before B and B occurs before C, then we can correctly deduce that A occurs before C. The full set of operators also covers pairs of intervals. So in our example, B occurs in the interval (A,C). However, we cannot perform arithmetic operations like (B-A) or (C-A) as we have not defined any timescale or measurements. For example, in geology, ‘subtracting’ Ordovician from Jurassic is meaningless; or in archeology, ‘subtracting’ a layer with a certain type of pottery remains from the layer containing burnt wood and bones is again not meaningful. Only the ordering can be deduced. This regime constitutes an Ordinal Temporal Reference System, with discrete enumerated ordered events. The internationally agreed atomic time, TAI, is an example of a timescale with an integer count as the measure of time, though in practice it is an arithmetic compromise across about two hundred separate atomic clocks, corrected for differing altitudes and temperatures. In this regime, the Allen Operators also can be used. If L occurs before M and M occurs before N, then we can correctly deduce that L occurs before N. The full set of operators also covers pairs of intervals. So if M occurs in the interval (L,N), we can now perform integer arithmetic operations like (M-L) or (N-L) as we have defined an integer timescale or measurement. In this regime, the Allen Operators also can be used. If L occurs before M and M occurs before N, then we can correctly deduce that L occurs before N. The full set of operators also covers pairs of intervals. So if M occurs in the interval (L,N), we can now perform integer arithmetic operations like (M-L) or (N-L) as we have defined an integer timescale or measurement. This regime constitutes a Temporal Coordinate Reference System, with discrete integer units of measure which can be subject to integer arithmetic. This gives us a continuous number line to perform theoretical measurements. It is a coordinate system. With a datum/origin/epoch, a unit of measure (a name for the ‘tick marks’ on the axis), positive and negative directions and the full range of normal arithmetic. It is a Coordinate Reference System. In this regime, the Allen Operators also can be used. If A occurs before B and B occurs before C, then we can correctly deduce that A occurs before C. The full set of operators also covers pairs of intervals. So if B occurs in the interval (A,C), we can now perform real number arithmetic operations like (B-A) or (C-A) as we have defined a timescale or measurement, and between any two instants, we can always find an infinite number of other instants. In this regime, the Allen Operators also can be used. If A occurs before B and B occurs before C, then we can correctly deduce that A occurs before C. The full set of operators also covers pairs of intervals. So if B occurs in the interval (A,C), we can now perform real number arithmetic operations like (B-A) or (C-A) as we have defined a timescale or measurement, and between any two instants, we can always find an infinite number of other instants. Example Unix milliseconds since 1970-01-01T00:00:00.0Z
This regime constitutes a Temporal Coordinate Reference System, with a continuous number line and units of measure, which can be subject to the full range of real or floating point arithmetic. This regime constitutes a Temporal Coordinate Reference System, with a continuous number line and units of measure, which can be subject to the full range of real or floating point arithmetic. In this regime, counts and measures of time are related to the various combinations of the rotations of the earth, moon and sun or other astronomical bodies. There is no simple arithmetic, so for example, the current civil year count of years in the Current Era (CE) and Before Current Era (BCE) is a calendar, albeit a very simple one, as there is no year zero. That is, Year 14CE – Year 12CE is a duration of 2 years, and Year 12BCE — Year 14BCE is also two years. However Year 1CE — Year 1BCE is one year, not two as there is no year 0CE or 0BCE. Calendars are social constructs made by combining several clocks and their associated timescales. In this regime, the use of the Allen Operators is not straightforward. If A occurs before B and B occurs before C, then we cannot always easily and correctly deduce that A occurs before C. The full set of Allen Operators also covers pairs of intervals. So in our example, B occurs in the interval (A,C). However, we cannot usually perform simple arithmetic operations like (B-A) or (C-A) as we are dependent on the vagaries of the calendar algorithms, multiple timescales and multiple Units of Measure. Calendars are social constructs made by combining several clocks and their associated timescales. This paper only addresses the internationally agreed Gregorian calendar. Astronomical Algorithms by Jean Meeus provides overwhelming detail for conversion to numerous other calendars that have developed around the world and over the millennia and to meet the various social needs of communities, whether agricultural, religious or other. The reference is comprehensive but not exhaustive, as there are calendars that have been omitted. This paper only addresses the internationally agreed Gregorian calendar. Calendrical Calculations by Nachum Dershowitz and Edward M. Reingold provides overwhelming detail for conversion to numerous other calendars that have developed around the world and over the millennia and to meet the various social needs of communities, whether agricultural, religious or other. The reference is comprehensive but not exhaustive, as there are calendars that have been omitted. A Calendar is a Temporal Reference System, but it is not a Temporal Coordinate Reference System nor an Ordinal Temporal Reference System. A Calendar is a Temporal Reference System, but it is not a Temporal Coordinate Reference System nor an Ordinal Temporal Reference System. Local solar time may or may not correspond to the local statutory or legal time in a country. Local solar time can be construed as a clock and timescale, with an angular measure of the apparent position of the sun along the ecliptic (path through the sky) as the basic physical principle. When dealing with moving objects, we find that the location of the object in space depends on its location in time. That is to say, that the location is an event in space and time. Astronomers have traditionally measured the apparent locations of stars, planets and other heavenly bodies by measuring angular separations from reference points or lines and the timing of transits across a meridian. Generally they use time determined by earth’s motion relative to the distant stars rather than the sun. This is called sidereal time. Times are usually measured from an epoch in daylight, such as local midday, rather than midnight. Accurate measurements of positions of stars, planets and moons were and are essential for navigation on Earth. See Astronomical Algorithms by Jean Meeus for examples of the calculations involved. Originally developed by Hermann Minkowski to support work in Special Relativity, the concept of Space-time is useful whenever the location of an object in space is dependent on its location in time. Since the speed of light in a vacuum is a measurable constant, Space-time uses that constant to create a coordinate axis with spatial units of measure (meters per second * seconds = meters). The result is coordinate reference system with four orthogonal axis all with the same units of measure, distance. When dealing with moving objects, we find that the location of the object in space depends on its location in time. That is to say, that the location is an event in space and time. Originally developed by Hermann Minkowski to support work in Special Relativity, the concept of space-time is useful whenever the location of an object in space is dependent on its location in time. Since the speed of light, c, in a vacuum is a measurable constant, space-time uses that constant to create a coordinate axis with spatial units of measure (meters per second * seconds = meters). The result is coordinate reference system with four orthogonal axes all with the same units of measure, distance. However, the measure of distance in this 4D space is not the usual Pythagorean d2 = x2 + y2 + z2 +(ct)2 but d2 = x2 + y2 + z2 -(ct)2, so reality is constrained to lying within a double cone subset around the ct axis of the full space. A regime may be needed for ‘space-time’, off the planet Earth, such as for recording and predicting space weather approaching from the sun, where the speed of light and relativistic effects such as gravity may be relevant. A regime may be needed for ‘space-time’, off the planet Earth, such as for recording and predicting space weather approaching from the sun, where the speed of light and relativistic effects such as gravity may be relevant. Once off the planet Earth, distances and velocities can become very large. The speed of light becomes a limiting factor in measuring both where and when an event takes place. Special Relativity deals with the accurate measurement of space-time events as measured between two moving objects. The core concepts are the Lorentz Transforms. These transforms allow one to calculate the degree of “contraction” a measurement undergos due to the relative velocity between the observing and observed object. Once off the planet Earth, distances and velocities can become very large. The speed of light becomes a limiting factor in measuring both where and when an event takes place. Special Relativity deals with the accurate measurement of space-time events as measured between two moving objects. The core concepts are the Lorentz Transforms. These transforms allow one to calculate the degree of “contraction” a measurement undergos due to the relative velocity between the observing and observed object. The key to this approach is to ensure each moving feature of interest has its own local clock and time, known as its ‘proper time’. This example can be construed as a fitting into the clock and timescale regime. The relativistic effects are addressed through the relationships between the separate clocks, positions and velocities of the features. The key to this approach is to ensure each moving feature of interest has its own local clock and time, known as its ‘proper time’. This example can be construed as a fitting into the clock and timescale regime. The relativistic effects are addressed through the relationships between the separate clocks, positions and velocities of the features. Relativistic effects may need to be taken into account for satellites and other space craft because of their relative speed and position in Earth’s gravity well. Relativistic effects may need to be taken into account for satellites and other space craft because of their relative speed and position in Earth’s gravity well. The presence of gravitational effects requires special relativity to te replaced by general relativity, and it can no longer be assumed that space (or space-time) is Euclidean. That is, Pythagoras’ Theorem does not hold execept locally over small areas. this is somewhat unfamiliar territory for geospatial experts. The presence of gravitational effects requires special relativity to be replaced by general relativity, and it can no longer be assumed that space (or space-time) is Euclidean. That is, Pythagoras’ Theorem does not hold execept locally over small areas. This is somewhat familiar territory for geospatial experts. The financial and administrative domains often use weeks, quarters, and other calendrical measures. These may be convenient (though often not!) for the requisite tasks, but are usually inappropriate for scientific or technical purposes. The financial and administrative domains often use weeks, quarters, and other calendrical measures. These may be convenient (though often not!) for the requisite tasks, but are usually inappropriate for scientific or technical purposes. The IETF RFC 3339 timestamp notation, a restrictive profile of ISO 8601, can express times before 1588CE, when the Gregorian calendar was first introduced in some parts of the world. The top level ReferenceSystem is an abstract super-class and does not have many attributes or properties. So far, only the total dimension of the reference system and the Location, Time or Domain of Applicability have been identified as essential. The ‘ReferenceSystem’ has two abstract sub-classes: ‘SpatialReferenceSystem’, which is defined in ISO 19111, and ‘TemporalReferenceSystem’, each with the attributes of Dimension and Domains of Applicability. The Dimension is one for time, or a vertical reference system, but may be as much as 6 for spatial location with orientation. Besides the conventional space and time, there may be other reference systems, such as wavelength/frequency, that can be addressed by the Abstract Conceptual Model. The top level ReferenceSystem is an abstract super-class and does not have many attributes or properties. So far, only the total dimension of the reference system and the Location, Time or Domain of Applicability have been identified as essential. An OrdinalTemporal Reference System has a well-ordered finite sequence of events against which other events can be compared. The ‘ReferenceSystem’ has two abstract sub-classes: ‘SpatialReferenceSystem’, which is defined in ISO 19111, and ‘TemporalReferenceSystem’, each with the attributes of Dimension and Domains of Applicability. The Dimension is one for time, or a vertical reference system, but may be as much as 6 for spatial location with orientation as in the GeoPose Draft Specification. Besides the conventional space and time, there may be other reference systems, such as wavelength/frequency, that can be addressed by the Abstract Conceptual Model. Name/Id
+ An OrdinalTemporal Reference System has a well-ordered finite sequence of events against which other events can be compared. An Ordinal Temporal Reference System is a type of temporal reference system. Therefore, it inherits the following attributes from the TemporalReferenceSystem class: applicableLocationTimeOrDomain: the location, time or domain of applicability
Optional location, time or domain of applicability
+ dimension: the number of dimensions in this reference system. For Ordinal Temporal Reference Systems this value is fixed at 1.
Optional Epoch, defined in some temporal reference system
+
+
+ An Ordinal Temporal Reference System does not have any attributes of its own. However, it does use associations with other classes to fully describe itself. Epoch: An Ordinal Temporal Reference System ‘has a’ one optional Epoch
Listed or enumerated sequence of events with the first and last events
+ Notation: An Ordinal Temporal Reference System ‘can use’ one or more Notations to represent itself.
Optional notations
+ Notation: An Ordinal Temporal Reference System ‘consists of’ an ordered set of Events. These events are identifiable temporal instances.
Example Ancient annals of a country may give a sequence of emperors which could be used to ‘date’ another event such as “Emperor Xi built a canal”, or may be used to date a particular reign. For example: “In the reign of Emperor Yi, a comet was sighted” and later research identifies this as an appearance of Hailey’s Comet. Example Ancient annals of a country may give a sequence of emperors which could be used to ‘date’ another event such as “Emperor Xi built a canal”, or may be used to date a particular reign. For example: “In the reign of Emperor Yi, a comet was sighted” and later research identifies this as an appearance of Hailey’s Comet. The events from the list may be instants, such as the change of reign, or intervals, such as the complete reign of each king. The Events class is an ordered list of temporal events. The events can be instances, such as the ascension of a King to a throne, or intervals, such as the complete reign of each king. Other documents may enable two such ‘king lists’ to be related, though not completely. Other documents may enable two such ‘king lists’ to be related, though not completely. A clock is a regular, repeating, physical event, or ‘tick’, that can be counted. The sequence of tick counts is a timescale. The ticks may be grouped into a Unit of Meaure for convenience. Other events can be compared to the ticks on the timescale. A Temporal Coordinate Reference System is a type of temporal reference system. Therefore, it inherits the following attributes from the TemporalReferenceSystem class: Name/Id
- Optional location, time or domain of applicability
- Optional Epoch, defined in some temporal reference system
+ applicableLocationTimeOrDomain: the location, time or domain of applicability
Arithmetic: Integer
+ dimension: the number of dimensions in this reference system. For Temporal Coordinate Reference Systems this value is fixed at 1.
Optional name for each tick
+
+
+ A Temporal Coordinate Reference System does not have any attributes of its own. However, it does use associations with other classes to fully describe itself. Epoch: A Temporal CRS ‘has a’ one optional Epochs
Optional Start time or count
+ Notation: A Temporal CRS ‘can use’ one or more Notations to represent itself.
Optional End time or count
+ Timescale: A Temporal CRS ‘has a’ one Timescale which is used to represent the values along its single axis. This Timescale can be either discrete or continuous.
Optional Unit of Measure and number of ticks per Unit
+
+ Calendars combine different timescales and their clocks and units of measure, and other events, to make a complex timeline against which events can be compared. Calculated algorithms are used to determine which instants of intervals on the compound timeline are identified and labeled. A Calendar is a type of temporal reference system. Therefore, it inherits the following attributes from the TemporalReferenceSystem class: applicableLocationTimeOrDomain: the location, time or domain of applicability
Optional notations
+ dimension: the number of dimensions in this reference system. For Calendars this value is fixed at 1.
Example 1 A well preserved fossilised log is recovered and the tree rings establish an annual ‘tick’. The start and end times may be known accurately by comparison and matching with other known tree ring sequences, or perhaps only dated imprecisely via Carbon Dating, or its archaeological or geological context. A Calendar does not have any attributes of its own. However, it does use associations with other classes to fully describe itself. Example 2 A clock is started, but undergoes a calibration process against some standard clock, so the initial, reliable Start Time does not start at Count Zero. The clock is accidentially knocked so that it is no longer correctly caliabrated, but is still working. the End Time is not the last time that the clock ticks. Name/id
+ Algorithm: A Calendar ‘has a’ one or more Algorithms. These Algorithms specify how the multiple Time Scales are aggregated into a single Timeline.
+ Epoch: A calendar ‘has a’ one optional Epoch
Optional location, time or domain of applicability
+ Notation: A calendar ‘can use’ one or more Notations to represent itself.
Optional Epoch, defined in some temporal reference system
+ Timeline: A Calendar ‘has a’ one Timeline which serves to aggregate a number of Timescales into a single coherent measure of date and time.
Tick definition
+ Timescale: A Calendar ‘has a’ two or more Timescales which are used to construct a Timeline.
Example 1 The timeline is usually a set of instants from the past to the future and is compounded from multiple timescales, with multiple units of measures, and complicated arithmetic determined by the calendar algorithm(s). The timeline is usually not even continuous, having gaps or even multiple simultaneous representations. Name/id
- Optional location, time or domain of applicability
- Optional Epoch, defined in some temporal reference system
- Arithmetic, whether counted integers or measured real/floating point numbers
+ A Timeline does not have any attributes of its own. Nor does it inherit any attributes from a parent class. However, it does use associations with other classes to fully describe itself. Algorithm: A Timeline ‘has a’ one or more Algorithms. These Algorithms specify how the multiple Time Scales are aggregated into a single Timeline.
Optional Unit of Measure
+ Timescale: A Timeline ‘has a’ two or more Timescales which are used to construct the Timeline.
Example 1 TAI (International Atomic Time, Temps Atomique International) is coordinated by the BIPM (International Bureau of Weights and Measures, Bureau International de Poids et Measures) in Paris, France. It is based on the average of hundreds of separate atomic clocks around the world, all corrected to be at mean sea level and standard pressure and temperature. The epoch is defined by Julian Date 2443144.5003725 (1 January 1977 00:00:32.184). An Algorithm specifies the logic used to construct a Timeline from its constituent Timescales. A Timeline does not have any attributes of its own. Nor does it make use of any other classes from this Temporal model. Example 2 The Julian Day is the continuous count of days (rotations of the Earth with respect to the Sun) since the beginning of the year 4173 BCE and will terminate at the end of the year 3267 CE. The count then starts again as “Period 2”. Many computer based timescales, such as Unix Time, are based on the Julian Day timescale, but with different epochs, to fit the numbers into the limited computer words. Example 1 The modern Gregorian calendar is calculated solar calendar, with various epochs from 1588 CE through to 1922 CE depending on location or country. The constituent timescales are days (earth’s rotations), months (moon’s orbit around the earth), years (earth’s orbit around the sun) and seconds determined by atomic clocks. To accommodate discrepancies, leap days and leap seconds are intercalated in some years. The commonest notations for the Gregorian calendar are ISO 8601 and its various restrictive profiles. Example 2 The timeline in a country may have gaps when clocks ‘spring forward’ for enacting daylight saving time. There may not be any time corresponding to the times between 01:00 and 02:00. When the daylight saving time is revoked, and clocks ‘fall back’, the times between 01:00 and 02:00 occur twice. The Direction attribute indicates whether counts or measures increase in the positive (future) or negative (past) direction. The attribute could be part of ‘Timescale’ or ‘TemporalCoordinateReferenceSystem’ rather than a separate class ‘UnitOfMeasure’, but on balance, it seems better here, as the names often imply directionality, such as fathoms increasing downwards, MYA (Millions of Years Ago) increasing earlier, Atmospheric Pressure in HPs (HectoPascals) decreasing upwards, and FL (FlightLevel) increasing upwards. Example 3 The modern Islamic calendar is an observed lunar calendar, and the major religious dates progress throughout the year, year on year. The important months are determined by the observation of new moons from Mecca. Name/Id/Abbreviation
- Direction
- Example 4 The modern Jewish calendar is a calculated luni-solar calendar, and discrepancies in the solar year are addressed by adding ‘leap months’ every few years. Example 5 The Ba’hai calendar is a calculated solar calendar, but without any other astronomical aspects. The year consists of 19 months of 19 days each, with 4 or 5 intercalated days for a new year holiday. Example 6 The West African Yoruba traditional calendar is a solar calendar with months, but rather than subdividing a nominal month of 28 days into 4 weeks, 7 weeks of 4 days are used. This perhaps gave rise to the fortnightly (every 8 days) markets in many villages in the grasslands of north-west Cameroon. Example The number of the years before the Current Era (BCE, previously known as BC) increase further back in time, whereas the number of the years in the Current Era (CE, previously known as AD) increase further into the future. Tis is an example of two timescales, adjacent but with no overlap. If there was a year zero defined, they could be replaced with one continuous timescale. Example 7 Some clocks allow the measurement of intervals between ticks, such as the movement of the sun across the sky. Alternatively, the ticks may not be completely distinguishable, but are still stable enough over the time of applicability to allow measurements rather than counting to determine the passage of time. A clock may be a regular, repeating, physical event, or ‘tick’, that can be counted. The sequence of tick counts form a discrete (counted) timescale. Name/Id
- Optional location, time or domain of applicability
- Optional Epoch, defined in some temporal reference system
+ Some clocks allow the measurement of intervals between ticks, such as the movement of the sun across the sky. Alternatively, the ticks may not be completely distinguishable, but are still stable enough over the time of applicability to allow measurements rather than counting to determine the passage of time. These clocks generate a continuous (measured) timescale. The duration of a tick is a constant. The length of a tick is specified using a Unit Of Measure. A Timescale is a linear measurement (one dimension) used to measure or count monotonic events. Arithmetic: an indicator of whether this Timescale contains counted integers or measured real/floating point numbers.
Arithmetic: Real/floating point
+ StartCount: the lowest value in a Timescale. The data type of this attribues is specified by the ‘arithmetic’ attribute.
Optional name for the Unit of Measure
+ EndCount: the greatest value in a Timescale. The data type of this attribues is specified by the ‘arithmetic’ attribute.
Optional Start time or measure
+
+
+ In addition to the attributes, the Timescale class matains associations with two other classes to complete its definition. Clock: A Timescale ‘has a’ one clock. This is the process which generates the ‘tick’ which is counted or measured for the Timescale.
Optional End time or measure
+ UnitOfMeasure: A timescale ‘has a’ one UnitOfMeasure. This class specifies the units of the clock measurement as well as the direction of increase of that measurement.
Optional notations
+
+ A Clock represents the process which generates the ‘tick’ which is counted or measured for a Timescale. Clock has one attribute: Tick definition: a description of the process which is being used to generate nonotonic events.
Example 1 A long, deep, ice core is retrieved from a stable ice-sheet. From long term meteorological observations, the rate of accumulation of ice is known, so linear length can be equated to time (assuming a stable climate too). This enables the dates of some previously unknown large scale volcanic eruptions to be identified and timed. Identifiable nuclear fallout from specific atmospheric atomic bomb tests detected in the ice core increase the confidence in the timing accuracy. Example 1 Example 2 A long, deep, sediment core is extracted from the bottom of a lake with a long geological history. Two layers in the core are dated using radiocarbon dating. Assuming steady rates of sediment deposition, a continuous timescale can be interpolated between the dated layers, and extrapolated before and after the dated layers. Example 2 Calendars combine different timescales and their clocks and units of measure, and other events, to make a complex timeline against which events can be compared. Calculated algorithms are used to determine which instants of intervals on the compound timescale are identified and labeled. Name/id
- Optional location, time or domain of applicability
- Optional Epoch, defined in some temporal reference system
- Astronomical Type (e.g. solar, sidereal, lunar, luni-solar)
- Predictive type (e.g. observed or calculated)
- Optional Start time
- Optional End time
- Constituent units or clocks and counts or timescales
- Algorithms to link constituent timescales
- Optional notations
+ The Direction attribute indicates whether counts or measures increase in the positive (future) or negative (past) direction. The attribute could be part of ‘Timescale’ or ‘TemporalCoordinateReferenceSystem’ rather than a separate class ‘UnitOfMeasure’, but on balance, it seems better here, as the names often imply directionality, such as fathoms increasing downwards, MYA (Millions of Years Ago) increasing earlier, Atmospheric Pressure in hPa (Hectopascals) decreasing upwards, and FL (FlightLevel) increasing upwards. Direction: indicates the direction in which a timescale progresses as new ‘ticks’ are counted or measured.
Example 1 The modern Gregorian calendar is calculated solar calendar, with various epochs from 1588 CE through to 1922 CE depending on location or country. Example The number of the years before the Current Era (BCE, previously known as BC) increase further back in time, whereas the number of the years in the Current Era (CE, previously known as AD) increase further into the future. This is an example of two timescales, adjacent but with no overlap. If there was a year zero defined, they could be replaced with one continuous timescale. Example 1 A long, deep ice core is retrieved from a stable ice-sheet. From long term meteorological observations, the rate of accumulation of ice is known, so linear length can be equated to time (assuming a stable climate too). This enables the dates of some previously unknown large scale volcanic eruptions to be identified and timed. Identifiable nuclear fallout from specific atmospheric atomic bomb tests detected in the ice core increase the confidence in the timing accuracy. Example 2 A long, deep, sediment core is extracted from the bottom of a lake with a long geological history. Two layers in the core are dated using radiocarbon dating. Assuming steady rates of sediment deposition, a continuous timescale can be interpolated between the dated layers, and extrapolated before and after the dated layers. The constituent timescales are days (earth’s rotations), months (moon’s orbit around the earth), years (earth’s orbit around the sun) and seconds determined by atomic clocks. To accommodate discrepancies, leap days and leap seconds are intercalated in some years. The commonest notations for the Gregorian calendar are ISO 8601 and its various restrictive profiles. Example 3 A well preserved fossilised log is recovered and the tree rings establish an annual ‘tick’. The start and end times may be known accurately by comparison and matching with other known tree ring sequences, or perhaps only dated imprecisely via Carbon Dating, or its archaeological or geological context. Example 2 The modern Islamic calendar is an observed lunar calendar, and the major religious dates progress throughout the year, year on year. The important months are determined by the observation of new moons from Mecca. Example 4 A clock is started, but undergoes a calibration process against some standard clock, so the initial, reliable Start Time does not start at Count Zero. The clock is accidentially knocked so that it is no longer correctly caliabrated, but is still working. the End Time is not the last time that the clock ticks. Example 3 The modern Jewish calendar is a calculated luni-solar calendar, and discrepancies in the solar year are addressed by adding ‘leap months’ every few years. Example 5 TAI (International Atomic Time, Temps Atomique International) is coordinated by the BIPM (International Bureau of Weights and Measures, Bureau International de Poids et Measures) in Paris, France. It is based on the average of hundreds of separate atomic clocks around the world, all corrected to be at mean sea level and standard pressure and temperature. The epoch is defined by Julian Date 2443144.5003725 (1 January 1977 00:00:32.184). Example 4 The Ba’hai calendar is a calculated solar calendar, but without any other astronomical aspects. The year consists of 19 months of 19 days each, with 4 or 5 intercalated days for a new year holiday. Example 6 The Julian Day is the continuous count of days (rotations of the Earth with respect to the Sun) since the beginning of the year 4173 BCE and will terminate at the end of the year 3267 CE. The count then starts again as “Period 2”. Many computer based timescales, such as Unix Time, are based on the Julian Day timescale, but with different epochs, to fit the numbers into the limited computer words. Example 5 The West African Yoruba traditional calendar is a solar calendar with months, but rather than subdividing a nominal month of 28 days into 4 weeks, 7 weeks of 4 days are used. This perhaps gave rise to the fortnightly (every 8 days) markets in many villages in the grasslands of north-west Cameroon. The Epoch class provides a origin or datum for a Temporal Reference System. Example 6 If there are two or more clocks, stationary with respect to each other, and a practical method of communicating their times to each other, the clocks can be perfectly synchronized. However, if the clocks are moving with respect to each other, they cannot be precisely coordinated (unless the communication is instantaneous). As communication speed is limited by the finite constant speed of light, perfect synchronisation is not possible, though repetitive protocols can be used to reduce the synchronization error to any practical desired level. See A Brief History of Timekeeping page=”187-191”. See A Brief History of Timekeeping, pages 187-191. The geospatial community has often used analogies between space and time to construct ‘temporal-geometry’. This analogy is useful but can be misleading and must not be taken too far. For example, taken from A Treatise on Time and Space by J R Lucas: 1.1 A thing cannot be in two places at one time; 1.2 A thing can be in one place at two times; 2.1 Two things cannot be in the same place at the same time; 2.2 Two things can be in the same place at different times. These are not symmetrical in space and time. Temporal constructs such as instants, durations or intervals, multi-instants (a set of instants), and multi-intervals are not included in this conceptual model. These do have strongly analogous equivalents in space, such as points and multi-points, especially in a single dimension, such as vertical. The temporal constructs are well described in Maintaining Knowledge about Temporal Intervals by J. F. Allen and apply across all of the regimes, so do not need to be in this Abstract Conceptual Model.
A.1. compound coordinate reference system coordinate reference system using at least two independent coordinate reference systems Note 1 to entry: Coordinate reference systems are independent of each other if coordinate values in one cannot be converted or transformed into coordinate values in the other. [SOURCE: ISO 19111] one of a sequence of numbers designating the position of a point Note 1 to entry: In a spatial coordinate reference system, the coordinate numbers are qualified by units. [SOURCE: ISO 19111] epoch to which coordinates in a dynamic coordinate reference system are referenced epoch to which coordinates in a dynamic coordinate reference system are referenced [SOURCE: ISO 19111] A.4. derived coordinate reference system coordinate reference system that is defined through the application of a specified coordinate conversion to the coordinates within a previously established coordinate reference system A.3. derived coordinate reference system coordinate reference system that is defined through the application of a specified coordinate conversion to the coordinates within a previously established coordinate reference system Note 1 to entry: The previously established coordinate reference system is referred to as the base coordinate reference system. Note 2 to entry: A derived coordinate reference system inherits its datum or reference frame from its base coordinate reference system. Note 3 to entry: The coordinate conversion between the base and derived coordinate reference system is implemented using the parameters and formula(s) specified in the definition of the coordinate conversion. [SOURCE: ISO 19111] Note 1 to entry: The previously established coordinate reference system is referred to as the base coordinate reference system. Note 2 to entry: A derived coordinate reference system inherits its datum or reference frame from its base coordinate reference system. Note 3 to entry: The coordinate conversion between the base and derived coordinate reference system is implemented using the parameters and formula(s) specified in the definition of the coordinate conversion. [SOURCE: ISO 19111] A.5. dynamic coordinate reference system coordinate reference system that has a dynamic reference frame A.4. dynamic coordinate reference system coordinate reference system that has a dynamic reference frame Note 1 to entry: Coordinates of points on or near the crust of the Earth that are referenced to a dynamic coordinate reference system may change with time, usually due to crustal deformations such as tectonic motion and glacial isostatic adjustment. Note 2 to entry: Metadata for a dataset referenced to a dynamic coordinate reference system should include coordinate epoch information. [SOURCE: ISO 19111] Note 1 to entry: Coordinates of points on or near the crust of the Earth that are referenced to a dynamic coordinate reference system may change with time, usually due to crustal deformations such as tectonic motion and glacial isostatic adjustment. Note 2 to entry: Metadata for a dataset referenced to a dynamic coordinate reference system should include coordinate epoch information. [SOURCE: ISO 19111] dynamic datum ADMITTED dynamic datum ADMITTED reference frame in which the defining parameters include time evolution reference frame in which the defining parameters include time evolution [SOURCE: ISO 19111] [SOURCE: ISO 19111] A.7. engineering coordinate reference system coordinate reference system based on an engineering datum A.6. engineering coordinate reference system coordinate reference system based on an engineering datum Example 1 System for identifying relative positions within a few kilometres of the reference point, such as a building or construction site. Example 2 Example 3 Internal coordinate reference system for an image. This has continuous axes. It may be the foundation for a grid. Example 1 System for identifying relative positions within a few kilometres of the reference point, such as a building or construction site. Example 2 Example 3 Internal coordinate reference system for an image. This has continuous axes. It may be the foundation for a grid. local datum ADMITTED local datum ADMITTED datum describing the relationship of a coordinate system to a local reference datum describing the relationship of a coordinate system to a local reference [SOURCE: ISO 19111] [SOURCE: ISO 19111] epoch of coordinates that define a dynamic reference frame epoch of coordinates that define a dynamic reference frame [SOURCE: ISO 19111] A.10. linear coordinate system one-dimensional coordinate system in which a linear feature forms the axis one-dimensional coordinate system in which a linear feature forms the axis Example 1 Example 2 Depths down a deviated oil well bore. Example 1 Example 2 [SOURCE: ISO 19111] A.11. parameter reference epoch epoch at which the parameter values of a time-dependent coordinate transformation are valid A.10. parameter reference epoch epoch at which the parameter values of a time-dependent coordinate transformation are valid Note 1 to entry: The transformation parameter values first need to be propagated to the epoch of the coordinates before the coordinate transformation can be applied. [SOURCE: ISO 19111] Note 1 to entry: The transformation parameter values first need to be propagated to the epoch of the coordinates before the coordinate transformation can be applied. [SOURCE: ISO 19111] A.12. parametric coordinate reference system coordinate reference system based on a parametric datum A.11. parametric coordinate reference system coordinate reference system based on a parametric datum [SOURCE: ISO 19111] A.13. parametric coordinate system one-dimensional coordinate system where the axis units are parameter values which are not inherently spatial A.12. parametric coordinate system one-dimensional coordinate system where the axis units are parameter values which are not inherently spatial [SOURCE: ISO 19111] datum describing the relationship of a parametric coordinate system to an object datum describing the relationship of a parametric coordinate system to an object [SOURCE: ISO 19111] [SOURCE: ISO 19111] coordinate operation that changes coordinates within one coordinate reference system due to the motion of the point coordinate operation that changes coordinates within one coordinate reference system due to the motion of the point Note 1 to entry: The change of coordinates is from those at an initial epoch to those at another epoch. Note 2 to entry: In this document the point motion is due to tectonic motion or crustal deformation. [SOURCE: ISO 19111] Note 1 to entry: The change of coordinates is from those at an initial epoch to those at another epoch. Note 2 to entry: In this document the point motion is due to tectonic motion or crustal deformation. [SOURCE: ISO 19111] A.16. spatio-parametric coordinate reference system compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a parametric coordinate reference system A.15. spatio-parametric coordinate reference system compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a parametric coordinate reference system Note 1 to entry: Normally the spatial component is “horizontal” and the parametric component is “vertical”. [SOURCE: ISO 19111] Note 1 to entry: Normally the spatial component is “horizontal” and the parametric component is “vertical”. [SOURCE: ISO 19111] A.17. spatio-parametric-temporal coordinate reference system compound coordinate reference system comprised of spatial, parametric and temporal coordinate reference systems A.16. spatio-parametric-temporal coordinate reference system compound coordinate reference system comprised of spatial, parametric and temporal coordinate reference systems [SOURCE: ISO 19111] A.18. spatio-temporal coordinate reference system compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a temporal coordinate reference system A.17. spatio-temporal coordinate reference system compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a temporal coordinate reference system [SOURCE: ISO 19111] A.19. static coordinate reference system coordinate reference system that has a static reference frame A.18. static coordinate reference system coordinate reference system that has a static reference frame Note 1 to entry: Coordinates of points on or near the crust of the Earth that are referenced to a static coordinate reference system do not change with time. Note 2 to entry: Metadata for a dataset referenced to a static coordinate reference system does not require coordinate epoch information. [SOURCE: ISO 19111] Note 1 to entry: Coordinates of points on or near the crust of the Earth that are referenced to a static coordinate reference system do not change with time. Note 2 to entry: Metadata for a dataset referenced to a static coordinate reference system does not require coordinate epoch information. [SOURCE: ISO 19111] reference frame in which the defining parameters exclude time evolution reference frame in which the defining parameters exclude time evolution [SOURCE: ISO 19111] A.21. terrestrial reference system TRS ADMITTED A.20. terrestrial reference system TRS ADMITTED set of conventions defining the origin, scale, orientation and time evolution of a spatial reference system co-rotating with the Earth in its diurnal motion in space set of conventions defining the origin, scale, orientation and time evolution of a spatial reference system co-rotating with the Earth in its diurnal motion in space Note 1 to entry: The abstract concept of a TRS is realised through a terrestrial reference frame that usually consists of a set of physical points with precisely determined coordinates and optionally their rates of change. In this document terrestrial reference frame is included within the geodetic reference frame element of the data model [SOURCE: ISO 19111] Note 1 to entry: The abstract concept of a TRS is realised through a terrestrial reference frame that usually consists of a set of physical points with precisely determined coordinates and optionally their rates of change. In this document terrestrial reference frame is included within the geodetic reference frame element of the data model [SOURCE: ISO 19111]
[1] Jean Meeus. Astronomical Algorithms. https://www.agopax.it/Libri_astronomia/pdf/Astronomical%20Algorithms.pdf [2] Bureau International des Poids et Mesures (BIPM). Establishment of International Atomic Time and Coordinated Universal Time. https://www.bipm.org/documents/20126/59466374/6_establishment_TAR20.pdf/5b18b648-0d5a-ee02-643d-a60ed6c148fc [3] CEN: Env 1613:1995 Medical informatics — Messages for exchange of laboratory information, 1995 [4] Chad Orzell. A Brief History of Timekeeping. Oneworld Publications. 2022. ISBN-13: 978-0-86154-321-2. [5] ISO/TC 211: ISO 19108:2002 Geographic information — Temporal schema, 2021, https://www.iso.org/standard/26013.html [6] Lorentz Transform. Wolfram MathWorld. https://mathworld.wolfram.com/LorentzTransformation.html [7] H. Minkowski. Space and Time, Minkowski’s Papers on RelativityMinkowski Institute Press, Montreal 2012. https://minkowskiinstitute.org/ebookstore [8] The Open Group. UNIX Time. https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_16 [last accessed 2023-01] [1] Jean Meeus. Astronomical Algorithms. https://www.agopax.it/Libri_astronomia/pdf/Astronomical%20Algorithms.pdf [2] Bureau International des Poids et Mesures (BIPM). Establishment of International Atomic Time and Coordinated Universal Time. https://www.bipm.org/documents/20126/59466374/6_establishment_TAR20.pdf/5b18b648-0d5a-ee02-643d-a60ed6c148fc [3] Nachum Dershowitz, Edward M. Reingold. Calendrical Calculations — The Ultimate Edition. Cambridge University Press. 2018. ISBN-13: 978-1107683167. http://emr.cs.iit.edu/home/reingold/calendar-book/third-edition [last accessed 2023-01] [4] Chad Orzell. A Brief History of Timekeeping. Oneworld Publications. 2022. ISBN-13: 978-0-86154-321-2. [5] ISO/TC 211: ISO 19108:2002 Geographic information — Temporal schema, 2021, https://www.iso.org/standard/26013.html [6] OGC: GeoPose Specification draft, 2021, https://github.com/opengeospatial/GeoPose/ [7] Lorentz Transform. Wolfram MathWorld. https://mathworld.wolfram.com/LorentzTransformation.html [8] H. Minkowski. Space and Time, Minkowski’s Papers on RelativityMinkowski Institute Press, Montreal 2012. https://minkowskiinstitute.org/ebookstore [9] J R Lucas. A Treatise on Time and Space. Methuen and Co. Ltd. 1973. ISBN 0-416-84190-2. [10] The Open Group. UNIX Time. https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_16 [last accessed 2023-01]II. Keywords
IV. Security Considerations
V. Submitting Organizations
4. Terms and definitions
5. Conventions
5.1. Abbreviated terms
@@ -3227,17 +3231,12 @@ minimum necessary to define data structures to full object implementation.
7. Temporal Abstract Conceptual Model
-
class ReferenceSystem {
<<abstract>>
dimension = 1..*
applicableLocationTimeOrDomain
}
class SpatialReferenceSystem {
<<abstract>>
dimension = 1..*
applicableLocationTimeOrDomain
}
class TemporalReferenceSystem {
<<abstract>>
dimension = 1
applicableLocationTimeOrDomain
}
note for ReferenceSystem "Note: Has at least one of:\nSpatialReferenceSystem, or \nTemporalReferenceSystem"
ReferenceSystem <|-- SpatialReferenceSystem : is a
ReferenceSystem <|-- TemporalReferenceSystem : is a
class OrdinalTemporalReferenceSystem {
dimension = 1
applicableLocationTimeOrDomain
}
class TemporalCoordinateReferenceSystem {
dimension = 1
applicableLocationTimeOrDomain
}
class Calendar {
dimension = 1
applicableLocationTimeOrDomain
}
note for TemporalReferenceSystem "Note: Consists of one only of:\nTemporalCoordinateReferenceSystem,\nCalendar, or \nOrdinalTemporalReferenceSystem"
TemporalReferenceSystem <|-- OrdinalTemporalReferenceSystem : is a
TemporalReferenceSystem <|-- TemporalCoordinateReferenceSystem : is a
TemporalReferenceSystem <|-- Calendar : is a
OrdinalTemporalReferenceSystem "1" o-- "(ordered)" Events : consists of
OrdinalTemporalReferenceSystem "1" o-- "0..1" Epoch : has an
OrdinalTemporalReferenceSystem "1" --> "1..*" Notation : can use
TemporalCoordinateReferenceSystem "1" o-- "1" Epoch : has an
TemporalCoordinateReferenceSystem "1" --> "1..*" Notation : can use
TemporalCoordinateReferenceSystem "1" o-- "1" Timescale : has a
Calendar "1" o-- "0..1" Epoch : has an
Calendar "1" --> "1..*" Notation : can use
Calendar "1" o-- "1..*" Timescale : has a
Calendar "1" o-- "1..*" Algorithm : has a
class Timescale {
StartCount
EndCount
arithmetic
}
Timescale "1" o-- "1" Clock : has a
Timescale "1" o-- "1" UnitOfMeasure : has a
class Clock {
Tick definition
}
class UnitOfMeasure {
Direction
}8. Temporal regimes
@@ -3257,7 +3256,7 @@ the Mermaid container with the following.
8.5. Calendars
8.6. Other Regimes
@@ -3320,31 +3322,36 @@ the Mermaid container with the following.
8.6.2. Space-time
+8.6.2. Astronomical Time
-8.6.3. Space-time
-8.6.3. Relativistic
+8.6.4. Relativistic
-8.6.4. Accountancy
+8.6.5. Accountancy
-10. Attributes of the Regimes/Classes
- 10.1. Attributes of Events and Ordinal Temporal Reference Systems
+ 10. Attributes of the Classes
+ 10.1. Reference Systems
+
+10.2. Ordinal Temporal Reference Systems
-10.2.1. Events
+
+10.3. Temporal Coordinate Reference System
-10.4. Calendar Reference Systems
+
+10.3. Attributes of Clocks
-
-10.4. Attributes of Timescales
+10.4.2. Algorithm
-10.4.3. Calendar Examples
+
+10.5. Attributes of Units of Measure
-10.5. Discrete and Continuous Time Scales
-10.5.1. Timescale
+
+10.5.2. Clock
+
+10.7. Attributes of Calendars
-10.5.3. UnitOfMeasure
-10.5.4. Time Scale Examples
+
+10.6. Supporting Classes
+
+10.6.1. Epoch
-11. Synchronisation of clocks
12. Temporal Geometry
+
Annex A
(informative)
Glossary
Bibliography
-