Merge pull request #538 from opengeospatial/part2-rfc-changes

[WIP] update requirement 2 wording (#536)

extensions/pubsub/standard/abstract_tests/pubsub-message-payload/ATS_test_id.adoc

@@ -3,7 +3,7 @@
 [%metadata]
 identifier:: /conf/pubsub-message-payload/id
 target:: /req/pubsub-message-payload/id
-test-purpose:: Validate that a notification message provides an `id` property that is a GUID.
+test-purpose:: Validate that a notification message provides an `id` property that is a UUID.
 test-method::
 +
 --
@@ -13,6 +13,6 @@ test-method::
 4. Find a link that contains `+rel=service-desc+` that corresponds to an AsyncAPI 3.0 description
 5. Using the server endpoint, subscribe to a given topic.
 6. Upon receiving a message against the selected topic, ensure that the message has an `id` property.
-7. Ensure that the `id` property is a valid GUID.
+7. Ensure that the `id` property is a valid UUID.
 --
 ====

extensions/pubsub/standard/requirements/pubsub-channels/REQ_rc-channels.adoc

@@ -3,5 +3,5 @@
 ====
 [%metadata]
 identifier:: /req/pubsub-channels/channels
-part:: Channels (topic/destination/node depending on protocol) that have equivalent API endpoint functionality SHALL be expressed within an AsyncAPI channel with an ``x-ogc-api-link`` object.
+part:: Channels (topic/destination/node depending on protocol) that communicate changes to resources in an OGC Web API SHALL be expressed within an AsyncAPI channel with an ``x-ogc-api-link`` object.
 ====

extensions/pubsub/standard/requirements/pubsub-message-payload/REQ_rc-id.adoc

@@ -3,5 +3,5 @@
 ====
 [%metadata]
 identifier:: /req/pubsub-message-payload/id
-part:: A Pub/Sub notification message SHALL provide an `+id+` property as a GUID.
+part:: A Pub/Sub notification message SHALL provide an `+id+` property as a UUID.
 ====