2020-12 vocabulary schemas should be in vocab/ and not in meta/
ssilverman opened this issue · 3 comments
This way the URI matches the URL on the site.
This issue affects specification.md and the vocabulary schema locations.
The meta-schema URIs are correct, and they match their downloadable locations.
There was an important distinction between the vocabulary ID URI (as seen in the $vocabulary keyword) and the vocabulary's meta-schema $id (as seen in the main meta-schema's allOf which pulls in all of the vocabulary meta-schemas). The vocabulary ID URI is eventually intended to be the URI of another machine-readable non-schema document that describes the keywords in a bit more detail than a subschema can (e.g. in the meta-schema). This other document would define attributes for the keywords such as keyword function (e.g. assertion vs annotation). There's some more discussion in the spec repo issues on this topic, but nothing has been deeply worked out yet.
Both of these are independently required.
I see. This confused me for a little bit, but I think I get the intent of the reasoning you mention.
As @gregsdennis noted, this is correct as-is. One day hopefully we'll have machine-readable vocabulary files.