Skip to content

Latest commit

 

History

History
62 lines (45 loc) · 3.55 KB

specification.md

File metadata and controls

62 lines (45 loc) · 3.55 KB
layout redirect_from permalink title
page
/documentation.html
/specification.html
Specification
  • TOC {:toc}

Draft numbering

The latest Internet-Drafts at the IETF are the draft-handrews-json-schema*-01 documents, which correspond to the draft-07 meta-schemas. These were published on 2018-03-19 (Core and Validation) and 2018-01-19 (Hyper-Schema and Relative JSON Pointer).

Due to a change in author/editorship the I-D numbering was reset to -00 again. Due to bugs in the draft-handrews-*-00 specifications, they have been replaced with -01, but are still considered draft-07 as there is no functional change.

Specification documents

The specification is split into three parts, Core, Validation, and Hyper-Schema, along with a related specification, Relative JSON Pointers:

|--------------------------------------------------------------|-------------------------------------------------------| | JSON Schema Core | defines the basic foundation of JSON Schema | | JSON Schema Validation | defines the validation keywords of JSON Schema | | JSON Hyper-Schema (errata) | defines the hyper-media keywords of JSON Schema | | Relative JSON Pointers | extends the JSON Pointer syntax for relative pointers |

They are also available on the IETF main site:

Meta-schemas

The meta-schemas are schemas against which other schemas can be validated. They are self-descriptive: the JSON Schema meta-schema validates itself, while the JSON Hyper-Schema meta-schema both validates itself and defines its own "self" link. The latest meta-schema is draft-07.

|--------------------------------------------------------------|------------------------------------------------------------| | Core/Validation meta-schema | Used for schemas written for pure validation. | | Hyper meta-schema | Used for schemas written for validation and hyper-linking. |

If you are accessing the above meta-schema links from a web browser, you will need to save the file then open it as a JSON document.

Migrating from older drafts

The release notes discuss the changes impacting users and implementers:

Older drafts

Please see Specification Links for older drafts and the latest unreleased version of the specification.