From ce356c100e50abe27ea31a2a1456cf91478408e6 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Tue, 15 Aug 2023 18:05:24 +0100 Subject: [PATCH 01/21] Update 06-other-clauses.adoc --- .../sections/06-other-clauses.adoc | 30 +++++++++---------- 1 file changed, 14 insertions(+), 16 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 424a29b9..6c5443b7 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -119,7 +119,7 @@ In this regime, no clocks or time measurements are defined, only events, that ar 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, 'subtracting' Ordovician from Jurassic is meaningless. +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 archaeology, 'subtracting' a layer with a certain type of pottery remains from the layer containg 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. @@ -133,19 +133,19 @@ There is no sub-division between two successive clock ticks. Measuring time cons 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 process of physically trying to interpolate between ticks is not possible. +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 (<>) 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 integer arithmetic operations like (B-A) or (C-A) as we have defined a 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. === CRS and Continuous Timescales -This regime takes a clock from the previous regime ands 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. +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 defined 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 rotation 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 roation 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 ince core, or angular position of an astronomical body,such as the sun, moon or a star. +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. @@ -159,12 +159,11 @@ Some examples are: . Julian Days, and fractions of a day, since noon on 1st January, 4713 BCE. -This regime constitutes a Temporal Coordinate Reference System, with continuous, floating-point, units of measure, which can be subject to the full range of real 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. === 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. +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. @@ -172,13 +171,11 @@ This paper only addresses the internationally agreed Gregorian calendar. <> to support work in Special Relativity, the concept of Spacetime is useful whenever the location of an object in space is dependent on its location in time. +Originally developed by <> to support work in Special Relativity, the concept of spac-etime is useful whenever the location of an object in space is dependent on its location in time. -Since the speed of light in a vacum is a constant, Spacetime 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 orthagonal axis all with the same units of measure. +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 axes 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 may be relevant. -Once off the planet Earth, distances and velocities grow 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 Spacetime events as measured between two moving objects. The core concepts are the <>. 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 grow 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 <>. 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 spatial relativity to be replaced by general relativity, and it can no longer be assumed the space (or space-time) are Euclidean. That is, Pythagoras' Theorem does not hold except locally over small areas. This is somewhat familiar 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. @@ -215,10 +214,9 @@ The <> timestamp notation, a restrictive profile of <>, can express times before 1588CE, when the Gregorian calendar was first introduced in some parts of the world. - == Attributes of the Regimes/Classes -The top level `Reference System` is a super-class and does not have many attributes or properties. So far, only the dimension of the reference system and the Location, Time or Domain of Applicability have been identified as essential. +The top level `Reference System` is an abstract super-class and does not have many attributes or properties. So far, only the dimension of the reference system and the Location, Time or Domain of Applicability have been identified as essential. The Dimension is one for time, or a vertical reference system, but may be as much as 6 for spatial location and orientation. From 3c85a3a18febaf5e124c9e56b231106cfbf77105 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Tue, 15 Aug 2023 18:09:33 +0100 Subject: [PATCH 02/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 6c5443b7..e81e5993 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -175,7 +175,7 @@ A Calendar is a Temporal Reference System, but it is not a Temporal Coordinate R ==== General -There may in be a series of 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. +There may be a series of 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 From bf064894655d9c1c22110210099459a0b1d1b0e5 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Tue, 15 Aug 2023 18:10:45 +0100 Subject: [PATCH 03/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index e81e5993..5ec58dc6 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -185,7 +185,7 @@ Local solar time may or may not correspond to the local statutory or legal 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 <> to support work in Special Relativity, the concept of spac-etime is useful whenever the location of an object in space is dependent on its location in time. +Originally developed by <> to support work in Special Relativity, the concept of spac-etime 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 axes all with the same units of measure, distance. From ae235e4323fb2ef505a82c859dd5b0f03c5274ca Mon Sep 17 00:00:00 2001 From: Chris Little Date: Tue, 15 Aug 2023 18:11:35 +0100 Subject: [PATCH 04/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 5ec58dc6..146b6873 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -185,7 +185,7 @@ Local solar time may or may not correspond to the local statutory or legal 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 <> to support work in Special Relativity, the concept of spac-etime is useful whenever the location of an object in space is dependent on its location in time. +Originally developed by <> 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 axes all with the same units of measure, distance. From 6f74f3e6f9f7b87d84ffd8776e6a2c1b5fb48f16 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Tue, 15 Aug 2023 18:49:50 +0100 Subject: [PATCH 05/21] Update 06-other-clauses.adoc Improved and tweaked attributes of the different regimes to be consistent with agreed diagram --- .../sections/06-other-clauses.adoc | 43 ++++++++++--------- 1 file changed, 23 insertions(+), 20 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 146b6873..21a61637 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -216,9 +216,11 @@ introduced in some parts of the world. == Attributes of the Regimes/Classes -The top level `Reference System` is an abstract super-class and does not have many attributes or properties. So far, only the dimension of the reference system and the Location, Time or Domain of Applicability have been identified as essential. +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 Dimension is one for time, or a vertical reference system, but may be as much as 6 for spatial location and orientation. +The `ReferenceSystem` has two abstract sub-classes: `SpatialReferenceSystem`, which is defined in ISO19111, and `TemporalReferenceSystem`, each with the attributes of Dimension and Domain of Applicabiity. + +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. @@ -230,17 +232,14 @@ Besides the conventional space and time, there may be other reference systems, s . First and last events -. Optional Epoch, defined in some other temporal reference system +. Optional Epoch, defined in some temporal reference system -. Optional location or region of applicability +. Optional location, time or domain of applicability . Optional notations [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. +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 emperor. @@ -250,15 +249,17 @@ Other documents may enable two such 'king lists' to be related, though not compl . Name/Id -. Optional Epoch/starting time defined in some other temporal reference system +. Optional Epoch/starting time defined in some temporal reference system . Optional name for each tick . Optional End time or count -. Optional location +. Optional Unit of Measure and number of ticks per Unit + +. Optional location, time or domain of applicability -. Optional Notation +. Optional notations [example] A well preserved fossilised log is recovered and the tree rings establish an @@ -270,20 +271,20 @@ via Carbon Dating, or its archaeological or geological context. . Name/Id -. Optional Epoch/starting time, defined in some other temporal reference system +. Optional Epoch/starting time, defined in some temporal reference system -. Optional name for the measure +. Optional name for the Unit of Measure . Optional End time or measure -. Optional location +. Optional location, time or domain of applicability -. Optional Notation +. Optional notations [example] A long 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 enable the +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 increase the confidence in the timing accuracy. @@ -296,15 +297,17 @@ tests increase the confidence in the timing accuracy. . Predictive type (e.g. observed or calculated) -. Epoch/start time +. Optional Epoch/starting time, defined in some temporal reference system . Optional end time -. Optional location or region of applicability +. Optional location, time or domain of applicability . Constituent units or clocks and counts or timescales -. Optional Notation +. Algorithms to link constituent timescales + +. Optional Notations [example] The modern Gregorian calendar is calculated solar calendar, with various epochs @@ -335,7 +338,7 @@ astronomical aspects. The year consists of 19 months of 19 days each, with 4 or 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 Cameroun. +markets in many villages in the grasslands of north-west Cameroon. [example] Teams controlling remote vehicles on Mars use a solar calendar, with Martian From 23ef50fb8d1a7b1edc32947ae1448d10a8b837f8 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 14:35:51 +0100 Subject: [PATCH 06/21] Update 06-other-clauses.adoc Relaxed multiplicity of spatial coordinates from 1..3 to 1..* to allow geoposes, parametric, etc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 21a61637..a5979118 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -54,7 +54,7 @@ class ReferenceSystem { } class SpatialReferenceSystem { <> - dimension = 1..3 + dimension = 1..* applicableLocationTimeOrDomain } class TemporalReferenceSystem { From 60342503fbabed378e4a8b76ac9fa421c4166fe6 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 18:35:02 +0100 Subject: [PATCH 07/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index a5979118..2557265f 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -249,10 +249,12 @@ Other documents may enable two such 'king lists' to be related, though not compl . Name/Id -. Optional Epoch/starting time defined in some temporal reference system +. Optional Epoch, defined in some temporal reference system . Optional name for each tick +. Optional Start time or count + . Optional End time or count . Optional Unit of Measure and number of ticks per Unit @@ -267,6 +269,9 @@ 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] +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 accidentally knocked so that it is no longer correctly calibrated, but is still working. The End Time is not the last time that the clock counts. + === Attributes of a CRS and Continuous Timescales . Name/Id From 369e97f14d334a933a933d386d1e6133b7cef19b Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 18:37:00 +0100 Subject: [PATCH 08/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 2557265f..f4fc2614 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -92,8 +92,8 @@ OrdinalTemporalReferenceSystem "1" o-- "0..1" Epoch : has an OrdinalTemporalReferenceSystem "1" o-- "(ordered)" Event : consists of OrdinalTemporalReferenceSystem "1" --> "1..*" Notation : can use class Timescale { - earliestCount - latestCount + StartCount + EndCount arithmetic } Timescale "1" o-- "1" Clock : has a From bc06e6681f01e3f57082e09e11ee6179c927a8e7 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 18:40:20 +0100 Subject: [PATCH 09/21] Update 06-other-clauses.adoc --- .../sections/06-other-clauses.adoc | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index f4fc2614..37a48d4d 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -228,13 +228,13 @@ Besides the conventional space and time, there may be other reference systems, s . Name/Id -. Listed or enumerated sequence of events - -. First and last events +. Optional location, time or domain of applicability . Optional Epoch, defined in some temporal reference system -. Optional location, time or domain of applicability +. Listed or enumerated sequence of events + +. First and last events . Optional notations @@ -249,6 +249,8 @@ Other documents may enable two such 'king lists' to be related, though not compl . Name/Id +. Optional location, time or domain of applicability + . Optional Epoch, defined in some temporal reference system . Optional name for each tick @@ -259,8 +261,6 @@ Other documents may enable two such 'king lists' to be related, though not compl . Optional Unit of Measure and number of ticks per Unit -. Optional location, time or domain of applicability - . Optional notations [example] @@ -276,14 +276,14 @@ A clock is started, but undergoes a calibration process against some standard cl . Name/Id +. Optional location, time or domain of applicability + . Optional Epoch/starting time, defined in some temporal reference system . Optional name for the Unit of Measure . Optional End time or measure -. Optional location, time or domain of applicability - . Optional notations [example] From 785e5ab45b9ea4463b8037406d0ef529f1a02f8f Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 18:57:47 +0100 Subject: [PATCH 10/21] Update 06-other-clauses.adoc --- .../sections/06-other-clauses.adoc | 21 ++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 37a48d4d..87562f69 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -278,41 +278,48 @@ A clock is started, but undergoes a calibration process against some standard cl . Optional location, time or domain of applicability -. Optional Epoch/starting time, defined in some temporal reference system +. Optional Epoch, defined in some temporal reference system . Optional name for the Unit of Measure +. Optional Start time or measure + . Optional End time or measure . Optional notations [example] -A long ice core is retrieved from a stable ice-sheet. From long term +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 increase the confidence in the timing accuracy. +[example] +A long, deep, sediment core is extract from the bottom of a lake with a long geological history. two layers in the core are date using radiocarbon dated. Assuming steady rates of sediment deposition, a continuous timescale can be inerpolated between the dated layers, and extrapolated before and after the dated layers. + == Attributes of Calendars . 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 Epoch/starting time, defined in some temporal reference system +. Optional Start time -. Optional end time - -. Optional location, time or domain of applicability +. Optional End time . Constituent units or clocks and counts or timescales . Algorithms to link constituent timescales -. Optional Notations +. Optional notations [example] The modern Gregorian calendar is calculated solar calendar, with various epochs From 4655e541db0aef432a6d2e0fbf96cfca57f57c8c Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 21:28:30 +0100 Subject: [PATCH 11/21] Update 06-other-clauses.adoc add attributes and examples of timescales and clocks --- .../sections/06-other-clauses.adoc | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 87562f69..f7b8d9dc 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -357,6 +357,40 @@ Teams controlling remote vehicles on Mars use a solar calendar, with Martian years and martian days (called sols). Months are not used because there are two moons, with different, rather short, 'months'. +== Attributes of Timescales + +. 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 + +. Optional Unit of Measure + +[example] +TAI (International Atomic Time, Temps Atomique International) is coordinated by the BIPM (Inernational Bureau of Weights and measures, Bureau International de Poids et Mesures) 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] +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 limited computer words. + +== Attributes of Clocks + +. Name/id + +. Optional location, time or domain of applicability + +. Optional Epoch, defined in some temporal reference system + +' Tick definition + +[example] +An atomic clock may be calibrated to be valid only for a given temperature range and altitude. + +[example] +A pendulum clock may have each tick or swing of the pendulum adjusted to be an exact fraction or multipe of a second. The famous London "Big Ben" clock's pendulum is 4.4m long and ticks every two seconds. + == Synchronisation of clocks 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. From bbb9a54777c8efbf7172f535966cc163813f0b36 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 21:30:41 +0100 Subject: [PATCH 12/21] Update 06-other-clauses.adoc Change L to R order of diagram --- abstract-specification/sections/06-other-clauses.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index f7b8d9dc..a1381a0f 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -65,15 +65,15 @@ class TemporalReferenceSystem { note for ReferenceSystem "Note: Has at least one of:\nSpatialReferenceSystem, or \nTemporalReferenceSystem" ReferenceSystem <|-- SpatialReferenceSystem : is a ReferenceSystem <|-- TemporalReferenceSystem : is a -class TemporalCoordinateReferenceSystem { +class OrdinalTemporalReferenceSystem { dimension = 1 applicableLocationTimeOrDomain } -class Calendar { +class TemporalCoordinateReferenceSystem { dimension = 1 applicableLocationTimeOrDomain } -class OrdinalTemporalReferenceSystem { +class Calendar { dimension = 1 applicableLocationTimeOrDomain } From 6609cc65343b0ee0a4dc7a0ce67d955564a3ebb2 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 21:32:56 +0100 Subject: [PATCH 13/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index a1381a0f..06c28153 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -78,9 +78,12 @@ class Calendar { 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 - TemporalReferenceSystem <|-- OrdinalTemporalReferenceSystem : is a +OrdinalTemporalReferenceSystem "1" o-- "0..1" Epoch : has an +OrdinalTemporalReferenceSystem "1" o-- "(ordered)" Event : consists of +OrdinalTemporalReferenceSystem "1" --> "1..*" Notation : can use TemporalCoordinateReferenceSystem "1" o-- "1" Timescale : has a TemporalCoordinateReferenceSystem "1" o-- "1" Epoch : has an TemporalCoordinateReferenceSystem "1" --> "1..*" Notation : can use @@ -88,9 +91,6 @@ Calendar "1" o-- "0..1" Epoch : has an Calendar "1" o-- "1..*" Timescale : has a Calendar "1" o-- "1..*" Algorithm : has a Calendar "1" --> "1..*" Notation : can use -OrdinalTemporalReferenceSystem "1" o-- "0..1" Epoch : has an -OrdinalTemporalReferenceSystem "1" o-- "(ordered)" Event : consists of -OrdinalTemporalReferenceSystem "1" --> "1..*" Notation : can use class Timescale { StartCount EndCount From 8c57792d7e42e62b10e8f9f3ca29effdbaf9fd6b Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 21:36:48 +0100 Subject: [PATCH 14/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 06c28153..d6539b0c 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -383,7 +383,7 @@ The Julian Day is the continuous count of days (rotations of the Earth with resp . Optional Epoch, defined in some temporal reference system -' Tick definition +. Tick definition [example] An atomic clock may be calibrated to be valid only for a given temperature range and altitude. From 8eae23ad7cb10a76eeab9bf2c0d27ffa4686fc2f Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 21:39:23 +0100 Subject: [PATCH 15/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index d6539b0c..45aefee3 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -82,7 +82,7 @@ note for TemporalReferenceSystem "Note: Consists of one only of:\nTemporalCoordi TemporalReferenceSystem <|-- TemporalCoordinateReferenceSystem : is a TemporalReferenceSystem <|-- Calendar : is a OrdinalTemporalReferenceSystem "1" o-- "0..1" Epoch : has an -OrdinalTemporalReferenceSystem "1" o-- "(ordered)" Event : consists of +OrdinalTemporalReferenceSystem "1" o-- "(ordered)" Events : consists of OrdinalTemporalReferenceSystem "1" --> "1..*" Notation : can use TemporalCoordinateReferenceSystem "1" o-- "1" Timescale : has a TemporalCoordinateReferenceSystem "1" o-- "1" Epoch : has an From f34b65258be36e25551eeb7321b853965815afe5 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Wed, 16 Aug 2023 21:43:30 +0100 Subject: [PATCH 16/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 45aefee3..18095ec3 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -191,7 +191,7 @@ Since the speed of light in a vacuum is a measurable constant, space-time uses t ==== 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 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 grow 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 <>. These transforms allow one to calculate the degree of "contraction" a measurement undergos due to the relative velocity between the observing and observed object. From 8a5504026b19b70164118b5ff903a02aec4f48fb Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 17 Aug 2023 11:15:58 +0100 Subject: [PATCH 17/21] Update 06-other-clauses.adoc Refine layout of diagram --- abstract-specification/sections/06-other-clauses.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 18095ec3..06cb1b9a 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -81,16 +81,16 @@ note for TemporalReferenceSystem "Note: Consists of one only of:\nTemporalCoordi TemporalReferenceSystem <|-- OrdinalTemporalReferenceSystem : is a TemporalReferenceSystem <|-- TemporalCoordinateReferenceSystem : is a TemporalReferenceSystem <|-- Calendar : is a -OrdinalTemporalReferenceSystem "1" o-- "0..1" Epoch : has an 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" Timescale : has a 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 -Calendar "1" --> "1..*" Notation : can use class Timescale { StartCount EndCount From d1d0e61cb2da8dba4070825e563b96b22a4f4889 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 17 Aug 2023 11:46:53 +0100 Subject: [PATCH 18/21] Update 06-other-clauses.adoc Added more examples --- .../sections/06-other-clauses.adoc | 60 ++++++++++++------- 1 file changed, 39 insertions(+), 21 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 06cb1b9a..7a488da2 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -48,39 +48,40 @@ the Mermaid container with the following. ```mermaid classDiagram class ReferenceSystem { - <> - dimension = 1..* - applicableLocationTimeOrDomain + <> + dimension = 1..* + applicableLocationTimeOrDomain } class SpatialReferenceSystem { - <> - dimension = 1..* - applicableLocationTimeOrDomain + <> + dimension = 1..* + applicableLocationTimeOrDomain } class TemporalReferenceSystem { - <> - dimension = 1 - applicableLocationTimeOrDomain + <> + 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 + dimension = 1 + applicableLocationTimeOrDomain } class TemporalCoordinateReferenceSystem { - dimension = 1 - applicableLocationTimeOrDomain + dimension = 1 + applicableLocationTimeOrDomain } class Calendar { - dimension = 1 - applicableLocationTimeOrDomain + 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 +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 @@ -92,12 +93,18 @@ 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 + StartCount + EndCount + arithmetic } Timescale "1" o-- "1" Clock : has a Timescale "1" o-- "1" UnitOfMeasure : has a +class Clock { + Tick definition + } +class UnitOfMeasure { + Direction + } ``` == Temporal regimes @@ -391,6 +398,17 @@ An atomic clock may be calibrated to be valid only for a given temperature range [example] A pendulum clock may have each tick or swing of the pendulum adjusted to be an exact fraction or multipe of a second. The famous London "Big Ben" clock's pendulum is 4.4m long and ticks every two seconds. +== Attributes of Units of Measure + +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 the Unit of Measure, 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. + +. Name/Id/Abbreviation + +. Direction + +[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 wth no overlap. If there was a year zero defined, they could be replaced with one continuous timescale. + == Synchronisation of clocks 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. From dcefd9b58f99dd534e7d2a1f38ea1699e9d3e15d Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 17 Aug 2023 11:57:31 +0100 Subject: [PATCH 19/21] Update 06-other-clauses.adoc Improve consistency of text and diagram --- abstract-specification/sections/06-other-clauses.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 7a488da2..3a4d4e09 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -260,6 +260,8 @@ Other documents may enable two such 'king lists' to be related, though not compl . Optional Epoch, defined in some temporal reference system +. Arithmetic: Integer + . Optional name for each tick . Optional Start time or count @@ -287,6 +289,8 @@ A clock is started, but undergoes a calibration process against some standard cl . Optional Epoch, defined in some temporal reference system +. Aarithmetic: Real/floating point + . Optional name for the Unit of Measure . Optional Start time or measure From 89b557372a8327148cf71d4ab623be13fc927c28 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 17 Aug 2023 15:38:55 +0100 Subject: [PATCH 20/21] Update 06-other-clauses.adoc editorial, consistent titling --- .../sections/06-other-clauses.adoc | 175 ++++++++---------- 1 file changed, 73 insertions(+), 102 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 3a4d4e09..194ea54a 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -7,36 +7,26 @@ A conceptual model organizes the vocabulary needed to communicate consistently a A conceptual model: -. is a representation of a system, made of the composition of concepts which are -used to help people know, understand, or simulate a subject the model -represents. A documented conceptual model represents 'concepts' (entities), the -relationships between them, and a vocabulary; +. is a representation of a system, made of the composition of concepts which are used to help people know, understand, or simulate a subject the model represents. A documented conceptual model represents 'concepts' (entities), the relationships between them, and a vocabulary; . is explicitly defined to be independent of design or implementation concerns; -. organizes the vocabulary needed to communicate consistently and thoroughly -about the know-how of a problem domain; +. organizes the vocabulary needed to communicate consistently and thoroughly about the know-how of a problem domain; -. starts with a glossary of terms and definitions. There is a very high premium -on high-quality, design-independent definitions, free of data or implementation -biases; the model also emphasizes rich vocabulary; and +. starts with a glossary of terms and definitions. There is a very high premium on high-quality, design-independent definitions, free of data or implementation biases; the model also emphasizes rich vocabulary; and -. is always about identifying the correct choice of terms to use in -communications, including statements of rules and requirements, especially where -high precision and subtle distinctions need to be made. The core concepts of a -temporal geospatial problem domain are typically quite stable over time. +. is always about identifying the correct choice of terms to use in communications, including statements of rules and requirements, especially where +high precision and subtle distinctions need to be made. The core concepts of a temporal geospatial problem domain are typically quite stable over time. == Temporal Abstract Conceptual Model -This attempt at a Temporal Abstract Conceptual Model follows <>, -which is the ISO adoption of <>. +This attempt at a Temporal Abstract Conceptual Model follows <>, which is the ISO adoption of <>. The model is also informed by <>. [NOTE] ==== -This Mermaid diagram should be converted to PlantUML for Metanorma, by replacing -the Mermaid container with the following. +This Mermaid diagram should be converted to PlantUML for Metanorma, by replacing the Mermaid container with the following. ==== `[plantuml] @@ -217,9 +207,7 @@ The financial and administrative domains often use weeks, quarters, and other ca 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 <> timestamp notation, a restrictive profile of <>, -can express times before 1588CE, when the Gregorian calendar was first -introduced in some parts of the world. +The <> timestamp notation, a restrictive profile of <>, can express times before 1588CE, when the Gregorian calendar was first introduced in some parts of the world. == Attributes of the Regimes/Classes @@ -233,27 +221,29 @@ Besides the conventional space and time, there may be other reference systems, s === Attributes of Events and Ordinal Temporal Reference Systems +An OrdinalTemporal Reference System has a well-ordered finite sequence of events against which other events can be compared. + . Name/Id . Optional location, time or domain of applicability . Optional Epoch, defined in some temporal reference system -. Listed or enumerated sequence of events - -. First and last events +. Listed or enumerated sequence of events with the first and last events . Optional notations [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 emperor. +The events from the list may be instants, such as the change of reign, or intervals, such as the complete reign of each king. Other documents may enable two such 'king lists' to be related, though not completely. === Attributes of simple Clock and Discrete Timescale +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 Measure for convenience. Other events can be compared to the ticks on the timescale. + . Name/Id . Optional location, time or domain of applicability @@ -273,44 +263,28 @@ Other documents may enable two such 'king lists' to be related, though not compl . Optional notations [example] -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 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] -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 accidentally knocked so that it is no longer correctly calibrated, but is still working. The End Time is not the last time that the clock counts. +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 accidentally knocked so that it is no longer correctly calibrated, but is still working. The End Time is not the last time that the clock ticks. -=== Attributes of a CRS and Continuous Timescales +=== Attributes of Clocks -. Name/Id +. Name/id . Optional location, time or domain of applicability . Optional Epoch, defined in some temporal reference system -. Aarithmetic: Real/floating point - -. Optional name for the Unit of Measure - -. Optional Start time or measure - -. Optional End time or measure - -. Optional notations +. Tick definition [example] -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 increase the confidence in the timing accuracy. +An atomic clock may be calibrated to be valid only for a given temperature range and altitude. [example] -A long, deep, sediment core is extract from the bottom of a lake with a long geological history. two layers in the core are date using radiocarbon dated. Assuming steady rates of sediment deposition, a continuous timescale can be inerpolated between the dated layers, and extrapolated before and after the dated layers. +A pendulum clock may have each tick or swing of the pendulum adjusted to be an exact fraction or multipe of a second. The famous London "Big Ben" clock's pendulum is 4.4m long and ticks every two seconds. -== Attributes of Calendars +=== Attributes of Timescales . Name/id @@ -318,75 +292,56 @@ A long, deep, sediment core is extract from the bottom of a lake with a long geo . Optional Epoch, defined in some temporal reference system -. Astronomical Type (e.g. solar, sidereal, lunar, luni-solar) +. Arithmetic, whether counted integers or measured real/floating point numbers -. Predictive type (e.g. observed or calculated) +. Optional Unit of Measure -. Optional Start time +[example] +TAI (International Atomic Time, Temps Atomique International) is coordinated by the BIPM (Inernational Bureau of Weights and measures, Bureau International de Poids et Mesures) 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). -. Optional End time +[example] +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 limited computer words. -. Constituent units or clocks and counts or timescales +=== Attributes of Units of Measure -. Algorithms to link constituent timescales +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. -. Optional notations +. Name/Id/Abbreviation -[example] -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. +. Direction [example] -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. +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 wth no overlap. If there was a year zero defined, they could be replaced with one continuous timescale. -[example] -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. +=== Attributes of a CRS and Continuous Timescales -[example] -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. +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. -[example] -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. +. Name/Id -[example] -Teams controlling remote vehicles on Mars use a solar calendar, with Martian -years and martian days (called sols). Months are not used because there are two -moons, with different, rather short, 'months'. +. Optional location, time or domain of applicability -== Attributes of Timescales +. Optional Epoch, defined in some temporal reference system -. Name/id +. Aarithmetic: Real/floating point -. Optional location, time or domain of applicability +. Optional name for the Unit of Measure -. Optional Epoch, defined in some temporal reference system +. Optional Start time or measure -. Arithmetic, whether counted integers or measured real/floating point numbers +. Optional End time or measure -. Optional Unit of Measure +. Optional notations [example] -TAI (International Atomic Time, Temps Atomique International) is coordinated by the BIPM (Inernational Bureau of Weights and measures, Bureau International de Poids et Mesures) 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). +A long, deep, ice core is retrieved from a stable ice-sheet. From long termmeteorological 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] -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 limited computer words. +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. + +=== Attributes of Calendars -== Attributes of Clocks +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 or intervals on the ompound timescale are identified and labelled. . Name/id @@ -394,24 +349,40 @@ The Julian Day is the continuous count of days (rotations of the Earth with resp . Optional Epoch, defined in some temporal reference system -. Tick definition +. Astronomical Type (e.g. solar, sidereal, lunar, luni-solar) -[example] -An atomic clock may be calibrated to be valid only for a given temperature range and altitude. +. 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 [example] -A pendulum clock may have each tick or swing of the pendulum adjusted to be an exact fraction or multipe of a second. The famous London "Big Ben" clock's pendulum is 4.4m long and ticks every two seconds. +The modern Gregorian calendar is calculated solar calendar, with various epochs from 1588 CE through to 1922 CE depending on location or country. -== Attributes of Units of Measure +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 ISO8601 and its various restrictive profiles. -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 the Unit of Measure, 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. +[example] +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 +[example] +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. -. Direction +[example] +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] -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 wth no overlap. If there was a year zero defined, they could be replaced with one continuous timescale. +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] +Teams controlling remote vehicles on Mars use a solar calendar, with Martian years and Martian days (called Sols). Months are not used because there are two moons, with different, rather short, orbital periods. == Synchronisation of clocks From f5e571a8bc045e49d2e474954a18d738a2524dd9 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 17 Aug 2023 15:43:35 +0100 Subject: [PATCH 21/21] Update 06-other-clauses.adoc --- abstract-specification/sections/06-other-clauses.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/abstract-specification/sections/06-other-clauses.adoc b/abstract-specification/sections/06-other-clauses.adoc index 194ea54a..0e9bc9f2 100644 --- a/abstract-specification/sections/06-other-clauses.adoc +++ b/abstract-specification/sections/06-other-clauses.adoc @@ -172,13 +172,13 @@ A Calendar is a Temporal Reference System, but it is not a Temporal Coordinate R ==== General -There may be a series of 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. +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 of the apparent position of the sun along the ecliptic (path through the sky) as the basic physical principle. +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. -==== Spacetime +==== 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. @@ -190,7 +190,7 @@ Since the speed of light in a vacuum is a measurable constant, space-time uses t 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 grow 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 <>. 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 <>. 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.