Henry Andrews
Henry Andrews
Hello from the JSON Schema specification team! Does this project intend to update to more recent drafts? We have published some [release migration notes](http://json-schema.org/specification.html#migrating-from-older-drafts) and are happy to answer any...
This is just a bug fix for an accidental oversight. I'm hoping it's non-controversial as I don't think any of us meant to allow arbitrary behaviors for unrecognized keywords. When...
Currently, the Relative JSON Pointer (RJP) specification only specifies how to evaluate an RJP with a document reference. This is actually challenging as typical in-memory representations of JSON documents do...
This is an alternative proposal to #1235 (specifying evaluation of Relative JSON Pointer relative to JSON Pointer). The feature that currently can't be implemented is using `#` to get the...
I've noticed that people often think of `$vocabulary` as a very strange case of keyword, specifically asking why it is in the meta-schema and not the schema. The answer is...
It occurs to me that how a schema is loaded and processed is a very fundamental thing that deserves more emphasis than we are giving it. Loading a referenced schema...
Since `unevaluatedProperties` #556 and `unevaluatedItems` #557 depend on the results of other keywords, not just in the immediate schema object but in subschemas, we need to decide how extension keywords...
We should be consistent when talking about evaluating a schema and an instance together. This is sometimes discussed as being "runtime", which I think is fairly clear although maybe should...
PR #914 had some confusing language around schema resources being linked vs embedded, and how to think about related sets of schema resources and/or documents. We should probably have a...
JSON Hyper-Schema is very much on its own path separate from JSON Schema Core and Validation. I've been going through the issues, and it's a bit hard to see the...