Skip to content

Commit b98d7ad

Browse files
committed
Rephrase recomended validation process for processing a schema document, as it is possible to identify embedded schema resources if you know it's a schema as opposed to just an instance.
1 parent ea80459 commit b98d7ad

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

jsonschema-core.xml

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1850,7 +1850,8 @@
18501850
</section>
18511851
<section title="Differing and Default Dialects">
18521852
<t>
1853-
In addition to the rules defining the use of the "$schema" keyword <target='The "$schema" Keyword' format="counter"></xref>,
1853+
In addition to the rules defining the use of the "$schema" keyword
1854+
<target='The "$schema" Keyword' format="counter"></xref>,
18541855
if multiple schema resources are present in a single document, then
18551856
schema resources which do not have a "$schema" keyword in their root
18561857
schema object MUST be processed as if "$schema" were present with the
@@ -1866,8 +1867,12 @@
18661867
Given a Compound Schema Document may have embedded resources which idenfiy as using different
18671868
dialects, it is NOT RECOMMENDED that these documents are validated by applying a meta-schema
18681869
to the Compound Schema Document as an instance. It is RECOMMENDED that an alternate
1869-
validation process be provided in order to validate Compound Schema Documents
1870-
(such as a different function).
1870+
validation process be provided in order to validate Schema Documents.
1871+
<cref>
1872+
If you know a schema is what's being validated, you can identify if the schemas
1873+
is a Compound Schema Document or not, by way of use of "$id", which identifies an
1874+
embedded resource when used not at the document's root.
1875+
</cref>
18711876
</t>
18721877
<t>
18731878
A Compound Schema Document in which all embedded resources idenfity as using the same

0 commit comments

Comments
 (0)