Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: explain Multi Format Schema Object option in Schema Object #1018

Merged
merged 3 commits into from
Feb 12, 2024
Merged

docs: explain Multi Format Schema Object option in Schema Object #1018

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9c2829f
docs: explain Multi Format Schema Object option in Schema Object
Lazzaretti Feb 8, 2024
1c7d844
Update sentence
Lazzaretti Feb 8, 2024
d7c41bd
Merge branch 'master' into feature/explain-multischema-format
Lazzaretti Feb 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion spec/asyncapi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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. Other formats, that are not representable with JSON Schema (e.g., Avro or protobuf) can be included as [Multi Format Schema Object](#multiFormatSchemaObject).
Lazzaretti marked this conversation as resolved.
Show resolved Hide resolved

##### Properties

Expand Down
Loading