|
531 | 531 | </t>
|
532 | 532 | </section>
|
533 | 533 |
|
534 |
| - <section title="Extending JSON Schema"> |
| 534 | + <section title="Extending JSON Schema" anchor="extending"> |
535 | 535 | <t>
|
536 | 536 | Additional schema keywords and schema vocabularies MAY be defined
|
537 | 537 | by any entity. Save for explicit agreement, schema authors SHALL NOT
|
|
1145 | 1145 | MAY use the URL of the vocabulary specification, in a human-readable
|
1146 | 1146 | media type such as text/html or text/plain, as the vocabulary URI.
|
1147 | 1147 | <cref>
|
1148 |
| - Vocabulary documents may be added shortly, or in the next draft. |
| 1148 | + Vocabulary documents may be added in forthcoming drafts. |
1149 | 1149 | For now, identifying the keyword set is deemed sufficient as that,
|
1150 | 1150 | along with meta-schema validation, is how the current "vocabularies"
|
1151 | 1151 | work today. Any future vocabulary document format will be specified
|
|
1158 | 1158 | If the value is true, then implementations that do not recognize
|
1159 | 1159 | the vocabulary MUST refuse to process any schemas that declare
|
1160 | 1160 | this meta-schema with "$schema". If the value is false, implementations
|
1161 |
| - that do not recognize the vocabulary MAY choose to proceed with processing |
| 1161 | + that do not recognize the vocabulary SHOULD proceed with processing |
1162 | 1162 | such schemas.
|
1163 | 1163 | </t>
|
1164 | 1164 | <t>
|
1165 |
| - When processing a schema that uses unrecognized vocabularies, keywords |
1166 |
| - declared by those vocabularies are treated like any other unrecognized |
1167 |
| - keyword, and ignored. |
| 1165 | + Per <xref target="extending" format="counter"></xref>, unrecognized |
| 1166 | + keywords SHOULD be ignored. This remains the case for keywords defined |
| 1167 | + by unrecognized vocabularies. It is not currently possible to distinguish |
| 1168 | + between unrecognized keywords that are defined in vocabularies from |
| 1169 | + those that are not part of any vocabulary. |
1168 | 1170 | </t>
|
1169 | 1171 | <t>
|
1170 | 1172 | The "$vocabulary" keyword SHOULD be used in the root schema of any schema
|
|
0 commit comments