bound_crs and abridged_transformation - should they be included in an OGC CRS JSON encoding?

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.

"abridged_transformation": {
"type": "object",
"properties": {
"$schema" : { "type": "string" },
"type": { "type": "string", "enum": ["AbridgedTransformation"] },
"name": { "type": "string" },
"source_crs": {
"$ref": "#/definitions/crs",
"$comment": "Only present when the source_crs of the bound_crs does not match the source_crs of the AbridgedTransformation. No equivalent in WKT"
},
"method": { "$ref": "#/definitions/method" },
"parameters": {
"type": "array",
"items": { "$ref": "#/definitions/parameter_value" }
},
"id": { "$ref": "#/definitions/id" },
"ids": { "$ref": "#/definitions/ids" }
},
"required" : [ "name", "method", "parameters" ],
"allOf": [
{ "$ref": "#/definitions/id_ids_mutually_exclusive" }
],
"additionalProperties": false
},

The concepts of bound_crs and abridged_transformation are not recognised in Topic 2 (18-005r8) but are defined in CRS WKT (18-010r11). Should they be included in an OGC CRS JSON encoding?

Read the extracted ProjJson v0-7 RL 2024-06-16.docx material, then compare the Topic 2 and CRS WKT references cited in the issue. Determine whether bound_crs and abridged_transformation belong in the OGC CRS JSON encoding and document the agreed specification decision; no tests or implementation entry points are mentioned.