Merge branch 'master' into master

.all-contributorsrc

@@ -474,6 +474,15 @@
         "doc",
         "maintenance"
       ]
+    },
+    {
+      "login": "Lazzaretti",
+      "name": "Fabrizio Lazzaretti",
+      "avatar_url": "https://avatars.githubusercontent.com/u/7142819?v=4",
+      "profile": "https://lazzaretti.me/",
+      "contributions": [
+        "doc"
+      ]
     }
   ],
   "commitConvention": "none",

README.md

@@ -43,7 +43,8 @@
 The latest draft specification can be found at [spec/asyncapi.md](./spec/asyncapi.md) which tracks the latest commit to the master branch in this repository.
 The human-readable markdown file is the source of truth for the specification.
 
-- [Version 2.6.0](https://github.com/asyncapi/spec/blob/v2.6.0/spec/asyncapi.md) (latest)
+- [Version 3.0.0](https://github.com/asyncapi/spec/blob/v3.0.0/spec/asyncapi.md) (latest)
+- [Version 2.6.0](https://github.com/asyncapi/spec/blob/v2.6.0/spec/asyncapi.md)
 - [Version 2.5.0](https://github.com/asyncapi/spec/blob/v2.5.0/spec/asyncapi.md)
 - [Version 2.4.0](https://github.com/asyncapi/spec/blob/v2.4.0/spec/asyncapi.md)
 - [Version 2.3.0](https://github.com/asyncapi/spec/blob/v2.3.0/spec/asyncapi.md)
@@ -205,6 +206,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
       <td align="center" valign="top" width="11.11%"><a href="https://github.com/nickshoe"><img src="https://avatars.githubusercontent.com/u/32668766?v=4?s=100" width="100px;" alt="nickshoe"/><br /><sub><b>nickshoe</b></sub></a><br /><a href="https://github.com/asyncapi/spec/issues?q=author%3Anickshoe" title="Bug reports">🐛</a> <a href="https://github.com/asyncapi/spec/commits?author=nickshoe" title="Documentation">📖</a></td>
       <td align="center" valign="top" width="11.11%"><a href="https://github.com/AceTheCreator"><img src="https://avatars.githubusercontent.com/u/40604284?v=4?s=100" width="100px;" alt="Ace "/><br /><sub><b>Ace </b></sub></a><br /><a href="#eventOrganizing-AceTheCreator" title="Event Organizing">📋</a> <a href="#ideas-AceTheCreator" title="Ideas, Planning, & Feedback">🤔</a> <a href="#maintenance-AceTheCreator" title="Maintenance">🚧</a> <a href="#talk-AceTheCreator" title="Talks">📢</a></td>
       <td align="center" valign="top" width="11.11%"><a href="https://github.com/AnimeshKumar923"><img src="https://avatars.githubusercontent.com/u/99868037?v=4?s=100" width="100px;" alt="Animesh Kumar"/><br /><sub><b>Animesh Kumar</b></sub></a><br /><a href="#content-AnimeshKumar923" title="Content">🖋</a> <a href="https://github.com/asyncapi/spec/commits?author=AnimeshKumar923" title="Documentation">📖</a> <a href="#maintenance-AnimeshKumar923" title="Maintenance">🚧</a></td>
+      <td align="center" valign="top" width="11.11%"><a href="https://lazzaretti.me/"><img src="https://avatars.githubusercontent.com/u/7142819?v=4?s=100" width="100px;" alt="Fabrizio Lazzaretti"/><br /><sub><b>Fabrizio Lazzaretti</b></sub></a><br /><a href="https://github.com/asyncapi/spec/commits?author=Lazzaretti" title="Documentation">📖</a></td>
     </tr>
   </tbody>
 </table>

examples/adeo-kafka-request-reply-asyncapi.yml

@@ -206,59 +206,69 @@ components:
     RequesterId:
       type: string
       description: The Costing requester service account used to produce costing request.
-      example: svc-ecollect-app
+      examples:
+        - svc-ecollect-app
     RequesterCode:
       type: string
       description: >-
         The Costing requester code (generally the BU Code). The requester code
         is useful to get the dedicated context (tenant).
-      example: 1
+      examples:
+        - 1
     MessageId:
       type: string
       format: uuid
       description: A unique Message ID.
-      example: 1fa6ef40-8f47-40a8-8cf6-f8607d0066ef
+      examples:
+        - 1fa6ef40-8f47-40a8-8cf6-f8607d0066ef
     RequestId:
       type: string
       format: uuid
       description: >-
         A unique Request ID needed to define a `CORRELATION_ID` for exchanges,
         which will be sent back in the Costing Responses.
-      example: 1fa6ef40-8f47-40a8-8cf6-f8607d0066ef
+      examples:
+        - 1fa6ef40-8f47-40a8-8cf6-f8607d0066ef
     CorrelationId:
       type: string
       format: uuid
       description: >-
         A unique Correlation ID defined from the `REQUEST_ID` or the
         `MESSAGE_ID` provided in the Costing Request.
-      example: 1fa6ef40-8f47-40a8-8cf6-f8607d0066ef
+      examples:
+        - 1fa6ef40-8f47-40a8-8cf6-f8607d0066ef
     BuCode:
       type: string
       description: The Business Unit code for which data are applicable.
-      example: 1
+      examples:
+        - 1
     ReplyTopic:
       type: string
       description: >
         The Kafka topic where to send the Costing Response. This is required for
         the [Return Address EIP
         pattern](https://www.enterpriseintegrationpatterns.com/patterns/messaging/ReturnAddress.html).
         **You must grant WRITE access to our `svc-ccr-app` service account.**
-      example: adeo-case-study-COSTING-RESPONSE-V1
+      examples:
+        - adeo-case-study-COSTING-RESPONSE-V1
     ErrorStep:
       type: string
       description: |
         The woker that has thrown the error.
-      example: EXPOSE_RESULT
+      examples:
+        - EXPOSE_RESULT
     ErrorMessage:
       type: string
       description: |
         The error message describing the error.
-      example: Error message
+      examples:
+        - Error message
     ErrorCode:
       type: string
       description: |
         The error code.
-      example: CURRENCY_NOT_FOUND
+      examples:
+        - CURRENCY_NOT_FOUND
   parameters:
     Env:
       description: Adeo Kafka Environement for messages publications.

spec/asyncapi.md

@@ -1874,7 +1874,7 @@ The Schema Object allows the definition of input and output data types.
 These types can be objects, but also primitives and arrays. This object is a superset of the [JSON Schema Specification Draft 07](https://json-schema.org/). The empty schema (which allows any instance to validate) MAY be represented by the `boolean` value `true` and a schema which allows no instance to validate MAY be represented by the `boolean` value `false`.
 
 Further information about the properties can be found in [JSON Schema Core](https://tools.ietf.org/html/draft-handrews-json-schema-01) and [JSON Schema Validation](https://tools.ietf.org/html/draft-handrews-json-schema-validation-01).
-Unless stated otherwise, the property definitions follow the JSON Schema specification as referenced here.
+Unless stated otherwise, the property definitions follow the JSON Schema specification as referenced here. For other formats (e.g., Avro, RAML, etc) see [Multi Format Schema Object](#multiFormatSchemaObject).
 
 ##### Properties