Henry Andrews

I see that the JSON Schema being used to validate the JSON format is a draft-07 schema. Just in case folks aren't aware, the more recent draft 2020-12 ([core](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html), [validation](https://www.ietf.org/archive/id/draft-bhutton-json-schema-validation-01.html)),...

@jskeet You can read the [discussion of our standards approach](https://github.com/json-schema-org/json-schema-spec/pull/1277), and do note that we are still working with the IETF HTTPAPI working group to register the JSON Schema media...

> Describing a GET body as optional is just terrible. Far too many people don't seem to understand that "has no defined semantics" is standards-ese for "FFS don't do this!"...

This has been floated at the JSON Schema project as a sort of schema evolution feature. We're unlikely to act on it but it could be done in an extension...

You would need to handle the alternative names at the same level as the regular names, because keywords for a single property cannot be applied to the whole object (which...

In recent versions of JSON Schema, this is handled by `"contentMediaType"` and `"contentEncoding"`: https://tools.ietf.org/html/draft-handrews-json-schema-validation-01#section-8 These concepts have been part of JSON Schema since before OpenAPI, but under various names and...

@spacether `binary` is not a valid `contentEncoding` value. The encoding keyword is about transferring binary data as _non-binary_ JSON string data. Per the JSON Schema Validation spec: > Possible values...

@spacether I'm not sure you need a non-empty schema, btw, as the `image/png` part should be handled by the content type of the request or response. Unless it's part of...

It is not location-sensitive. The comment about multipart responses has to do with OpenAPI's Encoding Object, which is an are of considerable complexity outside the scope of JSON Schema.

@spacether > If one location allows ingestion and transmission of binary using AnyType schema and another location allows ingestion of different data with that same schema definition it looks location...