Skip to content
This repository was archived by the owner on Nov 2, 2023. It is now read-only.

Commit d129813

Browse files
handrewshandrews
committed
WIP fix for draft/2019-xx
1 parent 5608a74 commit d129813

6 files changed

+77
-77
lines changed

‎work-in-progress/WIP-jsonschema-core.html

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1124,8 +1124,8 @@ <h1 id="rfc.section.8.5">
11241124
<p id="rfc.section.8.5.p.2">The Core vocabulary MUST be considered mandatory at all times, in order to bootstrap the processing of further vocabularies. Meta-schemas that use "$vocabulary" MUST explicitly list the Core vocabulary, which MUST have a value of true indicating that it is required. </p>
11251125
<p id="rfc.section.8.5.p.3">The behavior of a false value for this vocabulary (and only this vocabulary) is undefined, as is the behavior when "$vocabulary" is present but the Core vocabulary is not included. However, it is RECOMMENDED that implementations detect these cases and raise an error when they occur. </p>
11261126
<p id="rfc.section.8.5.p.4">Meta-schemas that do not use "$vocabulary" MUST be considered to require the Core vocabulary as if its URI were present with a value of true. </p>
1127-
<p id="rfc.section.8.5.p.5">The current URI for the Core vocabulary is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-08/vocab/core">https://json-schema.org/draft/2019-08/vocab/core</a><span>&gt;</span>. </p>
1128-
<p id="rfc.section.8.5.p.6">The current URI for the corresponding meta-schema is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-08/meta/core">https://json-schema.org/draft/2019-08/meta/core</a><span>&gt;</span>. </p>
1127+
<p id="rfc.section.8.5.p.5">The current URI for the Core vocabulary is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-WIP/vocab/core">https://json-schema.org/draft/2019-WIP/vocab/core</a><span>&gt;</span>. </p>
1128+
<p id="rfc.section.8.5.p.6">The current URI for the corresponding meta-schema is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-WIP/meta/core">https://json-schema.org/draft/2019-WIP/meta/core</a><span>&gt;</span>. </p>
11291129
<p id="rfc.section.8.5.p.7">Updated vocabulary and meta-schema URIs MAY be published between specification drafts in order to correct errors. Implementations SHOULD consider URIs dated after this specification draft and before the next to indicate the same syntax and semantics as those listed here. </p>
11301130
<h1 id="rfc.section.8.6">
11311131
<a href="#rfc.section.8.6">8.6.</a> <a href="#example-meta-schema" id="example-meta-schema">Example Meta-Schema With Vocabulary Declarations</a>
@@ -1134,16 +1134,16 @@ <h1 id="rfc.section.8.6">
11341134
<pre>
11351135

