Definition of "temporal_datum"

NOTE: Markdown does not support highlighting in color, so bold/italic has been used to highlight the material being discussed. This issue is extracted from the document submitted by Roger Lott at https://github.com/opengeospatial/CRS-JSON-Encoding/blob/main/ProjJson%20v0-7%20RL%202024-06-16.docx for discussion at the CRS SWG meeting OGC held during the Montreal June 2024 TC meeting.

"temporal_datum": {
"type": "object",

"allOf": [{ "$ref": "#/definitions/object_usage" }],

  "properties": {
    "type": { "type": "string", "enum": ["TemporalDatum"] },
    "name": { "type": "string" },

"conventional_RS": { "type": "string" }
"publication_date": { "type": date }

    "calendar": { "type": "string" },
    "time_origin": { "type": "string" },
    "$schema" : {},

"scope": {},
"area": {},
"bbox": {},
"vertical_extent": {},
"temporal_extent": {},
"usages": {},

    "remarks": {},
    "id": {}, "ids": {}
  },
  "required" : [ "name", "calendar", "time_origin" ],
  "additionalProperties": false
},

"$comment": "[RL] See comment regarding usage under compound_crs."

"$comment": "[RL] Calendar default is proleptic Gregorian."

"$comment": "[RL] 19111/Topic 2 model has conventionalRS as an optional attribute but unlikely to be relevant to temporal datum."

Start by reviewing the temporal_datum definition in this issue and the linked ProjJson v0-7 RL 2024-06-16.docx. Compare the proposed properties, required fields, defaults, and comments with the current CRS-JSON Encoding schema, then confirm the intended definition through the CRS SWG discussion; done means the schema decision is recorded and consistently applied.