Skip to content

Commit a9d154c

Browse files
committed
Clarify the nature of schema placeholder keywords
Acknowledge that "$defs" and placeholders like it also indicate that their values are schemas, which is relevant to whether they can be detected as a proper "$ref" target or place where "$id" may appear. This ensures that similar extension keywords are understood to have the same concerns as extension applicator keywords.
1 parent c5a6078 commit a9d154c

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

jsonschema-core.xml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1789,7 +1789,9 @@
17891789
<section title="References to Possible Non-Schemas">
17901790
<t>
17911791
Subschema objects (or booleans) are recognized by their use with known
1792-
applicator keywords. These keywords may be the standard applicators
1792+
applicator keywords, or with placeholder keywords such as
1793+
<xref target="defs">"$defs"</xref> that take one or more subschemas
1794+
as a value. These keywords may be "$defs" and the standard applicators
17931795
from this document, or extension keywords from a known vocabulary, or
17941796
implementation-specific custom keywords.
17951797
</t>
@@ -1911,7 +1913,7 @@
19111913
</section>
19121914
</section>
19131915

1914-
<section title='Schema Re-Use With "$defs"'>
1916+
<section title='Schema Re-Use With "$defs"' anchor="defs">
19151917
<t>
19161918
The "$defs" keyword provides a standardized location for schema
19171919
authors to inline re-usable JSON Schemas into a more general schema.

0 commit comments

Comments
 (0)