Henry Andrews

> I don't feel I was able to get any specific suggestions about what definition we actually use today in conversation -- I'm happy to reopen and give it another...

> If you interpret "vocabulary" as a Vocabulary System vocabulary, the definition is not inclusive of versions of JSON Schema that pre-date the Vocabulary System. Words change over time. We...

@jdesrosiers the goal of these definitions should be to help people understand what these things are now, and how to use them now. Not to future-proof against possible later changes...

Mentioning `$vocabulary` is hardly getting stuck in the weeds. Not everyone reads UJS. I do not agree with your push to remove information from other sources in favor of UJS....

@jdesrosiers after recent events I agree with you, so I'm going to go ahead and close this.

For some reason the preview deployment isn't working- this will get merged once the person who knows about that stuff is back from a conference and can take a look...

> Do you mean what specific features of JSON Schema? The draft version? Should just mean draft support which you have listed. I notice that section doesn't have consistent formatting...

@gregsdennis they do [allow disabling these keywords](https://opis.io/json-schema/2.x/php-loader.html#parser-options). Implementing support for `$vocabulary`, making a vocabulary, and publishing a meta-schema requiring the vocabulary would (like OpenAPI 3.1's extensions) allow the extensions to...

@ricky-rockstar the JSON Schema specification recommends against automatically retrieving references by default. Implementations that do offer automatic retrieval (whether by default or otherwise) are not required to automatically support any...

See also #89.