Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial typos and tidy folders #93

Merged
merged 14 commits into from
Feb 22, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added 23-049/images/Figure1Mermaid.JPG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified 23-049/images/IntervalRelations.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
2 changes: 1 addition & 1 deletion 23-049/images/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@ This folder contains the images used in the Abstract Conceptual Model for Time,

Some are expressed directly as Mermaid or PlantUML diagrams.

The Mermaid diagram is so that it can be viewed while editing this repo. The equivalent PlantUML version will be built when the full OGC 23-049 document is created.
The Mermaid diagram is so that it can be viewed or changed while editing this repo. Currently, a JPG snapshot of the Mermaid diagram is used, but the equivalent PlantUML version could be built when the full OGC 23-049 document is created.
Binary file removed 23-049/plantuml/plantuml20240213-1-7qv577.png
Binary file not shown.
Binary file removed 23-049/plantuml/plantuml20240213-1-yyhrmj.png
Binary file not shown.
2 changes: 1 addition & 1 deletion 23-049/sections/00-preface.adoc
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

== Preface

When OGC Standards involve time, they generally refer to the ISO documents such as Geographic information Temporal schema <<iso19108>> (now largely superseded), Geographic information Referencing by coordinates <<iso19111>>, Date and Time Format <<iso8601>>, and their freely available OGC equivalents, such as OGC Abstract Specification Topic 2: Referencing by coordinates <<ogc18005>> (the equivalent to <<iso19111>>).
When OGC Standards involve time, they generally refer to the ISO documents such as Geographic Information Temporal Schema <<iso19108>> (now largely superseded), Geographic information Referencing by coordinates <<iso19111>>, Date and Time Format <<iso8601>>, and the freely available OGC equivalents, such as OGC Abstract Specification Topic 2: Referencing by Coordinates <<ogc18005>> (the equivalent to <<iso19111>>).

Over decades, much effort has gone into establishing complex structures to represent calendar based time, such as the <<iso8601>> notation, and many date-time schemas. A consequence of this effort is that many end-users and developers of software use calendar based "coordinates", with the associated ambiguities about underlying algorithms, imprecision and inappropriate scope.

Expand Down
6 changes: 4 additions & 2 deletions 23-049/sections/02-conformance.adoc
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@

== Conformance

According to https://portal.ogc.org/files/?artifact_id=102806&version=6[OGC Policy] "The detail of the Abstract Specification shall be sufficient to provide normative references, including models, and technical guidelines as a foundation for Standards. Each Topic, to the extent possible, provides unambiguous normative and informative information that allows for implementation of Standards in software.
According to https://portal.ogc.org/files/?artifact_id=102806&version=6[OGC Policy]:

The level of detail of the Abstract Specification is at the discretion of the TC as reflected by the actual content that is approved for inclusion in the document itself.”
"The detail of the Abstract Specification shall be sufficient to provide normative references, including models, and technical guidelines as a foundation for Standards. Each Topic, to the extent possible, provides unambiguous normative and informative information that allows for implementation of Standards in software.

The level of detail of the Abstract Specification is at the discretion of the TC [Technical Committee] as reflected by the actual content that is approved for inclusion in the document itself.”

This Abstract Specification does not include any specific requirements or conformance classes. However, it does include normative references and a normative Unified Modeling Language (UML) model. Conformance is demonstrated through inclusion of the normative references in any derivative specification and by basing any derived conceptual model on the abstract model provided in this Standard.

Expand Down
2 changes: 1 addition & 1 deletion 23-049/sections/08-temporal-regimes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,6 @@ The key to this approach is to ensure each moving feature of interest has its ow

Relativistic effects may need to be considered for satellites and other spacecraft because of their relative speed and position in Earth's gravity well.

The presence of gravitational effects requires special relativity to be replaced by general relativity, and it can no longer be assumed that space (or space-time) is Euclidean. That is, Pythagoras' Theorem does not hold except locally over small areas, or that the circumference of a circle is not precisely stem:[2 :pi r]. This is somewhat familiar territory for geospatial experts. This Abstract Conceptual Model for Time can support this regime, providing each feature has its own clock.
The presence of gravitational effects requires special relativity to be replaced by general relativity, and it can no longer be assumed that space (or space-time) is Euclidean. That is, Pythagoras' Theorem does not hold except locally over small areas, or that the circumference of a circle is not precisely stem:[2 pi r]. This is somewhat familiar territory for geospatial experts. This Abstract Conceptual Model for Time can support this regime, providing each feature has its own clock.


Loading