Pavel Bodiachevskii

> From a pure-spec perspective, I agree that allowing use of other Avro versions would be useful > > > > I'm not sure what knock-on impact this will have...

> From the spec perspective, we only say what MUST be supported, and we not say what MUST NOT > > So avro 1.9 is for example recommended, but nobody...

> > latest versions of Schemas > > which ones? > > atm MUST is set only on default AsyncAPI Schema and also on JSON Schema that AsyncAPI Schema is...

> My question is, why you think that setting all schemas to MUST in spec will change anything? I do not recall anyone refusing to support some schema formats. >...

> @Pakisan if they're using OpenAPI Schemas, they should specify so in the schemaFormat field, i.e., it should be `application/vnd.oai.openapi;version=3.0.0`. > > ### Example with v3: > ```yaml > asyncapi:...

> > But I want to clarify validation behavior when users didn't provide any schemaFormat so it must be interpreted as AAS schema > > The behaviour should be to...

nope: ``` AssertionError [ERR_ASSERTION]: Document /Users/pavelbodyachevskiy/IdeaProjects/spec-json-schemas/test/docs/3.0.0/streetlights-all.json must be validated correctly: [ { "instancePath": "/components/schemas/Json-ReferencedSchema", "schemaPath": "#/required", "keyword": "required", "params": { "missingProperty": "$ref" }, "message": "must have required property '$ref'" },...

> @Pakisan it does not solve your problem, but it cleans up the definition even more after your PR is merged. Ok. I thought that this MR is for replace...

@Gadam8 looks good Don't forget to update information about SNS and SQS here: - https://github.com/asyncapi/bindings/tree/master/sns - https://github.com/asyncapi/bindings/tree/master/sqs

@iancooper @dpwdec up!