Skip to content

Strengthen requirements on optional vocabularies and unknown keywords #1376

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

Closed
wants to merge 1 commit into from
Closed

Strengthen requirements on optional vocabularies and unknown keywords #1376

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 4 additions & 3 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -620,8 +620,9 @@

<section title="Handling of unrecognized or unsupported keywords" anchor="unrecognized">
<t>
Implementations SHOULD treat keywords they do not recognize, or that
they recognize but do not support, as annotations, where the value of
If annotation collection is supported and not disabled, implementations
MUST treat keywords they do not recognize, or that they recognize but
do not support, as annotations, where the collected value of
the keyword is the value of the annotation. Whether an implementation
collects these annotations or not, they MUST otherwise ignore the keywords.
</t>
Expand Down Expand Up @@ -1298,7 +1299,7 @@
</t>
<t>
Implementations that do not support a vocabulary that is optionally used
by a schema SHOULD proceed with processing the schema. The keywords will
by a schema MUST proceed with processing the schema. The keywords will
be considered to be unrecognized keywords as addressed by
<xref target="unrecognized"></xref>. Note that since
the recommended behavior for such keywords is to collect them as
Expand Down