Skip to content

Commit 2040d74

Browse files
committed
Move and rename the "External References" section
Move it up under "$ref", and change the title to be about loading referenced schemas. Some further wording tweaks will be required to the contents, this just moves the paragraph without changing it.
1 parent 5947aaf commit 2040d74

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

jsonschema-core.xml

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -709,6 +709,25 @@
709709
Schemas SHOULD NOT make use of infinite recursive nesting like this; the behavior is
710710
undefined.
711711
</t>
712+
<section title="Loading a referenced schema">
713+
<t>
714+
To differentiate schemas between each other in a vast ecosystem, schemas are
715+
identified by URI. As specified above, this does not necessarily mean
716+
anything is downloaded, but instead JSON Schema implementations SHOULD
717+
already understand the schemas they will be using, including the URIs that
718+
identify them.
719+
</t>
720+
<t>
721+
Implementations SHOULD be able to associate arbitrary URIs with an arbitrary
722+
schema and/or automatically associate a schema's "$id"-given URI, depending
723+
on the trust that the validator has in the schema.
724+
</t>
725+
<t>
726+
A schema MAY (and likely will) have multiple URIs, but there is no way for a
727+
URI to identify more than one schema. When multiple schemas try to identify
728+
with the same URI, validators SHOULD raise an error condition.
729+
</t>
730+
</section>
712731
</section>
713732

714733
<section title="Dereferencing">
@@ -758,25 +777,6 @@
758777
resolve the fragment against the base URI.
759778
</t>
760779
</section>
761-
<section title="External References">
762-
<t>
763-
To differentiate schemas between each other in a vast ecosystem, schemas are
764-
identified by URI. As specified above, this does not necessarily mean
765-
anything is downloaded, but instead JSON Schema implementations SHOULD
766-
already understand the schemas they will be using, including the URIs that
767-
identify them.
768-
</t>
769-
<t>
770-
Implementations SHOULD be able to associate arbitrary URIs with an arbitrary
771-
schema and/or automatically associate a schema's "$id"-given URI, depending
772-
on the trust that the validator has in the schema.
773-
</t>
774-
<t>
775-
A schema MAY (and likely will) have multiple URIs, but there is no way for a
776-
URI to identify more than one schema. When multiple schemas try to identify
777-
with the same URI, validators SHOULD raise an error condition.
778-
</t>
779-
</section>
780780
</section>
781781
</section>
782782

0 commit comments

Comments
 (0)