Skip to content

Commit c44829d

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 7beb355 commit c44829d

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
@@ -1865,7 +1865,8 @@
18651865
</section>
18661866
<section title="Differing and Default Dialects">
18671867
<t>
1868-
In addition to the rules defining the use of the "$schema" keyword <target='The "$schema" Keyword' format="counter"></xref>,
1868+
In addition to the rules defining the use of the "$schema" keyword
1869+
<target='The "$schema" Keyword' format="counter"></xref>,
18691870
if multiple schema resources are present in a single document, then
18701871
schema resources which do not have a "$schema" keyword in their root
18711872
schema object MUST be processed as if "$schema" were present with the
@@ -1881,8 +1882,12 @@
18811882
Given a Compound Schema Document may have embedded resources which idenfiy as using different
18821883
dialects, it is NOT RECOMMENDED that these documents are validated by applying a meta-schema
18831884
to the Compound Schema Document as an instance. It is RECOMMENDED that an alternate
1884-
validation process be provided in order to validate Compound Schema Documents
1885-
(such as a different function).
1885+
validation process be provided in order to validate Schema Documents.
1886+
<cref>
1887+
If you know a schema is what's being validated, you can identify if the schemas
1888+
is a Compound Schema Document or not, by way of use of "$id", which identifies an
1889+
embedded resource when used not at the document's root.
1890+
</cref>
18861891
</t>
18871892
<t>
18881893
A Compound Schema Document in which all embedded resources idenfity as using the same

0 commit comments

Comments
 (0)