Henry Andrews

@gregsdennis are you aware of any implementations other than AJV and Opis that require configuration to pass the suite?

I've added this in a PR on the CONTRIBUTING.md file in the spec repo. If that is approved, we should also add the key points about updating meta-schemas on the...

We now have a different approach to meta-schema versioning and should explain that. We should also explain that the unversioned URIs shouldn't be used, and why they do weird HTML...

Everything in JSON Schema is addressed using URI-references (including full URIs) ***or*** Relative JSON Pointer. Those are the two things that we use today (URIs everywhere, Relative JSON pointer in...

Also, JSON Schema does not include anything about performing I/O to fetch schemas or other resources. This will get addressed in detail through json-schema-org/json-schema-spec#849. But it's worth calling out. JSON...

_Might as well bring the comment over. The rest of this was not written by me:_ ----- JSON Schema doesn't support inheritance. You can combine schemas using boolean operations in...

@PaulCezanneFMR that's a good question. I think it depends on what you're trying to get out of JSON Schema. The Validation vocabulary is not really ideal for code generation tools,...

@epoberezkin I would also be plenty happy with something like: `ajv validate -s foo.json -p /some/pointer/to/whatever -d bar.json` perhaps with the limitation that only one -s can be used if...

> `validate` and `test` only allow a single schema anyway LOL I'm still at the `compile` phase :-)

I'll look into it :)