|
1058 | 1058 | </t>
|
1059 | 1059 | <t>
|
1060 | 1060 | The current URI for the Core vocabulary is:
|
1061 |
| - <eref target="https://json-schema.org/draft-08/vocabularies/core"/>. |
| 1061 | + <eref target="https://json-schema.org/draft/2019-04/vocab/core"/>. |
1062 | 1062 | </t>
|
1063 | 1063 | <t>
|
1064 | 1064 | The current URI for the corresponding meta-schema is:
|
1065 |
| - <eref target="https://json-schema.org/draft-08/core"/>. |
| 1065 | + <eref target="https://json-schema.org/draft/2019-04/meta/core"/>. |
| 1066 | + </t> |
| 1067 | + <t> |
| 1068 | + Updated vocabulary and meta-schema URIs MAY be published between |
| 1069 | + specification drafts in order to correct errors. Implementations |
| 1070 | + SHOULD consider URIs dated after this specification draft and |
| 1071 | + before the next to indicate the same syntax and semantics |
| 1072 | + as those listed here. |
1066 | 1073 | </t>
|
1067 | 1074 | </section>
|
1068 | 1075 | <section title="Example Meta-Schema With Vocabulary Declarations"
|
|
1081 | 1088 | <artwork>
|
1082 | 1089 | <![CDATA[
|
1083 | 1090 | {
|
1084 |
| - "$schema": "https://json-schema.org/draft-08/core-app-example#", |
1085 |
| - "$id": "https://json-schema.org/draft-08/core-app-example", |
| 1091 | + "$schema": "https://json-schema.org/draft/2019-04/core-app-example#", |
| 1092 | + "$id": "https://json-schema.org/draft/2019-04/core-app-example", |
1086 | 1093 | "$recursiveAnchor": true,
|
1087 | 1094 | "$vocabulary": {
|
1088 |
| - "https://json-schema.org/draft-08/vocabularies/core": true, |
1089 |
| - "https://json-schema.org/draft-08/vocabularies/applicator": true |
| 1095 | + "https://json-schema.org/draft/2019-04/vocab/core": true, |
| 1096 | + "https://json-schema.org/draft/2019-04/vocab/applicator": true |
1090 | 1097 | },
|
1091 | 1098 | "allOf": [
|
1092 |
| - {"$ref": "https://json-schema.org/draft-08/core"}, |
1093 |
| - {"$ref": "https://json-schema.org/draft-08/applicator"} |
| 1099 | + {"$ref": "https://json-schema.org/draft/2019-04/meta/core"}, |
| 1100 | + {"$ref": "https://json-schema.org/draft/2019-04/meta/applicator"} |
1094 | 1101 | ],
|
1095 | 1102 | "patternProperties": {
|
1096 | 1103 | "^unevaluated.*$": false
|
|
1352 | 1359 | <artwork>
|
1353 | 1360 | <![CDATA[
|
1354 | 1361 | {
|
1355 |
| - "$schema": "http://json-schema.org/draft-08/schema#", |
| 1362 | + "$schema": "http://json-schema.org/draft/2019-04/schema#", |
1356 | 1363 | "$id": "https://example.com/original",
|
1357 | 1364 |
|
1358 | 1365 | "properties": {
|
|
1366 | 1373 | }
|
1367 | 1374 |
|
1368 | 1375 | {
|
1369 |
| - "$schema": "http://json-schema.org/draft-08/schema#", |
| 1376 | + "$schema": "http://json-schema.org/draft/2019-04/schema#", |
1370 | 1377 | "$id": "https://example.com/extension",
|
1371 | 1378 |
|
1372 | 1379 | "$ref": "original",
|
|
1465 | 1472 | <artwork>
|
1466 | 1473 | <![CDATA[
|
1467 | 1474 | {
|
1468 |
| - "$schema": "http://json-schema.org/draft-08/schema#", |
| 1475 | + "$schema": "http://json-schema.org/draft/2019-04/schema#", |
1469 | 1476 | "$id": "https://example.com/original",
|
1470 | 1477 | "$recursiveAnchor": true,
|
1471 | 1478 |
|
|
1480 | 1487 | }
|
1481 | 1488 |
|
1482 | 1489 | {
|
1483 |
| - "$schema": "http://json-schema.org/draft-08/schema#", |
| 1490 | + "$schema": "http://json-schema.org/draft/2019-04/schema#", |
1484 | 1491 | "$id": "https://example.com/extension",
|
1485 | 1492 | "$recursiveAnchor": true,
|
1486 | 1493 |
|
|
1916 | 1923 | This section defines a vocabulary of applicator keywords that
|
1917 | 1924 | are RECOMMENDED for use as the basis of other vocabularies.
|
1918 | 1925 | </t>
|
| 1926 | + <t> |
| 1927 | + Meta-schemas that do not use "$vocabulary" SHOULD be considered to |
| 1928 | + require this vocabulary as if its URI were present with a value of true. |
| 1929 | + </t> |
1919 | 1930 | <t>
|
1920 | 1931 | The current URI for this vocabulary, known as the Applicator vocabulary, is:
|
1921 |
| - <eref target="https://json-schema.org/draft-08/vocabularies/applicator"/>. |
| 1932 | + <eref target="https://json-schema.org/draft/2019-04/vocab/applicator"/>. |
1922 | 1933 | </t>
|
1923 | 1934 | <t>
|
1924 | 1935 | The current URI for the corresponding meta-schema is:
|
1925 |
| - <eref target="https://json-schema.org/draft-08/applicator"/>. |
| 1936 | + <eref target="https://json-schema.org/draft/2019-04/meta/applicator"/>. |
1926 | 1937 | </t>
|
1927 | 1938 | <t>
|
1928 |
| - Meta-schemas that do not use "$vocabulary" SHOULD be considered to |
1929 |
| - require this vocabulary as if its URI were present with a value of true. |
| 1939 | + Updated vocabulary and meta-schema URIs MAY be published between |
| 1940 | + specification drafts in order to correct errors. Implementations |
| 1941 | + SHOULD consider URIs dated after this specification draft and |
| 1942 | + before the next to indicate the same syntax and semantics |
| 1943 | + as those listed here. |
1930 | 1944 | </t>
|
1931 | 1945 | <section title="Keyword Independence">
|
1932 | 1946 | <t>
|
|
2514 | 2528 | <figure>
|
2515 | 2529 | <artwork>
|
2516 | 2530 | <![CDATA[
|
2517 |
| -http://json-schema.org/draft-08/schema#/$defs/nonNegativeInteger/minimum |
| 2531 | +http://json-schema.org/draft/2019-04/schema#/$defs/nonNegativeInteger/minimum |
2518 | 2532 | ]]>
|
2519 | 2533 | </artwork>
|
2520 | 2534 | </figure>
|
@@ -2590,7 +2604,7 @@ http://json-schema.org/draft-08/schema#/$defs/nonNegativeInteger/minimum
|
2590 | 2604 | <![CDATA[
|
2591 | 2605 | {
|
2592 | 2606 | "$id": "http://example.com/polygon#",
|
2593 |
| - "$schema": "http://json-schema.org/draft-08/schema#", |
| 2607 | + "$schema": "http://json-schema.org/draft/2019-04/schema#", |
2594 | 2608 | "$defs": {
|
2595 | 2609 | "point": {
|
2596 | 2610 | "type": "object",
|
@@ -2801,16 +2815,16 @@ http://json-schema.org/draft-08/schema#/$defs/nonNegativeInteger/minimum
|
2801 | 2815 | </t>
|
2802 | 2816 | <t>
|
2803 | 2817 | Because this output structure can be quite large, a smaller example is given
|
2804 |
| - here for brevity. The full output structure of the example above can be found |
2805 |
| - <eref target="standardized-output-verbose.json">here</eref>. |
| 2818 | + here for brevity. The URI of the full output structure of the example above is: |
| 2819 | + <eref target="https://json-schema.org/draft/2019-04/output/verbose-example"/>. |
2806 | 2820 | </t>
|
2807 | 2821 | <figure>
|
2808 | 2822 | <artwork>
|
2809 | 2823 | <![CDATA[
|
2810 | 2824 | // schema
|
2811 | 2825 | {
|
2812 | 2826 | "$id": "http://example.com/polygon#",
|
2813 |
| - "$schema": "http://json-schema.org/draft-08/schema#", |
| 2827 | + "$schema": "http://json-schema.org/draft/2019-04/schema#", |
2814 | 2828 | "type": "object",
|
2815 | 2829 | "properties": {
|
2816 | 2830 | "validProp": true,
|
@@ -2860,10 +2874,11 @@ http://json-schema.org/draft-08/schema#/$defs/nonNegativeInteger/minimum
|
2860 | 2874 | </figure>
|
2861 | 2875 | </section>
|
2862 | 2876 |
|
2863 |
| - <section title="Output validation schema"> |
| 2877 | + <section title="Output validation schemas"> |
2864 | 2878 | <t>
|
2865 |
| - For convenience, a JSON Schema has been provided to validate output generated |
2866 |
| - by implementations. It can be found <eref target="schema-output.json">here</eref>. |
| 2879 | + For convenience, JSON Schema has been provided to validate output generated |
| 2880 | + by implementations. Its URI is: |
| 2881 | + <eref target="https://json-schema.org/draft/2019-04/output/schema"/>. |
2867 | 2882 | </t>
|
2868 | 2883 | </section>
|
2869 | 2884 |
|
|
0 commit comments