From 3a9c049de23ee2e4584b20980a1389900d92313f Mon Sep 17 00:00:00 2001 From: Vladimir Gorej Date: Tue, 31 Oct 2023 11:38:55 +0100 Subject: [PATCH] docs: align text definition of Message.payload with it's field definition Refs #928 --- spec/asyncapi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/asyncapi.md b/spec/asyncapi.md index e57815747..1c70e9c84 100644 --- a/spec/asyncapi.md +++ b/spec/asyncapi.md @@ -104,7 +104,7 @@ A consumer is a type of application, connected to a [server](#definitionsServer) ### Message -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. +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. ### Channel