Skip to content

Commit ba61045

Browse files
committed
Vocab explanation improvements from gregsdennis
Two improvements extracted from an older PR by Greg: * better wording around "forthcoming drafts" (kept verbatim) * clarification around keywords from unknown vocabularies (loosely inspired by Greg's wording).
1 parent c5a6078 commit ba61045

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

jsonschema-core.xml

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -531,7 +531,7 @@
531531
</t>
532532
</section>
533533

534-
<section title="Extending JSON Schema">
534+
<section title="Extending JSON Schema" anchor="extending">
535535
<t>
536536
Additional schema keywords and schema vocabularies MAY be defined
537537
by any entity. Save for explicit agreement, schema authors SHALL NOT
@@ -1145,7 +1145,7 @@
11451145
MAY use the URL of the vocabulary specification, in a human-readable
11461146
media type such as text/html or text/plain, as the vocabulary URI.
11471147
<cref>
1148-
Vocabulary documents may be added shortly, or in the next draft.
1148+
Vocabulary documents may be added in forthcoming drafts.
11491149
For now, identifying the keyword set is deemed sufficient as that,
11501150
along with meta-schema validation, is how the current "vocabularies"
11511151
work today. Any future vocabulary document format will be specified
@@ -1158,13 +1158,15 @@
11581158
If the value is true, then implementations that do not recognize
11591159
the vocabulary MUST refuse to process any schemas that declare
11601160
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
11621162
such schemas.
11631163
</t>
11641164
<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.
11681170
</t>
11691171
<t>
11701172
The "$vocabulary" keyword SHOULD be used in the root schema of any schema

0 commit comments

Comments
 (0)