@@ -966,13 +966,15 @@ just a fragment identifier not an IRI reference. To reference the "foo"
966966` $anchor ` from the same schema resource, you would use the fragment-only IRI
967967` #foo ` . See below for full examples.
968968
969- ` $dynamicAnchor ` defines a different kind of identifier that only has meaning
970- when used as a value for ` $dynamicRef ` . It's not a fragment identifier that can
971- be used in an IRI. ` $dynamicRef ` uses a syntax similar to a fragment-only IRI,
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.
969+ ` $dynamicAnchor ` defines a different kind of fragment identifier that only has
970+ meaning when used with ` $dynamicRef ` . It's not a normal fragment identifier and
971+ therefore can't be used anywhere other than ` $dynamicRef ` . Normal [ fragment
972+ identifiers] ( https://www.rfc-editor.org/rfc/rfc3986#section-3.5 ) identify the
973+ secondary resource (the subschema) while the rest of the IRI identifies the
974+ primary resource (the schema resource). The fragment identifiers defined by
975+ ` $dynamicAnchor ` are not normal fragment identifies because they identify both
976+ the primary resource and the secondary resource. See {{dynamic-ref}} for
977+ details.
976978
977979If present, the value of these keywords MUST be a string and MUST conform to the
978980plain name fragment identifier syntax defined in {{fragments}}.
0 commit comments