Skip to content

Commit ec2f8a2

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 b30d80b commit ec2f8a2

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
@@ -1851,7 +1851,9 @@
18511851
<section title="References to Possible Non-Schemas">
18521852
<t>
18531853
Subschema objects (or booleans) are recognized by their use with known
1854-
applicator keywords. These keywords may be the standard applicators
1854+
applicator keywords, or with placeholder keywords such as
1855+
<xref target="defs">"$defs"</xref> that take one or more subschemas
1856+
as a value. These keywords may be "$defs" and the standard applicators
18551857
from this document, or extension keywords from a known vocabulary, or
18561858
implementation-specific custom keywords.
18571859
</t>
@@ -1973,7 +1975,7 @@
19731975
</section>
19741976
</section>
19751977

1976-
<section title='Schema Re-Use With "$defs"'>
1978+
<section title='Schema Re-Use With "$defs"' anchor="defs">
19771979
<t>
19781980
The "$defs" keyword provides a standardized location for schema
19791981
authors to inline re-usable JSON Schemas into a more general schema.

0 commit comments

Comments
 (0)