Henry Andrews

Results 158 issues of Henry Andrews

This was originally filed by @cavanaug as https://github.com/json-schema-org/json-schema-spec/issues/285, where it originally referenced Avro's "aliases" as a starting point. This is probably the most concise explanation from @cavanaug: > Avro schema...

api doc
code gen

The idea of a way to indicate whether array order is significant or not (basically, is this a list or a set) has been suggested numerous times. We would have...

If you have a schema with some non-required named properties and an additionalProperties schema, it is not easy to specify that the schema requires at least one property matching the...

JSON Hyper-Schema is a hypermedia media type. Therefore it defines links for a given document, but it does not have a concept of an API, any more than HTML has...

question
api doc

Hello! If this is still an active project, you may be interested to know that there have been new drafts published adding more features to JSON Schema and cleaning up...

* Ports #3760 * Fixes #1542 This makes the relational requirements of `content` vs `schema` and associated fields more clear. The mutual exclusivity requirement is moved up to the top...

clarification
param serialization

* Ports #3760 * Fixes #1542 This makes the relational requirements of `content` vs `schema` and associated fields more clear. The mutual exclusivity requirement is moved up to the top...

clarification
param serialization

* Ports #3714 * Fixes #3601 Includes an example. This intentionally does not explain how dynamic referencing works, as there are better resources available in both the spec and (more...

schema-object
clarification

TL;DR: I have no idea how to define compliance criteria for `allowEmptyValue: false`, which is the default behavior, with setting `true` being NOT RECOMMENDED. <rant> The clarification added in 3.0.2...

review
param serialization

This is sort-of a port of #3732, but modified because the scenario involved was mostly assumed to be valid based on the more direct text of OAS 2.0. So instead...

clarification
re-use: ref/id resolution