11361136
{
1137-
"$schema": "https://json-schema.org/draft/2019-08/core-app-example#",
1138-
"$id": "https://json-schema.org/draft/2019-08/core-app-example",
1137+
"$schema": "https://json-schema.org/draft/2019-WIP/core-app-example#",
1138+
"$id": "https://json-schema.org/draft/2019-WIP/core-app-example",
11391139
"$recursiveAnchor": true,
11401140
"$vocabulary": {
1141-
"https://json-schema.org/draft/2019-08/vocab/core": true,
1142-
"https://json-schema.org/draft/2019-08/vocab/applicator": true
1141+
"https://json-schema.org/draft/2019-WIP/vocab/core": true,
1142+
"https://json-schema.org/draft/2019-WIP/vocab/applicator": true
11431143
},
11441144
"allOf": [
1145-
{"$ref": "https://json-schema.org/draft/2019-08/meta/core"},
1146-
{"$ref": "https://json-schema.org/draft/2019-08/meta/applicator"}
1145+
{"$ref": "https://json-schema.org/draft/2019-WIP/meta/core"},
1146+
{"$ref": "https://json-schema.org/draft/2019-WIP/meta/applicator"}
11471147
],
11481148
"patternProperties": {
11491149
"^unevaluated.*$": false
@@ -1303,7 +1303,7 @@ <h1 id="rfc.section.9.3.2">
13031303
<pre>
13041304

13051305
{
1306-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1306+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
13071307
"$id": "https://example.com/original",
13081308

13091309
"properties": {
@@ -1317,7 +1317,7 @@ <h1 id="rfc.section.9.3.2">
13171317
}
13181318

13191319
{
1320-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1320+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
13211321
"$id": "https://example.com/extension",
13221322

13231323
"$ref": "original",
@@ -1359,7 +1359,7 @@ <h1 id="rfc.section.9.3.2.2">
13591359
<pre>
13601360

13611361
{
1362-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1362+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
13631363
"$id": "https://example.com/original",
13641364
"$recursiveAnchor": true,
13651365

@@ -1374,7 +1374,7 @@ <h1 id="rfc.section.9.3.2.2">
13741374
}
13751375

13761376
{
1377-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1377+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
13781378
"$id": "https://example.com/extension",
13791379
"$recursiveAnchor": true,
13801380

@@ -1460,8 +1460,8 @@ <h1 id="rfc.section.11">
14601460
<a href="#rfc.section.11">11.</a> A Vocabulary for Applying Subschemas</h1>
14611461
<p id="rfc.section.11.p.1">This section defines a vocabulary of applicator keywords that are RECOMMENDED for use as the basis of other vocabularies. </p>
14621462
<p id="rfc.section.11.p.2">Meta-schemas that do not use "$vocabulary" SHOULD be considered to require this vocabulary as if its URI were present with a value of true. </p>
1463-
<p id="rfc.section.11.p.3">The current URI for this vocabulary, known as the Applicator vocabulary, is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-08/vocab/applicator">https://json-schema.org/draft/2019-08/vocab/applicator</a><span>&gt;</span>. </p>
1464-
<p id="rfc.section.11.p.4">The current URI for the corresponding meta-schema is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-08/meta/applicator">https://json-schema.org/draft/2019-08/meta/applicator</a><span>&gt;</span>. </p>
1463+
<p id="rfc.section.11.p.3">The current URI for this vocabulary, known as the Applicator vocabulary, is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-WIP/vocab/applicator">https://json-schema.org/draft/2019-WIP/vocab/applicator</a><span>&gt;</span>. </p>
1464+
<p id="rfc.section.11.p.4">The current URI for the corresponding meta-schema is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-WIP/meta/applicator">https://json-schema.org/draft/2019-WIP/meta/applicator</a><span>&gt;</span>. </p>
14651465
<p id="rfc.section.11.p.5">Updated vocabulary and meta-schema URIs MAY be published between specification drafts in order to correct errors. Implementations SHOULD consider URIs dated after this specification draft and before the next to indicate the same syntax and semantics as those listed here. </p>
14661466
<h1 id="rfc.section.11.1">
14671467
<a href="#rfc.section.11.1">11.1.</a> Keyword Independence</h1>
@@ -1646,7 +1646,7 @@ <h1 id="rfc.section.12.3.2">
16461646
<p id="rfc.section.12.3.2.p.1">The absolute, dereferenced location of the validating keyword. The value MUST be expressed as an absolute URI, and it MUST NOT include by-reference applicators such as "$ref" or "$recursiveRef". </p>
16471647
<pre>
16481648

1649-
https://json-schema.org/draft/2019-08/schema#/$defs/nonNegativeInteger/minimum
1649+
https://json-schema.org/draft/2019-WIP/schema#/$defs/nonNegativeInteger/minimum
16501650

16511651
</pre>
16521652
<p id="rfc.section.12.3.2.p.2">This information MAY be omitted only if either the relative location contains no references or if the schema does not declare an absolute URI as its "$id". </p>
@@ -1679,7 +1679,7 @@ <h1 id="rfc.section.12.4">
16791679

16801680
{
16811681
"$id": "https://example.com/polygon#",
1682-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1682+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
16831683
"$defs": {
16841684
"point": {
16851685
"type": "object",
@@ -1830,13 +1830,13 @@ <h1 id="rfc.section.12.4.4">
18301830
<a href="#rfc.section.12.4.4">12.4.4.</a> Verbose</h1>
18311831
<p id="rfc.section.12.4.4.p.1">The "Verbose" structure is a fully realized hierarchy that exactly matches that of the schema. This structure has applications in form generation and validation where the error's location is important. </p>
18321832
<p id="rfc.section.12.4.4.p.2">The primary difference between this and the "Detailed" structure is that all results are returned. This includes sub-schema validation results that would otherwise be removed (e.g. annotations for failed validations, successful validations inside a `not` keyword, etc.). Because of this, it is RECOMMENDED that each node also carry a `valid` property to indicate the validation result for that node. </p>
1833-
<p id="rfc.section.12.4.4.p.3">Because this output structure can be quite large, a smaller example is given here for brevity. The URI of the full output structure of the example above is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-08/output/verbose-example">https://json-schema.org/draft/2019-08/output/verbose-example</a><span>&gt;</span>. </p>
1833+
<p id="rfc.section.12.4.4.p.3">Because this output structure can be quite large, a smaller example is given here for brevity. The URI of the full output structure of the example above is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-WIP/output/verbose-example">https://json-schema.org/draft/2019-WIP/output/verbose-example</a><span>&gt;</span>. </p>
18341834
<pre>
18351835

18361836
// schema
18371837
{
18381838
"$id": "https://example.com/polygon#",
1839-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1839+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
18401840
"type": "object",
18411841
"properties": {
18421842
"validProp": true,
@@ -1885,7 +1885,7 @@ <h1 id="rfc.section.12.4.4">
18851885
</pre>
18861886
<h1 id="rfc.section.12.4.5">
18871887
<a href="#rfc.section.12.4.5">12.4.5.</a> Output validation schemas</h1>
1888-
<p id="rfc.section.12.4.5.p.1">For convenience, JSON Schema has been provided to validate output generated by implementations. Its URI is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-08/output/schema">https://json-schema.org/draft/2019-08/output/schema</a><span>&gt;</span>. </p>
1888+
<p id="rfc.section.12.4.5.p.1">For convenience, JSON Schema has been provided to validate output generated by implementations. Its URI is: <span>&lt;</span><a href="https://json-schema.org/draft/2019-WIP/output/schema">https://json-schema.org/draft/2019-WIP/output/schema</a><span>&gt;</span>. </p>
18891889
<h1 id="rfc.section.13">
18901890
<a href="#rfc.section.13">13.</a> <a href="#hypermedia" id="hypermedia">Usage for Hypermedia</a>
18911891
</h1>

‎work-in-progress/WIP-jsonschema-core.txt

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1371,10 +1371,10 @@ Internet-Draft JSON Schema August 2019
13711371
of true.
13721372

13731373
The current URI for the Core vocabulary is: <https://json-schema.org/
1374-
draft/2019-08/vocab/core>.
1374+
draft/2019-WIP/vocab/core>.
13751375

13761376
The current URI for the corresponding meta-schema is: <https://json-
1377-
schema.org/draft/2019-08/meta/core>.
1377+
schema.org/draft/2019-WIP/meta/core>.
13781378

13791379
Updated vocabulary and meta-schema URIs MAY be published between
13801380
specification drafts in order to correct errors. Implementations
@@ -1413,16 +1413,16 @@ Internet-Draft JSON Schema August 2019
14131413

14141414

14151415
{
1416-
"$schema": "https://json-schema.org/draft/2019-08/core-app-example#",
1417-
"$id": "https://json-schema.org/draft/2019-08/core-app-example",
1416+
"$schema": "https://json-schema.org/draft/2019-WIP/core-app-example#",
1417+
"$id": "https://json-schema.org/draft/2019-WIP/core-app-example",
14181418
"$recursiveAnchor": true,
14191419
"$vocabulary": {
1420-
"https://json-schema.org/draft/2019-08/vocab/core": true,
1421-
"https://json-schema.org/draft/2019-08/vocab/applicator": true
1420+
"https://json-schema.org/draft/2019-WIP/vocab/core": true,
1421+
"https://json-schema.org/draft/2019-WIP/vocab/applicator": true
14221422
},
14231423
"allOf": [
1424-
{"$ref": "https://json-schema.org/draft/2019-08/meta/core"},
1425-
{"$ref": "https://json-schema.org/draft/2019-08/meta/applicator"}
1424+
{"$ref": "https://json-schema.org/draft/2019-WIP/meta/core"},
1425+
{"$ref": "https://json-schema.org/draft/2019-WIP/meta/applicator"}
14261426
],
14271427
"patternProperties": {
14281428
"^unevaluated.*$": false
@@ -1748,7 +1748,7 @@ Internet-Draft JSON Schema August 2019
17481748

17491749

17501750
{
1751-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1751+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
17521752
"$id": "https://example.com/original",
17531753

17541754
"properties": {
@@ -1762,7 +1762,7 @@ Internet-Draft JSON Schema August 2019
17621762
}
17631763

17641764
{
1765-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1765+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
17661766
"$id": "https://example.com/extension",
17671767

17681768
"$ref": "original",
@@ -1860,7 +1860,7 @@ Internet-Draft JSON Schema August 2019
18601860

18611861

18621862
{
1863-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1863+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
18641864
"$id": "https://example.com/original",
18651865
"$recursiveAnchor": true,
18661866

@@ -1875,7 +1875,7 @@ Internet-Draft JSON Schema August 2019
18751875
}
18761876

18771877
{
1878-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
1878+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
18791879
"$id": "https://example.com/extension",
18801880
"$recursiveAnchor": true,
18811881

@@ -2135,11 +2135,11 @@ Internet-Draft JSON Schema August 2019
21352135
true.
21362136

21372137
The current URI for this vocabulary, known as the Applicator
2138-
vocabulary, is: <https://json-schema.org/draft/2019-08/vocab/
2138+
vocabulary, is: <https://json-schema.org/draft/2019-WIP/vocab/
21392139
applicator>.
21402140

21412141
The current URI for the corresponding meta-schema is: <https://json-
2142-
schema.org/draft/2019-08/meta/applicator>.
2142+
schema.org/draft/2019-WIP/meta/applicator>.
21432143

21442144
Updated vocabulary and meta-schema URIs MAY be published between
21452145
specification drafts in order to correct errors. Implementations
@@ -2678,7 +2678,7 @@ Internet-Draft JSON Schema August 2019
26782678
by-reference applicators such as "$ref" or "$recursiveRef".
26792679

26802680

2681-
https://json-schema.org/draft/2019-08/schema#/$defs/nonNegativeInteger/minimum
2681+
https://json-schema.org/draft/2019-WIP/schema#/$defs/nonNegativeInteger/minimum
26822682

26832683

26842684

@@ -2748,7 +2748,7 @@ Internet-Draft JSON Schema August 2019
27482748

27492749
{
27502750
"$id": "https://example.com/polygon#",
2751-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
2751+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
27522752
"$defs": {
27532753
"point": {
27542754
"type": "object",
@@ -3033,14 +3033,14 @@ Internet-Draft JSON Schema August 2019
30333033

30343034
Because this output structure can be quite large, a smaller example
30353035
is given here for brevity. The URI of the full output structure of
3036-
the example above is: <https://json-schema.org/draft/2019-08/output/
3036+
the example above is: <https://json-schema.org/draft/2019-WIP/output/
30373037
verbose-example>.
30383038

30393039

30403040
// schema
30413041
{
30423042
"$id": "https://example.com/polygon#",
3043-
"$schema": "https://json-schema.org/draft/2019-08/schema#",
3043+
"$schema": "https://json-schema.org/draft/2019-WIP/schema#",
30443044
"type": "object",
30453045
"properties": {
30463046
"validProp": true,
@@ -3099,7 +3099,7 @@ Internet-Draft JSON Schema August 2019
30993099

31003100
For convenience, JSON Schema has been provided to validate output
31013101
generated by implementations. Its URI is: <https://json-schema.org/
3102-
draft/2019-08/output/schema>.
3102+
draft/2019-WIP/output/schema>.
31033103

31043104
13. Usage for Hypermedia
31053105

0 commit comments

Comments
 (0)