Skip to content

Commit 03d78a7

Browse files
committed
use more common language; be more explicit about retrieval source
1 parent 3364674 commit 03d78a7

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

jsonschema-core.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -884,17 +884,18 @@ meta-schema features emphasizes flexibility over simplicity.
884884

885885
#### Dialect Determination
886886

887-
When the schema evaluation process begins, the first task is to determine the
888-
dialect used by the schema. To do this, implementations MUST determine the
889-
dialect using the following prioritized steps.
887+
When the 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
890+
steps.
890891

891892
1. The `$schema` keyword - Implementations MUST process the schema according to
892893
the dialect it declares.
893894
2. `application/schema+json` media type with a `schema` parameter -
894895
Implementations which support media type parameter inputs MUST process the
895896
schema according to the dialect the parameter declares. A media type will
896-
generally only be available if the schema has been retrieved and only applies
897-
to the document root.
897+
generally only be available if the schema has been retrieved from an external
898+
source and only applies to the document root.
898899
3. Parent dialect - An embedded schema resource which does not itself contain a
899900
`$schema` keyword MUST be processed using the same dialect as the schema
900901
which contains it.

0 commit comments

Comments
 (0)