Skip to content

Require at least one JSON Schema version #184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 31, 2023
Merged

Require at least one JSON Schema version #184

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0c6ddd9
fix 180
Jul 25, 2023
a3c30a0
add note on stable version
Jul 25, 2023
c5e25d7
Apply suggestions from code review
decentralgabe Jul 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 23 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -335,32 +335,47 @@ <h2>JSON Schema Specifications</h2>
The following section describes the allowed specifications for
using a [[JSON-Schema]] with a <a>credential schema</a>.
</p>
<p>
To promote conformance and enable interoperability, implementers MUST
provide support for JSON Schema specifications where, in the following table,
the <i>required</i> column's value is <b>yes</b>.
</p>
<table class="simple">
<thead>
<tr>
<th style="white-space: nowrap">JSON Schema Specification</th>
<th>Date of Publication</th>
<th>$schema URI</th>
<th>Required</th>
</tr>
</thead>
<tbody>
<tr>
<td>[[JSON-SCHEMA-2020-12]]</td>
<td>10 June 2022</td>
<td><a href="https://json-schema.org/draft/2020-12/schema">https://json-schema.org/draft/2020-12/schema</a></td>
<td>Yes</td>
</tr>
<tr>
<td>[[JSON-SCHEMA-2019-09]]</td>
<td>19 March 2020</td>
<td><a href="https://json-schema.org/draft/2019-09/schema">https://json-schema.org/draft/2019-09/schema</a></td>
<td>No</td>
</tr>
<tr>
<td>[[JSON-SCHEMA-DRAFT-7]]</td>
<td>20 September 2018</td>
<td><a href="http://json-schema.org/draft-07/schema#">http://json-schema.org/draft-07/schema#</a></td>
<td>No</td>
</tr>
</tbody>
</table>

<p class="note" title="A stable JSON Schema specification is coming">
<a href="https://json-schema.org/blog/posts/future-of-json-schema">A stable JSON Schema specification</a>
is in the works. When it's released, we intend to update this table to require the stable version.
</p>

<section class="normative">
<h3>Reserved Keywords</h3>
<p>
Expand Down Expand Up @@ -435,11 +450,16 @@ <h2>Processing</h2>
<p>
A common feature of a JSON schema validator is the ability to detect the version of a JSON schema document
and select the validator for that specific version of [[JSON-SCHEMA]]. This is done by switching on the
schema's <code>$schema</code> and picking the corresponding validator. Schemas without a <code>$schema</code>
property are not considered valid and MUST not be processed. It is RECOMMENDED that implementers
choose validators which possess this capability and are able to limit validation to the
schema's <code>$schema</code> property and picking the corresponding validator. Schemas without a
<code>$schema</code> property are not considered valid and MUST NOT be processed. Implementers
SHOULD choose validators which possess this capability and are able to limit validation to the
<a href="#json-schema-specifications">JSON schema specifications</a> supported by this document.
</p>
<p>
Conformant implementers MUST support JSON schema specification versions marked as <b>required</b>
in the table defined in the <a href="#json-schema-specifications">JSON schema specifications section</a>
of this document.
</p>
<section>
<h3>Integrity Validation</h3>
<p>
Expand Down