Skip to content

Commit 01a56ea

Browse files
committed
Drop the initial resolve step for dynamic references
1 parent 38fccc0 commit 01a56ea

File tree

1 file changed

+7
-14
lines changed

1 file changed

+7
-14
lines changed

jsonschema-core.xml

+7-14
Original file line numberDiff line numberDiff line change
@@ -1510,22 +1510,15 @@
15101510
<t>
15111511
Together with "$dynamicAnchor", "$dynamicRef" implements a cooperative
15121512
extension mechanism that is primarily useful with recursive schemas
1513-
(schemas that reference themselves). The extension point is defined with
1514-
"$dynamicAnchor" and only exhibits runtime dynamic behavior when referenced
1515-
with "$dynamicRef".
1513+
(schemas that reference themselves). The extension point is defined
1514+
with "$dynamicAnchor", and only exhibits runtime dynamic behavior when
1515+
referenced with "$dynamicRef".
15161516
</t>
15171517
<t>
1518-
The value of the "$dynamicRef" property MUST be a string which is a
1519-
IRI-Reference that contains a valid <xref target="anchor">plain name
1520-
fragment</xref>. Resolved against the current IRI base, it indicates
1521-
the schema resource used as the starting point for runtime resolution.
1522-
This initial resolution is safe to perform on schema load.
1523-
</t>
1524-
<t>
1525-
The schema to apply is the outermost schema resource in the
1526-
<xref target="scopes">dynamic scope</xref> that defines a
1527-
"$dynamicAnchor" that matches the plain name fragment in the initially
1528-
resolved IRI.
1518+
The value of the "$dynamicRef" property MUST be a valid
1519+
<xref target="anchor">plain name fragment</xref>. The schema to apply is
1520+
the outermost schema resource in the <xref target="scopes">dynamic scope</xref>
1521+
that defines a "$dynamicAnchor" matching the value of this keyword.
15291522
</t>
15301523
<t>
15311524
For a full example using these keyword, see appendix

0 commit comments

Comments
 (0)