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
Hi folks,
I'm dropping by from the JSON Schema specification project to let you know that JSON Schema is now up to draft-07, with an increasing number of implementations supporting at least draft-06 and a few supporting draft-07. (draft-05 was a wording improvement of draft-04 and is not separately implemented).
Since you are generating schemas, I believe that all you would have to do to claim compatibility is:
Be able to produce draft-06 and/or draft-07 $schema values.
Support using $id instead of id (changed in draft-06, id was too easily confused with very common "id" instance object properties)
If you use exclusiveMinimum or exclusiveMaximum, they are now numbers instead of being boolean modifiers to minimum or maximum (changed in draft-06)
Make sure that you are only using $ref where a schema is expected (most people do this already)
On the json-schema.org web site, we will be moving tools that support only draft-04 and older to a separate page for legacy/obsolete implementations. The main implementations page will focus on tools supporting draft-06 or later.
Please let me know if you have any questions, and of course feel free to close this if you will not be updating. This is a notification, not a demand :-)
The text was updated successfully, but these errors were encountered:
Hi folks,
I'm dropping by from the JSON Schema specification project to let you know that JSON Schema is now up to draft-07, with an increasing number of implementations supporting at least draft-06 and a few supporting draft-07. (draft-05 was a wording improvement of draft-04 and is not separately implemented).
Since you are generating schemas, I believe that all you would have to do to claim compatibility is:
Be able to produce draft-06 and/or draft-07
$schema
values.Support using
$id
instead ofid
(changed in draft-06,id
was too easily confused with very common "id" instance object properties)If you use
exclusiveMinimum
orexclusiveMaximum
, they are now numbers instead of being boolean modifiers tominimum
ormaximum
(changed in draft-06)Make sure that you are only using
$ref
where a schema is expected (most people do this already)On the json-schema.org web site, we will be moving tools that support only draft-04 and older to a separate page for legacy/obsolete implementations. The main implementations page will focus on tools supporting draft-06 or later.
Please let me know if you have any questions, and of course feel free to close this if you will not be updating. This is a notification, not a demand :-)
The text was updated successfully, but these errors were encountered: