Skip to content
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

clarify that a meta-schema applies to the schema resource, not necessarily the whole document #1559

Merged
merged 1 commit into from
Nov 28, 2024
Merged

clarify that a meta-schema applies to the schema resource, not necessarily the whole document #1559

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
8 changes: 5 additions & 3 deletions specs/jsonschema-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -833,9 +833,11 @@ Meta-schemas are used to inform an implementation how to interpret a schema.
Every schema has a meta-schema, which can be explicitly declared using the
`$schema` keyword.

The meta-schema serves to describe valid schema syntax. A schema MUST
The meta-schema serves to describe valid schema syntax. A schema resource MUST
successfully validate against its meta-schema, which constrains the syntax of
the available keywords. The syntax described for a given keyword is expected to
the available keywords. (See {{compound-validation}} for information on
validating schemas which contain embedded schema resources that declare a
different meta-schema.) The syntax described for a given keyword is expected to
be compatible with the document which defines the keyword; while it is possible
to describe an incompatible syntax, such a meta-schema would be unlikely to be
useful.
Expand Down Expand Up @@ -1339,7 +1341,7 @@ Since any schema that can be referenced can also be embedded, embedded schema
resources MAY specify different processing dialects using the `$schema` values
from their enclosing resource.

#### Validating
#### Validating {#compound-validation}

Given that a Compound Schema Document may have embedded resources which identify
as using different dialects, these documents SHOULD NOT be validated by applying
Expand Down
Loading