Pub/Sub: fix doc refs

extensions/pubsub/examples/yaml/asyncapi.yaml

@@ -1,4 +1,4 @@
-asyncapi: '2.5.0'
+asyncapi: '3.0.0'
 info:
     title: AsyncAPI demo
     version: '0.0.1'

extensions/pubsub/standard/sections/clause_7_pubsub.adoc

@@ -23,12 +23,6 @@ The OGC API building block approach would typically be used for shared component
 
 The above workflow requires adherence to a hierarchy of channels, auto-discovery of channels, as well as processing of generic messages for broad interoperability by all components.
 
-==== Message payloads
-
-For smaller payload workflow, implementations of OGC API Standards can additionally provide a channel for notification metadata in order to receive a smaller message payload, which a user can process to determine whether to further interact with the referenced data granule or resource.
-
-include::../recommendations/pubsub/REC_message-payloads.adoc[]
-
 ==== AsyncAPI
 
 Based on research and testing, the Pub/Sub White Paper recommended the use of AsyncAPI. AsyncAPI provides an event-driven equivalent of what is provided by OpenAPI for OGC API Standards (description of protocols, channels, parameters, models, etc.). An implementation of the https://ogcapi.ogc.org/common/overview.html[OGC API landing page requirements class] can provide a link to an AsyncAPI document as follows:

extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc

@@ -19,7 +19,6 @@ an OGC API implementation ecosystem.
 _GeoJSON_ can provide a compact and machine readable encoding as a baseline for message notification.
 
 include::../requirements/pubsub-message-payload/REQ_rc-geojson.adoc[]
-include::../recommendations/pubsub-message-payload/REC_links.adoc[]
 
 ==== Identifier