Clarified MUST requirement for JSON format (#644)

* Clarified that JSON format is a MUST, if structured content mode is supported. Signed-off-by: Klaus Deissner <[email protected]> * Added AMQP,Kafka and MQTT Signed-off-by: Klaus Deissner <[email protected]>
cloudevents · Jun 21, 2020 · bf71de5 · bf71de5
1 parent 5ea5b40
commit bf71de5
Show file tree

Hide file tree

Showing 4 changed files with 14 additions and 13 deletions.
diff --git a/amqp-protocol-binding.md b/amqp-protocol-binding.md
@@ -77,7 +77,8 @@ AMQP [application-properties][app-properties] section.
 
 Event formats, used with the _stuctured_ content mode, define how an event is
 expressed in a particular data format. All implementations of this specification
-MUST support the [JSON event format][json-format].
+that support the _structured_ content mode MUST support the [JSON event
+format][json-format].
 
 ### 1.5. Security
 

diff --git a/http-protocol-binding.md b/http-protocol-binding.md
@@ -86,8 +86,9 @@ supports batching.
 
 Event formats, used with the _structured_ content mode, define how an event is
 expressed in a particular data format. All implementations of this specification
-MUST support the non-batching [JSON event format][json-format], but MAY support
-any additional, including proprietary, formats.
+that support the _structured_ content mode MUST support the non-batching [JSON
+event format][json-format], but MAY support any additional, including
+proprietary, formats.
 
 Event formats MAY additionally define how a batch of events is expressed. Those
 can be used with the _batched_ content mode

diff --git a/kafka-protocol-binding.md b/kafka-protocol-binding.md
@@ -76,16 +76,17 @@ the Kafka message's value section as-is, with the `content-type` header value
 declaring its media type; all other event attributes MUST be mapped to the
 Kafka message's [header section][kafka-message-header].
 
-Implementations that use Kafka 0.11.0.0 and above MAY use either _binary_
-or _structured_ modes. Implementations that use Kafka 0.10.x.x and below
-MUST use only use _structured_ mode and encode the event in JSON. This is
-because older versions of Kafka lacked support for message level headers.
+Implementations that use Kafka 0.11.0.0 and above MAY use either _binary_ or
+_structured_ modes. Implementations that use Kafka 0.10.x.x and below MUST only
+use _structured_ mode and encode the event in JSON. This is because older
+versions of Kafka lacked support for message level headers.
 
 ### 1.4. Event Formats
 
 Event formats, used with the _structured_ content mode, define how an event is
-expressed in a particular data format. All implementations of this
-specification MUST support the [JSON event format][json-format].
+expressed in a particular data format. All implementations of this specification
+that support the _structured_ content mode MUST support the [JSON event
+format][json-format].
 
 ### 1.5. Security
 

diff --git a/mqtt-protocol-binding.md b/mqtt-protocol-binding.md
@@ -73,10 +73,8 @@ event attributes are mapped to User Property fields.
 
 Event formats, used with the _structured_ content mode, define how an event is
 expressed in a particular data format. All implementations of this specification
-MUST support the [JSON event format][json-format].
-
-MQTT 5.0 implementations MAY support any additional, including proprietary,
-formats.
+that support the _structured_ content mode MUST support the [JSON event
+format][json-format].
 
 ### 1.5. Security