Merge pull request #97 from opengeospatial/Chucks-Updates

Chucks updates, to meet 3 week rule.

23-049/23-049.adoc

@@ -4,10 +4,10 @@
 :status: swg-draft
 :committee: technical
 :edition: 1.0
-:docnumber: 23-049r1
+:docnumber: 23-049r2
 :received-date: 2023-05-23
-:issued-date: 2024-02-14
-:published-date: 2024-02-14
+:issued-date: 2024-03-07
+:published-date: 2024-03-07
 :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

23-049/sections/07-cm.adoc

@@ -5,87 +5,5 @@ This Temporal Abstract Conceptual Model follows <<iso19111>>, which is the ISO a
 
 The model is also informed by the <<w3cowltime,W3C Time Ontology in OWL>>.
 
-[plantuml]
-....
-@startuml
-abstract class ReferenceSystem {
-        dimension "dimension >= 1"
-        locationOfApplicability = 0..1
-        timeOfApplicability = 0..1
-        domainOfApplicability = 0..1
-}
-
-note right of ReferenceSystem
-Note: Has at least one of:
-* SpatialReferenceSystem, or
-* TemporalReferenceSystem
-end note
-
-abstract class SpatialReferenceSystem {
-}
-
-abstract class TemporalReferenceSystem {
-  dimension = 1
-}
-
-note left of TemporalReferenceSystem
-Note: Consists of one only of:
-* TemporalCoordinateReferenceSystem,
-* Calendar, or
-* OrdinalTemporalReferenceSystem
-end note
-
-ReferenceSystem <|-- SpatialReferenceSystem : is a
-ReferenceSystem <|-- TemporalReferenceSystem : is a
-
-class OrdinalTemporalReferenceSystem {
-}
-class TemporalCoordinateReferenceSystem {
-}
-class Calendar {
-}
-class Timeline {
-}
-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 : anchored by
-OrdinalTemporalReferenceSystem "1" --> "1..*" Notation : is represented by
-TemporalCoordinateReferenceSystem "1" o-- "1" Epoch : anchored by
-TemporalCoordinateReferenceSystem "1" --> "1..*" Notation : is represented by
-TemporalCoordinateReferenceSystem "1" o-- "1" Timescale : must have
-
-Calendar "1" o-- "0..1" Epoch : anchored by
-Calendar "1" --> "1..*" Notation : is represented by
-Calendar "1" o-- "1" Timeline : has a
-
-Timeline "1" o-- "1..*" Algorithm : defined by
-
-class Timescale {
-  StartCount
-  EndCount
-  arithmetic
-}
-
-Timescale "1" o-- "1" Clock : determined by
-Timescale "1" o-- "1" UnitOfMeasure : has a
-
-class Clock {
-}
-Clock "1" o-- "1..*" Ticks : counts
-class Ticks {
-    }
-
-class UnitOfMeasure {
-  Direction
-}
-
-class Algorithm {
-} 
-Algorithm "1" o-- "2..*" Timescale : uses
-
-@enduml
-
-....
+[[fig-UML-diagram]]
+image::./images/Figure1Mermaid.JPG[align="center"]

23-049/sections/12-temporal-geometry.adoc

