Definition of "dynamic_vertical_reference_frame"

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.

"dynamic_vertical_reference_frame": {
  "type": "object",

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

  "properties": {
    "type": { "type": "string", "enum": ["DynamicVerticalReferenceFrame"] },
    "name": { "type": "string" },
    "anchor": { "type": "string" },
    "anchor_epoch": { "type": "number" },

"conventional_RS: { "type": "string" }
"publication_date: { "type": date }
"realization_method": { "$ref": "#/definitions/realization_method" }

    "frame_reference_epoch": { "type": "number" },
    "$schema" : {},

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

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

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

"$comment": "[RL] 3x missing attributes and 2x missing data type."

Start with the dynamic_vertical_reference_frame fragment in this issue and the linked ProjJson v0-7 RL 2024-06-16.docx submission. Review the proposed attributes, data types, usage fields, and comments against the current CRS-JSON-Encoding definition, then confirm the CRS SWG meeting's decision. Done means the agreed definition and required fields are recorded consistently.