From d01b07129cd8ec3f3358fb9088fc182a580b6959 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 12 Oct 2023 16:06:49 +0100 Subject: [PATCH 1/5] Update 00-preface.adoc Public Comment 1.3 add third submitter --- 23-049/sections/00-preface.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/23-049/sections/00-preface.adoc b/23-049/sections/00-preface.adoc index 885e355c..d9c7241e 100644 --- a/23-049/sections/00-preface.adoc +++ b/23-049/sections/00-preface.adoc @@ -34,6 +34,7 @@ h| Name h| Affiliation | Chris Little (editor) | U.K. Met Office | Chuck Heazel | HeazelTech +| Ron Tse | Ribose Inc. |=== From b602c958e6ed3ac19639fa0cec6a4bc0d9676926 Mon Sep 17 00:00:00 2001 From: Ronald Tse Date: Tue, 24 Oct 2023 20:56:32 +0800 Subject: [PATCH 2/5] feat: update Ronald Tse / Ribose as submitter --- 23-049/23-049.adoc | 4 +++- 23-049/sections/00-preface.adoc | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/23-049/23-049.adoc b/23-049/23-049.adoc index 85e756ea..e8201aae 100644 --- a/23-049/23-049.adoc +++ b/23-049/23-049.adoc @@ -12,10 +12,12 @@ :referenceURLID: http://docs.opengeospatial.org/as/23-049/23-049.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: diff --git a/23-049/sections/00-preface.adoc b/23-049/sections/00-preface.adoc index d9c7241e..234fba39 100644 --- a/23-049/sections/00-preface.adoc +++ b/23-049/sections/00-preface.adoc @@ -34,7 +34,7 @@ h| Name h| Affiliation | Chris Little (editor) | U.K. Met Office | Chuck Heazel | HeazelTech -| Ron Tse | Ribose Inc. +| Ronald Tse | Ribose Inc. |=== From d5b904946b7439dbef81f15bd99291496691ec38 Mon Sep 17 00:00:00 2001 From: Ronald Tse Date: Tue, 24 Oct 2023 20:53:34 +0800 Subject: [PATCH 3/5] chore: clean up gemfile --- Gemfile | 1 - 1 file changed, 1 deletion(-) diff --git a/Gemfile b/Gemfile index 8d658e52..ae144ae1 100644 --- a/Gemfile +++ b/Gemfile @@ -1,4 +1,3 @@ source "https://rubygems.org" gem "metanorma-cli" -gem "relaton-cli" From 48afa3f66fef463fca5e0cd413e0c52d51aa3d45 Mon Sep 17 00:00:00 2001 From: Ronald Tse Date: Tue, 24 Oct 2023 20:55:55 +0800 Subject: [PATCH 4/5] chore: simplify auto-fetch bib cross-refs to use default rendering --- 23-049/sections/00-preface.adoc | 6 +- 23-049/sections/03-references.adoc | 10 ++-- 23-049/sections/04-terms_and_definitions.adoc | 18 +++--- 23-049/sections/06-abstract_model.adoc | 6 +- 23-049/sections/annex-bibliography.adoc | 2 +- 23-049/sections/annex-glossary.adoc | 38 ++++++------- 23-050/sections/00-preface.adoc | 6 +- 23-050/sections/06-abstract_model.adoc | 6 +- 23-050/sections/07-formal_abstract_model.adoc | 2 +- 23-050/sections/annex-glossary.adoc | 56 +++++++++---------- 10 files changed, 75 insertions(+), 75 deletions(-) diff --git a/23-049/sections/00-preface.adoc b/23-049/sections/00-preface.adoc index 234fba39..76fad09f 100644 --- a/23-049/sections/00-preface.adoc +++ b/23-049/sections/00-preface.adoc @@ -12,7 +12,7 @@ Traditionally, geospatial communities used 2D coordinates and the vertical and t The fundamental concepts of events, clocks, timescales, coordinates and calendars have been long established, but there is no clear, straightforward defining document. This document aims to to give clear consistent definitions of the fundamental concepts and terminology, so that people are well aware of the advantages and disadvantages of adopting a particular technological approach and then perhaps they can contribute to building better and more interoperable systems using other more detailed documents such as logical and implementation standards that have an agreed common conceptual basis and terminology. -This document is consistent with <> and <> in OWL. +This document is consistent with <> and <> in OWL. The aim of this document is to establish clear concepts and terminology. @@ -41,8 +41,8 @@ h| Name h| Affiliation [.preface] == Introduction -When OGC standards involve time, they generally refer to the ISO documents such as <> (now largely superseded), <>, <>, and their freely available OGC equivalents, such as <> (the equivalent to <>). +When OGC standards involve time, they generally refer to the ISO documents such as <> (now largely superseded), <>, <>, and their freely available OGC equivalents, such as <> (the equivalent to <>). -Much effort over decades has gone into establishing complex structures to represent calendar based time, such as the <> notation, and many date-time schemas. Because of this effort, many people use calendar based "coordinates", with the attendant ambiguities, imprecision and inappropriate scope. +Much effort over decades has gone into establishing complex structures to represent calendar based time, such as the <> notation, and many date-time schemas. Because of this effort, many people use calendar based "coordinates", with the attendant ambiguities, imprecision and inappropriate scope. The aim of this document is to establish clear concepts and terminology, so that people are well aware of the advantages and disadvantages of adopting a particular technological approach and then perhaps contribute to building better interoperable systems. diff --git a/23-049/sections/03-references.adoc b/23-049/sections/03-references.adoc index 5daf4a84..3249e277 100644 --- a/23-049/sections/03-references.adoc +++ b/23-049/sections/03-references.adoc @@ -4,15 +4,15 @@ The following normative documents contain provisions that, through reference in this text, constitute provisions of this document. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies. -* [[[rfc3339,nofetch(IETF RFC 3339)]]] IETF: RFC 3339 _Date and Time on the Internet: Timestamps_. https://www.rfc-editor.org/rfc/rfc3339[https://www.rfc-editor.org/rfc/rfc3339] +* [[[rfc3339,IETF RFC 3339]]] -* [[[iso8601,nofetch(ISO 8601:2004)]]] ISO/TC 211: 8601:2004 _Data elements and interchange formats — Information interchange — Representation of dates and times_, 2004, https://www.iso.org/standard/40874.html[https://www.iso.org/standard/40874.html] +* [[[iso8601,ISO 8601:2004]]] -* [[[iso19111,nofetch(ISO 19111)]]] ISO/TC 211: ISO 19111:2019, _Geographic information – Referencing by coordinates_, 2019, https://www.iso.org/standard/74039.html[https://www.iso.org/standard/74039.html] +* [[[iso19111,ISO 19111:2019]]] * [[[temporal-knowledge,nofetch(Maintaining Knowledge about Temporal Intervals)]]] Allen, J. F. _Maintaining Knowledge about Temporal Intervals_ Communications of the ACM, 1983, vol. 26 pp. 832-843. -* [[[ogc18005,nofetch(OGC 18-005r4)]]] OGC: 18-005, _OGC Abstract Specification Topic 2: Referencing by coordinates Corrigendum_, 2021, https://docs.ogc.org/as/18-005r5/18-005r5.html[https://docs.ogc.org/as/18-005r5/18-005r5.html] +* [[[ogc18005,OGC 18-005r4]]] -* [[[w3cowltime,nofetch(W3C REC-owl-time-20171019)]]] W3C: Time Ontology in OWL, 2017, https://www.w3.org/TR/2017/REC-owl-time-20171019/[https://www.w3.org/TR/2017/REC-owl-time-20171019/] +* [[[w3cowltime,W3C REC-owl-time-20171019]]] diff --git a/23-049/sections/04-terms_and_definitions.adoc b/23-049/sections/04-terms_and_definitions.adoc index 36b42d63..da9b598a 100644 --- a/23-049/sections/04-terms_and_definitions.adoc +++ b/23-049/sections/04-terms_and_definitions.adoc @@ -12,7 +12,7 @@ description of common concepts and their relationships, particularly in order to one of a sequence of numbers designating the position of a point [.source] -<> +<> NOTE: In many coordinate reference systems, the coordinate numbers are qualified by units. @@ -22,7 +22,7 @@ NOTE: In many coordinate reference systems, the coordinate numbers are qualified <> that is related to an object by a <> [.source] -<> +<> NOTE: Geodetic and vertical datums are referred to as reference frames. @@ -34,7 +34,7 @@ NOTE: For geodetic and vertical reference frames, the object will be the Earth. set of mathematical rules for specifying how coordinates are to be assigned to points [.source] -<> +<> [[datum_definition]] === datum @@ -43,7 +43,7 @@ admitted:[reference frame] parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a <> [.source] -<> +<> [[epoch_definition]] === epoch @@ -52,7 +52,7 @@ domain:[geodesy] point in time [.source] -<> +<> NOTE: In the ISO 19111 document an epoch is expressed in the Gregorian calendar as a decimal year. @@ -66,7 +66,7 @@ admitted:[datum] parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a <> [.source] -<> +<> [[temporal-coordinate-refrence-system_definition]] === temporal coordinate reference system @@ -74,7 +74,7 @@ parameter or set of parameters that realize the position of the origin, the scal <> based on a <> [.source] -<> +<> [[temporal-coordinate-system_definition]] === temporal coordinate system @@ -83,7 +83,7 @@ domain:[geodesy] one-dimensional <> where the axis is time [.source] -<> +<> [[temporal-datum_definition]] === temporal datum @@ -91,7 +91,7 @@ one-dimensional <> where the axi <> describing the relationship of a <> to an object [.source] -<> +<> NOTE: The object is normally time on the Earth. diff --git a/23-049/sections/06-abstract_model.adoc b/23-049/sections/06-abstract_model.adoc index ae4e13b9..bdb123e6 100644 --- a/23-049/sections/06-abstract_model.adoc +++ b/23-049/sections/06-abstract_model.adoc @@ -19,7 +19,7 @@ A conceptual model: == Temporal Abstract Conceptual Model -This Temporal Abstract Conceptual Model follows <>, which is the ISO adoption of <>. +This Temporal Abstract Conceptual Model follows <>, which is the ISO adoption of <>. The model is also informed by the <>. @@ -217,7 +217,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 Classes @@ -226,7 +226,7 @@ The <> timestamp notation, a restrictive profile of <>, and 'TemporalReferenceSystem', each with the attributes of Dimension and Domains of Applicability. +The 'ReferenceSystem' has two abstract sub-classes: 'SpatialReferenceSystem', which is defined in <>, and 'TemporalReferenceSystem', each with the attributes of Dimension and Domains of Applicability. The Dimension is one for time, or a vertical reference system, but may be as much as 6 for spatial location with orientation as in the <>. diff --git a/23-049/sections/annex-bibliography.adoc b/23-049/sections/annex-bibliography.adoc index da4a71ac..f78b7baa 100644 --- a/23-049/sections/annex-bibliography.adoc +++ b/23-049/sections/annex-bibliography.adoc @@ -22,7 +22,7 @@ _A Brief History of Timekeeping_. Oneworld Publications. 2022. ISBN-13: 978-0-86154-321-2. -* [[[iso19108,nofetch(ISO 19108)]]] ISO/TC 211: ISO 19108:2002 _Geographic information — Temporal schema_, 2021, https://www.iso.org/standard/26013.html[https://www.iso.org/standard/26013.html] +* [[[iso19108,ISO 19108:2002]]] ISO/TC 211: ISO 19108:2002 _Geographic information — Temporal schema_, 2021, https://www.iso.org/standard/26013.html * [[[OGCgeopose,nofetch(OGC 21-056r10)]]] OGC: _GeoPose Specification draft_, 2021, https://github.com/opengeospatial/GeoPose/ diff --git a/23-049/sections/annex-glossary.adoc b/23-049/sections/annex-glossary.adoc index 24ad594b..d8438020 100644 --- a/23-049/sections/annex-glossary.adoc +++ b/23-049/sections/annex-glossary.adoc @@ -9,7 +9,7 @@ coordinate reference system using at least two independent coordinate reference systems [.source] -<> +<> NOTE: Coordinate reference systems are independent of each other if coordinate values in one cannot be converted or transformed into coordinate values in the other. @@ -19,7 +19,7 @@ NOTE: Coordinate reference systems are independent of each other if coordinate v epoch to which coordinates in a dynamic coordinate reference system are referenced [.source] -<> +<> [[derived-coordinate-reference-system_definition]] === derived coordinate reference system @@ -27,7 +27,7 @@ epoch to which coordinates in a dynamic coordinate reference system are referenc coordinate reference system that is defined through the application of a specified coordinate conversion to the coordinates within a previously established coordinate reference system [.source] -<> +<> NOTE: The previously established coordinate reference system is referred to as the base coordinate reference system. @@ -41,7 +41,7 @@ NOTE: The coordinate conversion between the base and derived coordinate referenc coordinate reference system that has a dynamic reference frame [.source] -<> +<> NOTE: Coordinates of points on or near the crust of the Earth that are referenced to a dynamic coordinate reference system may change with time, usually due to crustal deformations such as tectonic motion and glacial isostatic adjustment. @@ -54,7 +54,7 @@ admitted:[dynamic datum] reference frame in which the defining parameters include time evolution [.source] -<> +<> NOTE: The defining parameters that have time evolution are usually a coordinate set. @@ -79,7 +79,7 @@ admitted:[local datum] datum describing the relationship of a coordinate system to a local reference [.source] -<> +<> NOTE: Engineering datum excludes both geodetic and vertical reference frames. @@ -89,7 +89,7 @@ NOTE: Engineering datum excludes both geodetic and vertical reference frames. epoch of coordinates that define a dynamic reference frame [.source] -<> +<> [[linear-coordinate-system_definition]] === linear coordinate system @@ -97,7 +97,7 @@ epoch of coordinates that define a dynamic reference frame one-dimensional coordinate system in which a linear feature forms the axis [.source] -<> +<> [example] Distances along a pipeline. @@ -111,7 +111,7 @@ Depths down a deviated oil well bore. epoch at which the parameter values of a time-dependent coordinate transformation are valid [.source] -<> +<> NOTE: The transformation parameter values first need to be propagated to the epoch of the coordinates before the coordinate transformation can be applied. @@ -121,7 +121,7 @@ NOTE: The transformation parameter values first need to be propagated to the epo coordinate reference system based on a parametric datum [.source] -<> +<> [[parametric-coordinate-system_definition]] === parametric coordinate system @@ -129,7 +129,7 @@ coordinate reference system based on a parametric datum one-dimensional coordinate system where the axis units are parameter values which are not inherently spatial [.source] -<> +<> [[parametric-datum_definition]] === parametric datum @@ -137,7 +137,7 @@ one-dimensional coordinate system where the axis units are parameter values whic datum describing the relationship of a parametric coordinate system to an object [.source] -<> +<> NOTE: The object is normally the Earth. @@ -147,7 +147,7 @@ NOTE: The object is normally the Earth. coordinate operation that changes coordinates within one coordinate reference system due to the motion of the point [.source] -<> +<> NOTE: The change of coordinates is from those at an initial epoch to those at another epoch. @@ -159,7 +159,7 @@ NOTE: In this document the point motion is due to tectonic motion or crustal def compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a parametric coordinate reference system [.source] -<> +<> NOTE: Normally the spatial component is “horizontal” and the parametric component is “vertical”. @@ -169,7 +169,7 @@ NOTE: Normally the spatial component is “horizontal” and the parametric comp compound coordinate reference system comprised of spatial, parametric and temporal coordinate reference systems [.source] -<> +<> [[spatio-temporal-coordinate-reference-system_definition]] === spatio-temporal coordinate reference system @@ -177,7 +177,7 @@ compound coordinate reference system comprised of spatial, parametric and tempor compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a temporal coordinate reference system [.source] -<> +<> [[static-coordinate-reference-system_definition]] === static coordinate reference system @@ -185,7 +185,7 @@ compound coordinate reference system in which one constituent coordinate referen coordinate reference system that has a static reference frame [.source] -<> +<> NOTE: Coordinates of points on or near the crust of the Earth that are referenced to a static coordinate reference system do not change with time. @@ -199,7 +199,7 @@ static datum reference frame in which the defining parameters exclude time evolution [.source] -<> +<> [[terrestrial-reference-system_definition]] === terrestrial reference system @@ -208,6 +208,6 @@ admitted:[TRS] set of conventions defining the origin, scale, orientation and time evolution of a spatial reference system co-rotating with the Earth in its diurnal motion in space [.source] -<> +<> NOTE: The abstract concept of a TRS is realised through a terrestrial reference frame that usually consists of a set of physical points with precisely determined coordinates and optionally their rates of change. In this document terrestrial reference frame is included within the geodetic reference frame element of the data model diff --git a/23-050/sections/00-preface.adoc b/23-050/sections/00-preface.adoc index 7ffbcf49..740f46c6 100644 --- a/23-050/sections/00-preface.adoc +++ b/23-050/sections/00-preface.adoc @@ -13,7 +13,7 @@ Traditionally, geospatial communities used 2D coordinates and the vertical and t The fundamental concepts of events, clocks, timescales, coordinates and calendars have been long established, but there is no clear, straightforward defining document. This document aims to to give clear consistent definitions of the fundamental concepts and terminology, so that people are well aware of the advantages and disadvantages of adopting a particular technological approach and then perhaps they can contribute to building better and more interoperable systems using other more detailed documents such as logical and implementation standards that have an agreed common conceptual basis and terminology. -This document is consistent with <> and <> in OWL. +This document is consistent with <> and <> in OWL. The aim of this document is to establish clear concepts and terminology. @@ -41,8 +41,8 @@ h| Name h| Affiliation [.preface] == Introduction -When OGC standards involve time, they generally refer to the ISO documents such as <> (now largely superseded), <>, <>, and their freely available OGC equivalents, such as <> (the equivalent to <>). +When OGC standards involve time, they generally refer to the ISO documents such as <> (now largely superseded), <>, <>, and their freely available OGC equivalents, such as <> (the equivalent to <>). -Much effort over decades has gone into establishing complex structures to represent calendar based time, such as the <> notation, and many date-time schemas. Because of this effort, many people use calendar based "coordinates", with the attendant ambiguities, imprecision and inappropriate scope. +Much effort over decades has gone into establishing complex structures to represent calendar based time, such as the <> notation, and many date-time schemas. Because of this effort, many people use calendar based "coordinates", with the attendant ambiguities, imprecision and inappropriate scope. The aim of this document is to establish clear concepts and terminology, so that people are well aware of the advantages and disadvantages of adopting a particular technological approach and then perhaps contribute to building better interoperable systems. diff --git a/23-050/sections/06-abstract_model.adoc b/23-050/sections/06-abstract_model.adoc index 9b889c6f..404d09bd 100644 --- a/23-050/sections/06-abstract_model.adoc +++ b/23-050/sections/06-abstract_model.adoc @@ -19,7 +19,7 @@ A conceptual model: == 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 <>. @@ -209,7 +209,7 @@ The <> timestamp notation, a restrictive profile of <>, The top level `Reference System` is an abstract super-class and does not have many attributes or properties. So far, only the total dimension of the reference system and the Location, Time or Domain of Applicability have been identified as essential. -The 'ReferenceSystem' has two abstract sub-classes: 'SpatialReferenceSystem' , which is defined in <>, and 'TemporalReferenceSystem', each with the attributes of Dimension and Domains of Applicability. +The 'ReferenceSystem' has two abstract sub-classes: 'SpatialReferenceSystem' , which is defined in <>, and 'TemporalReferenceSystem', each with the attributes of Dimension and Domains of Applicability. The Dimension is one for time, or a vertical reference system, but may be as much as 6 for spatial location with orientation. @@ -362,7 +362,7 @@ Calendars combine different timescales and their clocks and unito of measure, an [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 <> and its various restrictive profiles. +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 <> and its various restrictive profiles. [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. diff --git a/23-050/sections/07-formal_abstract_model.adoc b/23-050/sections/07-formal_abstract_model.adoc index 3e725b5c..095cd093 100644 --- a/23-050/sections/07-formal_abstract_model.adoc +++ b/23-050/sections/07-formal_abstract_model.adoc @@ -4,7 +4,7 @@ The Temporal Abstract Conceptual Model has been built using a UML model. This pr === Context -When OGC standards involve time, they generally refer to the ISO documents such as <>, <>, <>, and their freely available OGC equivalents, such as Abstract Specification Topic 2 Referencing by Coordinates (equivalent to <). +When OGC standards involve time, they generally refer to the ISO documents such as <>, <>, <>, and their freely available OGC equivalents, such as Abstract Specification Topic 2 Referencing by Coordinates (equivalent to <). When dealing with temporal reference systems, it is necessary to understand all of these standards and how they interact. ISO Technical Committee 211 (ISO/TC211) provides a useful tool for integrating their standards. The https://github.com/ISO-TC211/HMMG[ISO/TC 211 Harmonized Model Management Group] provides a single integrated model for most of the ISO/TC 211 standards. That model will provide the foundation for the Abstract Temporal Reference Model. diff --git a/23-050/sections/annex-glossary.adoc b/23-050/sections/annex-glossary.adoc index 5bf10646..fd663918 100644 --- a/23-050/sections/annex-glossary.adoc +++ b/23-050/sections/annex-glossary.adoc @@ -17,7 +17,7 @@ description of common concepts and their relationships, particularly in order to coordinate reference system using at least two independent coordinate reference systems [.source] -<> +<> NOTE: Coordinate reference systems are independent of each other if coordinate values in one cannot be converted or transformed into coordinate values in the other. @@ -27,7 +27,7 @@ NOTE: Coordinate reference systems are independent of each other if coordinate v one of a sequence of numbers designating the position of a point [.source] -<> +<> NOTE: In a spatial coordinate reference system, the coordinate numbers are qualified by units. @@ -37,7 +37,7 @@ NOTE: In a spatial coordinate reference system, the coordinate numbers are quali epoch to which coordinates in a dynamic coordinate reference system are referenced [.source] -<> +<> [[coordinate-reference-system_definition]] === coordinate reference system @@ -45,7 +45,7 @@ epoch to which coordinates in a dynamic coordinate reference system are referenc coordinate system that is related to an object by a datum [.source] -<> +<> NOTE: Geodetic and vertical datums are referred to as reference frames. @@ -57,7 +57,7 @@ NOTE: For geodetic and vertical reference frames, the object will be the Earth. set of mathematical rules for specifying how coordinates are to be assigned to points [.source] -<> +<> [[datum_definition]] === datum @@ -66,7 +66,7 @@ admitted:[reference frame] parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a coordinate system [.source] -<> +<> [[derived-coordinate-reference-system_definition]] === derived coordinate reference system @@ -74,7 +74,7 @@ parameter or set of parameters that realize the position of the origin, the scal coordinate reference system that is defined through the application of a specified coordinate conversion to the coordinates within a previously established coordinate reference system [.source] -<> +<> NOTE: The previously established coordinate reference system is referred to as the base coordinate reference system. @@ -88,7 +88,7 @@ NOTE: The coordinate conversion between the base and derived coordinate referenc coordinate reference system that has a dynamic reference frame [.source] -<> +<> NOTE: Coordinates of points on or near the crust of the Earth that are referenced to a dynamic coordinate reference system may change with time, usually due to crustal deformations such as tectonic motion and glacial isostatic adjustment. @@ -101,7 +101,7 @@ admitted:[dynamic datum] reference frame in which the defining parameters include time evolution [.source] -<> +<> NOTE: The defining parameters that have time evolution are usually a coordinate set. @@ -126,7 +126,7 @@ admitted:[local datum] datum describing the relationship of a coordinate system to a local reference [.source] -<> +<> NOTE: Engineering datum excludes both geodetic and vertical reference frames. @@ -137,7 +137,7 @@ domain:[geodesy] point in time [.source] -<> +<> NOTE: In this document an epoch is expressed in the Gregorian calendar as a decimal year. @@ -150,7 +150,7 @@ NOTE: In this document an epoch is expressed in the Gregorian calendar as a deci epoch of coordinates that define a dynamic reference frame [.source] -<> +<> [[linear-coordinate-system_definition]] === linear coordinate system @@ -158,7 +158,7 @@ epoch of coordinates that define a dynamic reference frame one-dimensional coordinate system in which a linear feature forms the axis [.source] -<> +<> [example] Distances along a pipeline. @@ -172,7 +172,7 @@ Depths down a deviated oil well bore. epoch at which the parameter values of a time-dependent coordinate transformation are valid [.source] -<> +<> NOTE: The transformation parameter values first need to be propagated to the epoch of the coordinates before the coordinate transformation can be applied. @@ -182,7 +182,7 @@ NOTE: The transformation parameter values first need to be propagated to the epo coordinate reference system based on a parametric datum [.source] -<> +<> [[parametric-coordinate-system_definition]] === parametric coordinate system @@ -190,7 +190,7 @@ coordinate reference system based on a parametric datum one-dimensional coordinate system where the axis units are parameter values which are not inherently spatial [.source] -<> +<> [[parametric-datum_definition]] === parametric datum @@ -198,7 +198,7 @@ one-dimensional coordinate system where the axis units are parameter values whic datum describing the relationship of a parametric coordinate system to an object [.source] -<> +<> NOTE: The object is normally the Earth. @@ -208,7 +208,7 @@ NOTE: The object is normally the Earth. coordinate operation that changes coordinates within one coordinate reference system due to the motion of the point [.source] -<> +<> NOTE: The change of coordinates is from those at an initial epoch to those at another epoch. @@ -221,7 +221,7 @@ admitted:[datum] parameter or set of parameters that realize the position of the origin, the scale, and the orientation of a coordinate system [.source] -<> +<> [[spatio-parametric-coordinate-reference-system_definition]] === spatio-parametric coordinate reference system @@ -229,7 +229,7 @@ parameter or set of parameters that realize the position of the origin, the scal compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a parametric coordinate reference system [.source] -<> +<> NOTE: Normally the spatial component is “horizontal” and the parametric component is “vertical”. @@ -239,7 +239,7 @@ NOTE: Normally the spatial component is “horizontal” and the parametric comp compound coordinate reference system comprised of spatial, parametric and temporal coordinate reference systems [.source] -<> +<> [[spatio-temporal-coordinate-reference-system_definition]] === spatio-temporal coordinate reference system @@ -247,7 +247,7 @@ compound coordinate reference system comprised of spatial, parametric and tempor compound coordinate reference system in which one constituent coordinate reference system is a spatial coordinate reference system and one is a temporal coordinate reference system [.source] -<> +<> [[static-coordinate-reference-system_definition]] === static coordinate reference system @@ -255,7 +255,7 @@ compound coordinate reference system in which one constituent coordinate referen coordinate reference system that has a static reference frame [.source] -<> +<> NOTE: Coordinates of points on or near the crust of the Earth that are referenced to a static coordinate reference system do not change with time. @@ -269,7 +269,7 @@ static datum reference frame in which the defining parameters exclude time evolution [.source] -<> +<> [[temporal-coordinate-refrence-system_definition]] === temporal coordinate reference system @@ -277,7 +277,7 @@ reference frame in which the defining parameters exclude time evolution coordinate reference system based on a temporal datum [.source] -<> +<> [[temporal-coordinate-system_definition]] === temporal coordinate system @@ -286,7 +286,7 @@ domain:[geodesy] one-dimensional coordinate system where the axis is time [.source] -<> +<> [[temporal-datum_definition]] === temporal datum @@ -294,7 +294,7 @@ one-dimensional coordinate system where the axis is time datum describing the relationship of a temporal coordinate system to an object [.source] -<> +<> NOTE: The object is normally time on the Earth. @@ -305,6 +305,6 @@ admitted:[TRS] set of conventions defining the origin, scale, orientation and time evolution of a spatial reference system co-rotating with the Earth in its diurnal motion in space [.source] -<> +<> NOTE: The abstract concept of a TRS is realised through a terrestrial reference frame that usually consists of a set of physical points with precisely determined coordinates and optionally their rates of change. In this document terrestrial reference frame is included within the geodetic reference frame element of the data model From 9d7fe5466da24d9e07f35e0e268d6f2a0c5bc1f2 Mon Sep 17 00:00:00 2001 From: Ronald Tse Date: Tue, 24 Oct 2023 20:56:13 +0800 Subject: [PATCH 5/5] chore: use numbered list notation instead of hardcoded list item labels --- 23-049/sections/02-conformance.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/23-049/sections/02-conformance.adoc b/23-049/sections/02-conformance.adoc index 702fb24f..aef0e65d 100644 --- a/23-049/sections/02-conformance.adoc +++ b/23-049/sections/02-conformance.adoc @@ -3,9 +3,9 @@ Clause 7 of this International Standard uses the Unified Modeling Language (UML) to present conceptual schemas for describing the higher level classes of time and temporal reference systems. These schemas define conceptual classes that -a) may be considered to comprise a cross-domain application schema, or +. may be considered to comprise a cross-domain application schema, or -b) may be used in application schemas, profiles and implementation specifications. +. may be used in application schemas, profiles and implementation specifications. This flexibility is controlled by a set of UML types that can be implemented in a variety of manners. Use of alternative names that are more familiar in a particular application is acceptable, provided that there is a one-