@@ -13,3 +13,4 @@ The geospatial community has often used analogies between space and time to cons
 These statements are not symmetrical between space and time.
 
 Temporal constructs such as instants, durations or intervals, multi-instants (a set of instants), and multi-intervals (a set of 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 <<temporal_knowledge,Maintaining Knowledge about Temporal Intervals by J. F. Allen>> (see <<fig-interval-relations>>) and apply across all of the regimes, so do not need to be in this Abstract Conceptual Model.
+

23-049/sections/annex-bibliography.adoc

@@ -1,6 +1,5 @@
 
 [appendix,obligation="informative"]
-[[annex-bibliography]]
 [bibliography]
 == Bibliography
 
@@ -104,3 +103,8 @@ https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended[https://dat
 The Library of Congress: 
 _Extended Date/Time Format (EDTF) Specification_. (2019).
 https://www.loc.gov/standards/datetime[https://www.loc.gov/standards/datetime]. [last accessed 2024-02]
+
+* [[[mih, Motion Imagery Handbook]]]
+Motion Imagery Standards Board:
+_Motion Imagery Standards Profile-2023.2: Motion Imagery Handbook, Chapter 6_. (March 2023), 
+https://nsgreg.nga.mil/doc/view?i=5470[https://nsgreg.nga.mil/doc/view?i=5470]. [last accessed 2024-03]

23-049/sections/annex-examples.adoc

@@ -1,7 +1,7 @@
 [appendix,obligation="informative"]
 [[annex-examples]]
-[examples]
 == Examples
+
 These show how the concepts of the Abstract Cocenptual Model for Time can be applied to realistic use cases. Of course, the logical and implementation details are outside the scope of this standard.
 
 === Ordinal Temporal Reference System
@@ -10,15 +10,15 @@ Geological eras and periods are forms of compound ordinal reference systems. A c
 
 Another consistent sequence of strata from another region can also form another ordinal temporal reference system. It may be possible to relate the two systems to each other because of layers that may share specific varieties of fossils, or a specific distinctive stratum type.
 
-Figure 2 shows how the four different geological ordinal temporal reference systems of sequences of rocks and fossils, called Periods, from west Wales (Ordovician), south Wales (Silurian), Devon (Devonian), and coal-bearing rocks (Carboniferous) have been combined to define a longer geological ordinal temporal reference system called the Paleozoic Era.
+Figure A.1 shows how the four different geological ordinal temporal reference systems of sequences of rocks and fossils, called Periods, from west Wales (Ordovician), south Wales (Silurian), Devon (Devonian), and coal-bearing rocks (Carboniferous) have been combined to define a longer geological ordinal temporal reference system called the Paleozoic Era.
 
 [[fig-geological-ordinal-example]]
 image::images/GeologicalOrdinalExample.jpg[]
 
 === Temporal Coordinate Reference System
-1. A remote autonomous underwater drone, known as a 'glider' is making regular measurements of temperature and salinity deep in the Atlantic Ocean. The measurements are time-stamped by an on-board computer clock. The clock was synchronized to a satellite's atomic clock when the drone was launched. When the drone surfaces to report its findings, or to be picked up by a research vessel, it is found that the computer clock as 'drifted' compared to time from the satellite. The drone's clock is assumed to have 'drifted' in a consistent, linear, fashion, and the error correction is distributed proportionately along the time series of measurements.
+1. A remote autonomous underwater drone, known as a 'glider' is making regular measurements of temperature and salinity deep in the Atlantic Ocean. The measurements are time-stamped by an on-board computer clock. The clock was synchronized to a satellite's atomic clock when the drone was launched. When the drone surfaces to report its findings, or to be picked up by a research vessel, it is found that the computer clock has 'drifted' compared to time from the satellite. The drone's clock is assumed to have 'drifted' in a consistent, linear, fashion, and the error correction is distributed proportionately along the time series of measurements.
 
-2. Several timescales have been defined using the same atomic clocks. For various reasons, such as the year of starting, or the need to store numbers in limited length computer words, different epochs have been chosen. This is illustrated in Figure 3. The figure also illustrates how UTC is not a timescale, but a timeline, as it has been adjusted with leap seconds to correspond to the Gregorian calendar and not deviate more than 0.6 seconds from Earth's actual day length. This is because UTC is based on the atomic definition of a second, the SI second, whereas the Gregorian calendar assumes that a day, based on Earth's rotation with respect to the sun, is 86,400 seconds, but this daily rotation varies in duration every day throughout the year for a variety of reasons. 
+2. Several timescales have been defined using the same atomic clocks. For various reasons, such as the year of starting, or the need to store numbers in limited length computer words, different epochs have been chosen. This is illustrated in Figure A.2. The figure also illustrates how UTC is not a timescale, but a timeline, as it has been adjusted with leap seconds to correspond to the Gregorian calendar and not deviate more than 0.6 seconds from Earth's actual day length. This is because UTC is based on the atomic definition of a second, the SI second, whereas the Gregorian calendar assumes that a day, based on Earth's rotation with respect to the sun, is 86,400 seconds, but this daily rotation varies in duration every day throughout the year for a variety of reasons. 
 
 [[fig-differing-timecales]]
 image::images/MISB_Figure_36.png[]
@@ -31,5 +31,7 @@ Months are not useful as there are two small fast moving moons. One orbits three
 The 'day', the rotation of Mars on its axis with respect to the Sun, is the other timescale that comprises the Mars calendar. To avoid confusion with Earth's days, they are called 'Sols'. This solar day, with a similar definition to an Earth day, would be useful for planning day time and night time activities, pehaps requiring solar power generation.
 
 Other definitions of a day could have been adopted:
+
 1. A sidereal Mars day, the rotation of Mars with respect to the distant stars, like the sidereal day on Earth. This could be useful if the rover was performing astronomical measurements, such as for navigating using the equivalent of a sextant;
+
 2. An Earth orientated day, the rotation of Mars with respect to Earth in its orbit. This could be useful for planning activities needing extended communication periods with direct line-of-sight with Earth.