Skip to content

Commit 6645f38

Browse files
committed
add text about schemas contained in non-schema documents
1 parent a301579 commit 6645f38

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

jsonschema-core.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -885,8 +885,8 @@ meta-schema features emphasizes flexibility over simplicity.
885885
#### Dialect Determination
886886

887887
When evaluation encounters a new schema resource (i.e. the lexical scope
888-
changes), the first task is to determine the dialect used by the schema. To do
889-
this, implementations MUST determine the dialect using the following prioritized
888+
changes), the first task is to determine the dialect used by the schema.
889+
Implementations MUST determine the dialect using the following prioritized
890890
steps.
891891

892892
1. The `$schema` keyword - Implementations MUST process the schema according to
@@ -898,7 +898,9 @@ steps.
898898
source and only applies to the document root.
899899
3. Parent dialect - An embedded schema resource which does not itself contain a
900900
`$schema` keyword MUST be processed using the same dialect as the schema
901-
which contains it.
901+
which contains it. If the schema is embedded in a non-schema document, the
902+
semantics for determining the dialect MAY be determined by any specification
903+
which applies to that document.
902904
4. User configuration - Implementations MAY provide means for the user to
903905
configure the dialect under which a schema should be processed.
904906

0 commit comments

Comments
 (0)