From 3607dd9bb45dc7758bc2a01275eb1c96f97f54aa Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 18 Jan 2024 16:31:50 +0000 Subject: [PATCH] Update clause_7_pubsub.adoc spelling --- extensions/pubsub/standard/sections/clause_7_pubsub.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extensions/pubsub/standard/sections/clause_7_pubsub.adoc b/extensions/pubsub/standard/sections/clause_7_pubsub.adoc index 6866820c8..14991f357 100644 --- a/extensions/pubsub/standard/sections/clause_7_pubsub.adoc +++ b/extensions/pubsub/standard/sections/clause_7_pubsub.adoc @@ -15,7 +15,7 @@ include::../recommendations/pubsub/PER_protocols.adoc[] === OGC API Considerations -The OGC API building block approach would typically be used for shared components in API implementations in support of a polling workflow. Using HTTP, this means that the client initiates and invokes requests and receives responses from the server. A key concept of the OGC API building blocks architecture is the service endpoint of the URL path specifying a resource and anysimialr sub-resources, which can be applied for Pub/Sub workflow as follows: +The OGC API building block approach would typically be used for shared components in API implementations in support of a polling workflow. Using HTTP, this means that the client initiates and invokes requests and receives responses from the server. A key concept of the OGC API building blocks architecture is the service endpoint of the URL path specifying a resource and any similar sub-resources, which can be applied for Pub/Sub workflow as follows: * Data producers: Messages are published to a broker, applied to a given channel (example: ``collections/mycollection``). * Broker provisioning: Published messages are sent to subscribers.