Henry Andrews

draft-07: more relative JSON pointer tests

8

They should probably include analogues of all of the absolute JSON Pointer tests from the JSON Pointer spec test case list. And there may be some other specific relative pointer...

`unevaluatedItems` should apply to instance items past the end of the `items` tuple the same way as `additionalItems`, except that it works with `items` across a reference or `allOf` or...

We should have a test that verifies that `$ref` is not affected by `$recursiveAnchor`

This has come up as a question a few times. `propertyNames` doesn't interact with other keywords. - [ ] `additionalProperties` and `propertyNames` (applies to earlier drafts as well) - [...

Questions about the JSON-LD JSON Schema

30

Hi folks, Some documents, such as the [W3C Web of Things "Thing Description"](https://w3c.github.io/wot-thing-description/proposals/simplified-td/), use JSON-LD and JSON Schema in the same document. Over at the JSON Schema project, we are...

Should "contentSchema" have schema location behavior?

4

For the purpose of this issue (and consistent with #1306), "schema location behavior" means that a keyword indicates that some part(s) of its value are schemas and MUST be recognized...

While I am generally in favor of allowing extension keywords to do anything that JSON Schema Org keywords can do, I think we should clearly lock down resource identification and...

Issue #1304 proposes forbidding extension keywords from being able to create embedded resources or change the base IRI. Should extension keywords be able to assign IRIs at all? Assigning an...

Fixes #1276 regarding the lack of discussion of runtime errors. This intentionally avoids saying anything at all about the mechanism or format of any of the outcomes.

This issue is _not_ intended to make fundamental changes, just address the overly-broad "implementation-defined" behavior by excluding obviously problematic behaviors. Doing this does not preclude further changes to `$schema` and/or...