@@ -963,15 +963,16 @@ fragments as an alternative to JSON Pointers.[^4] See {{fragments}}.
963963
964964[ ^ 4 ] : Note that the anchor string does not include the "#" character, as it is
965965just a fragment identifier not an IRI reference. To reference the "foo"
966- ` $anchor ` from the same Schema Resource , you would use the fragment-only IRI
966+ ` $anchor ` from the same schema resource , you would use the fragment-only IRI
967967` #foo ` . See below for full examples.
968968
969969` $dynamicAnchor ` defines a different kind of identifier that only has meaning
970970when used as a value for ` $dynamicRef ` . It's not a fragment identifier that can
971971be used in an IRI. ` $dynamicRef ` uses a syntax similar to a fragment-only IRI,
972- but the semantics are different. Unlike IRIs, the fragment identifies the
973- primary resource (the schema resource) in addition to the secondary resource
974- (the subschema within that schema resource). See {{dynamic-ref}} for details.
972+ but the semantics are different. Unlike fragments in IRIs, the fragment in
973+ ` $dynamicRef ` identifiers identifies the primary resource (the schema resource)
974+ in addition to the secondary resource (the subschema within that schema
975+ resource). See {{dynamic-ref}} for details.
975976
976977If present, the value of these keywords MUST be a string and MUST conform to the
977978plain name fragment identifier syntax defined in {{fragments}}.
@@ -993,8 +994,7 @@ applicators, applying the referenced schema to the instance.
993994##### Direct References with ` $ref ` {#ref}
994995
995996The ` $ref ` keyword is an applicator that is used to reference a statically
996- identified schema. Its results are the results of evaluating the referenced
997- schema.[ ^ 5 ]
997+ identified schema. Its results are the results of the referenced schema.[ ^ 5 ]
998998
999999[ ^ 5 ] : Note that this definition of how the results are determined means that
10001000other keywords can appear alongside of ` $ref ` in the same schema object.
@@ -1013,9 +1013,9 @@ default to operating offline.
10131013
10141014The ` $dynamicRef ` keyword is an applicator that is used when the referencing
10151015schema might need to override where a reference in the referenced schema will
1016- resolve. This is useful for authoring a recursive schema that can be extended or
1017- a generic schema such as a list whose items are defined by the referencing
1018- schema.
1016+ resolve. This is useful for cases such as authoring a recursive schema that can
1017+ be extended or a generic schema such as a list whose items are defined by the
1018+ referencing schema.
10191019
10201020The value of the ` $dynamicRef ` property MUST be formatted as a valid
10211021[ fragment-only IRI] ( #fragments ) .[ ^ 3 ]
@@ -1206,10 +1206,11 @@ each resource is a separate document connected with [schema
12061206references] ( #referenced ) , or is structured as a single document with one or more
12071207schema resources embedded as subschemas.
12081208
1209- Since IRIs with JSON Pointer fragments relative to the parent schema
1210- resource's IRI cease to be valid when the embedded schema is moved to a separate
1211- document and referenced, applications and schemas SHOULD NOT use such IRIs to
1212- identify embedded schema resources or locations within them.
1209+ Since IRIs with JSON Pointer fragments are relative to the parent schema
1210+ resource's IRI, they cease to be valid when the embedded schema is moved to a
1211+ separate document and referenced. Because of this, applications and schemas
1212+ SHOULD NOT use such IRIs to identify embedded schema resources or locations
1213+ within them.
12131214
12141215Consider the following schema document that contains another schema resource
12151216embedded within it:
0 commit comments