You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Draft 5 contains the following information about the $schema keyword:
The "$schema" keyword is both used as a JSON Schema version identifier
and the location of a resource which is itself a JSON Schema, which describes
any schema written for this particular version. [...] The current schema MUST
be valid against the meta-schema identified by this URI.
However, there is no JSON file available at http://json-schema.org/draft-05/schema# which would serve as the resource to validate against. (Other URIs, such as http://json-schema.org/schema# or http://json-schema.org/draft-04/schema#, do return a JSON document as expected.)
Since Draft 5 is an official IETF draft that users may validate against, there should be a JSON document made available at http://json-schema.org/draft-05/schema# as well.
The text was updated successfully, but these errors were encountered:
@dwhieb The intention with the latest release was to be backwards-compatible with the existing meta-schema. This was accomplished with a questionable amount of success in some areas, but JSON Schema Validation should, indeed, be entirely backwards compatible with the draft-04 meta-schema.
Unfortunately, the Validation and Hyper-schema documents never listed a URI to use for a meta-schema, and the latest I-D still doesn't, but this will be fixed when the next meta-schema is released. This is the top item on the priority list, so it's coming soon!
Also I'm obligated to point out, the Internet-Draft is only an individual submission at this point, it doesn't have the endorsement of the IETF until it's released as an RFC. If you need to refer to it in a specification or cite it in a paper, drop me an email so we can discuss options.
@awwright Yes, that makes perfect sense. Thanks for taking the time to clarify! And for all the awesome work on this. I'm excited to see JSON Schema on its way to becoming an official RFC again.
Draft 5 contains the following information about the
$schema
keyword:However, there is no JSON file available at
http://json-schema.org/draft-05/schema#
which would serve as the resource to validate against. (Other URIs, such ashttp://json-schema.org/schema#
orhttp://json-schema.org/draft-04/schema#
, do return a JSON document as expected.)Since Draft 5 is an official IETF draft that users may validate against, there should be a JSON document made available at
http://json-schema.org/draft-05/schema#
as well.The text was updated successfully, but these errors were encountered: