Skip to content

Commit

Permalink
chore: filename cleanups for 23-050
Browse files Browse the repository at this point in the history
  • Loading branch information
ronaldtse committed Mar 5, 2025
1 parent 0aa0aaa commit ca6e246
Show file tree
Hide file tree
Showing 9 changed files with 316 additions and 315 deletions.
18 changes: 14 additions & 4 deletions 23-050/23-050.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,12 @@
:referenceURLID: http://docs.opengeospatial.org/as/23-050/23-050.html
:fullname: Chris Little
:fullname_2: Charles Heazel
:fullname_3: Ronald Tse
:role: editor
:role_2: editor
:role_3: editor
:keywords: ogcdoc, OGC document, abstract specification, conceptual model, time, temporal referencing, referencing by coordinates, calendar, clock, timescale
:submitting-organizations: U.K. Met Office, HeazelTech
:submitting-organizations: U.K. Met Office, HeazelTech, Ribose Inc.
:mn-document-class: ogc
:mn-output-extensions: html,pdf,rxl
:local-cache-only:
Expand All @@ -38,12 +40,20 @@ include::sections/05-conventions.adoc[]
include::sections/06-abstract_model.adoc[]

// include::sections/07-formal_abstract_model.adoc[]
include::sections/07-temporal_abstract_model.adoc[]

// include::sections/08-data_dictionary.adoc[]
include::sections/08-temporal_regimes.adoc[]

// Annexes (add annex files as needed)
include::sections/aa-annexA.adoc[]
include::sections/09-notation.adoc[]

include::sections/10-attributes.adoc[]

include::sections/11-sync-clocks.adoc[]

// TODO: RT: propose to use dynamic generation of MBS
include::sections/12-data_dictionary.adoc[]

// Annexes (add annex files as needed)
include::sections/annex-ISO-glossary.adoc[]

// Bibliography should be the last annex
Expand Down
1 change: 1 addition & 0 deletions 23-050/sections/00-preface.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ h| Name h| Affiliation

| Chris Little (editor) | U.K. Met Office
| Chuck Heazel | HeazelTech
| Ronald Tse | Ribose Inc.

|===

Expand Down
301 changes: 0 additions & 301 deletions 23-050/sections/06-abstract_model.adoc

Large diffs are not rendered by default.

11 changes: 11 additions & 0 deletions 23-050/sections/07-temporal_abstract_model.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
== Temporal Abstract Conceptual Model

This attempt at a Temporal Abstract Conceptual Model follows <<iso19111>>, which is the ISO adoption of <<ogc18005r4>>.

The model is also informed by <<W3COWLTime>>.

[plantuml]
....
include::../plantuml_diagrams/TemporalAbstractConceptualModel.puml[]
....

102 changes: 102 additions & 0 deletions 23-050/sections/08-temporal_regimes.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,102 @@
== Temporal regimes

=== General

To help us think more clearly about time, this paper adopts the term “Regime” to describe the fundamentally different types of time and its measurement under consideration. This is a pragmatic approach that allows the grouping of recommendations and best practices in a practical way, but without obscuring the connection to the underlying theoretical components.

The first three regimes have deep underlying physical and mathematical foundations which cannot be legislated away. The fourth regime, of calendars, uses a seemingly random mixture of ad hoc algorithms, arithmetic, numerology and measurements. Paradoxically, this regime has historically driven advances in mathematics and physics.

The regimes are applicable to other planets and outer space, but with due consideration.

=== Events and Operators

The simplest way of relating entities in time is by events that can be ordered, that is, established in a sequence, and this sequence is used as an approximate measure of the passage of time.

In this regime, no clocks or time measurements are defined, only events, that are ordered in relation to each other. For example, geological layers, sediment or ice core layers, archaeological sequences, sequential entries in computer logs without coordinated time.

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 (<<temporal_knowledge>>) 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.

=== Simple Clocks and Discrete Timescales

In this regime, a clock is defined as any regularly repeating physical phenomena, such as pendulum swings, earth's rotation about sun, earth's rotation about its axis, heart beats, vibrations of electrically stimulated quartz crystals or the resonance of the unperturbed ground-state hyperfine transition frequency of the caesium 133 atom. Some phenomena make better clocks that others, in terms of the number of repetitions possible, the consistency of each repetition and the precision of each 'tick'. A mechanism for counting, or possibly measuring, the ticks is desirable.

It is an assumption that the ticks are regular and homogeneous.

There is no sub-division between two successive clock ticks. Measuring time consists of counting the complete number of repetitions of ticks since the clock started, or since some other event at a given clock count.

There is no time measurement before the clock started, or after it stops.

It may seem that time can be measured between 'ticks' by interpolation, but this needs another clock, with faster ticks. This process of devising more precise clocks continues down to the atomic scale, and then the deterministic process of physically trying to interpolate between ticks is not possible.

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 (<<temporal_knowledge>>) 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.

=== CRS and Continuous Timescales

This regime takes a clock from the previous regime and assumes that between any two adjacent ticks, it is possible to interpolate indefinitely to finer and finer precision, using ordinary arithmetic, rather than any physical device. Units of Measure may be defrined that are different from the 'ticks'. For example, a second may be defined as 9,192,631,770 vibrations of the ground-state hyperfine transition of the caesium 133 atom. Alternatively and differently, a second may be defined as 1/86400th of the toataion of the earth on its axis with respect to the sun. The count of rotations are the 'ticks' of an earth-day clock. This latter definition is not precise enough for many uses, as the rotaion of the earth on its axis varies from day to day.

Alternatively, it may be that the ticks are not counted but measured, and the precision of the clock is determined by the precision of the measurements, such as depth in an ice core, or angular position of an astronomical body,such as the sun, moon or a star.

It is also assumed that time can be extrapolated to before the time when the clock started and into the future, possibly past when the clock stops.

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 (<<temporal_knowledge>>) 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.

Some examples are:

* Unix milliseconds since 1970-01-01T00:00:00.0Z
* Julian Days, and fractions of a day, since noon on 1st January, 4713 BCE.

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.

=== Calendars

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.

This paper only addresses the internationally agreed Gregorian calendar. <<astro_algo>> 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.

=== Other Regimes

There are other regimes, which are out of scope of this document. This could include local solar time, useful, for example, for the calculation of illumination levels and the length of shadows on aerial photography, or relativistic time.


==== Local Solar Time

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.

==== Space-time

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 <<minkowski,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.

==== Relativistic

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_transform,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.

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.

==== Accountancy

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.

7 changes: 7 additions & 0 deletions 23-050/sections/09-notation.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
== Notation

There are often widely agreed, commonly accepted, notations used for temporal reference systems, but few have been standardised. Any particular notation may be capable of expressing a wider range of times than are valid for the reference system.

[example]
The <<rfc3339>> timestamp notation, a restrictive profile of <<iso8601>>, can express times before 1588CE, when the Gregorian calendar was first introduced in some parts of the world.

Loading

0 comments on commit ca6e246

Please sign in to comment.