Skip to content

Commit 8ca3eca

Browse files
committed
More detail on associating URIs and schemas
Note the case of identifying schemas during processing, as shown in the earlier example. This replaces the explicitly called-out concept of "Internal Referencing" which will be removed.
1 parent 2040d74 commit 8ca3eca

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

jsonschema-core.xml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -720,7 +720,10 @@
720720
<t>
721721
Implementations SHOULD be able to associate arbitrary URIs with an arbitrary
722722
schema and/or automatically associate a schema's "$id"-given URI, depending
723-
on the trust that the validator has in the schema.
723+
on the trust that the validator has in the schema. Such URIs and schemas
724+
can be supplied to an implementation prior to processing instances, or may
725+
be noted within a schema document as it is processed, producing associations
726+
as shown in section <xref target="idExamples" format="counter"></xref>.
724727
</t>
725728
<t>
726729
A schema MAY (and likely will) have multiple URIs, but there is no way for a

0 commit comments

Comments
 (0)