Skip to content

Commit 83fd0b9

Browse files
authored
docs: align text definition of Message.payload with it's field definition (#983)
1 parent 69ff34d commit 83fd0b9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

spec/asyncapi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ A consumer is a type of application, connected to a [server](#definitionsServer)
104104

105105
### <a name="definitionsMessage"></a>Message
106106

107-
A message is the mechanism by which information is exchanged via a channel between [servers](#definitionsServer) and applications. A message MUST contain a payload and MAY also contain headers. The headers MAY be subdivided into [protocol](#definitionsProtocol)-defined headers and header properties defined by the application which can act as supporting metadata. The payload contains the data, defined by the application, which MUST be serialized into a format (JSON, XML, Avro, binary, etc.). Since a message is a generic mechanism, it can support multiple interaction patterns such as event, command, request, or response.
107+
A message is the mechanism by which information is exchanged via a channel between [servers](#definitionsServer) and applications. A message MAY contain a payload and MAY also contain headers. The headers MAY be subdivided into [protocol](#definitionsProtocol)-defined headers and header properties defined by the application which can act as supporting metadata. The payload contains the data, defined by the application, which MUST be serialized into a format (JSON, XML, Avro, binary, etc.). Since a message is a generic mechanism, it can support multiple interaction patterns such as event, command, request, or response.
108108

109109
### <a name="definitionsChannel"></a>Channel
110110

0 commit comments

Comments
 (0)