From 2c0bc1bb4404a6bc0279ef0ca1de2b399c2aa938 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 1 Feb 2024 13:17:51 +0000 Subject: [PATCH] Update clause_9_pubsub-message-payload.adoc clarify requirements for GeoJSON, as raised in Issue #501 --- .../sections/clause_9_pubsub-message-payload.adoc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc b/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc index 4694e7aca..cc739c7ad 100644 --- a/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc +++ b/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc @@ -14,12 +14,18 @@ While the Publish-Subscribe (Pub/Sub) Requirements Class recommends a machine-re the Message Payload Requirements Class provides further requirements for interoperability of message payloads as part of an OGC API implementation ecosystem. -==== GeoJSON compliance +==== JSON, GeoJSON and FG-JSON -_GeoJSON_ can provide a compact and machine readable encoding as a baseline for message notification. +_JSON_ is a widely used, flexible, relatively compact, format that is both machine readable and amenable to human inspection. A restricted profile of _JSON_, _GeoJSON_, can be used for geospatial data to improve interoperability, but it specifies that geospatial coordinate data must only use the _WGS84_ coordinate reference system. _GeoJSON_ is defined in the standard IETF RFC7946. + +If _GeoJSON_ is used as a payload for message notification, then include::../requirements/pubsub-message-payload/REQ_rc-geojson.adoc[] +If a Coordinate Reference System other than _WGS84_ is used, then the _OGC Features and Geometry JSON_ extension to _GeoJSON_ should be used. + +include::../recommendations/pubsub-message-payload/REC_crs.adoc[] + ==== Identifier A universally unique identifier of the message using the UUID standard (RFC4122). The identifier is generated by the originator of the message.