Skip to content

Commit 0ac0fd9

Browse files
authored
Merge pull request #1559 from json-schema-org/gregsdennis/meta-schema-validation
clarify that a meta-schema applies to the schema resource, not necessarily the whole document
2 parents c6a845b + 19ccdb6 commit 0ac0fd9

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

specs/jsonschema-core.md

+5-3
Original file line numberDiff line numberDiff line change
@@ -833,9 +833,11 @@ Meta-schemas are used to inform an implementation how to interpret a schema.
833833
Every schema has a meta-schema, which can be explicitly declared using the
834834
`$schema` keyword.
835835

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

1342-
#### Validating
1344+
#### Validating {#compound-validation}
13431345

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

0 commit comments

Comments
 (0)