@@ -833,9 +833,11 @@ Meta-schemas are used to inform an implementation how to interpret a schema.
833
833
Every schema has a meta-schema, which can be explicitly declared using the
834
834
` $schema ` keyword.
835
835
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
837
837
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
839
841
be compatible with the document which defines the keyword; while it is possible
840
842
to describe an incompatible syntax, such a meta-schema would be unlikely to be
841
843
useful.
@@ -1339,7 +1341,7 @@ Since any schema that can be referenced can also be embedded, embedded schema
1339
1341
resources MAY specify different processing dialects using the ` $schema ` values
1340
1342
from their enclosing resource.
1341
1343
1342
- #### Validating
1344
+ #### Validating {#compound-validation}
1343
1345
1344
1346
Given that a Compound Schema Document may have embedded resources which identify
1345
1347
as using different dialects, these documents SHOULD NOT be validated by applying
0 commit comments