Skip to content

Commit 6d30f41

Browse files
committed
More guidance on initial base URI
Nudge readers a bit more clearly to consider things like 'file://' URLs and not just network URLs when constructing a location-based base URI. Also refer directly to the rules for application-specific default URIs.
1 parent 7401514 commit 6d30f41

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

jsonschema-core.xml

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -848,7 +848,8 @@
848848
<section title="Base URI and Dereferencing">
849849
<t>
850850
To differentiate between schemas in a vast ecosystem, schemas are
851-
identified by <xref target="RFC3986">URI</xref>, and can embed references to other schemas by specifying their URI.
851+
identified by <xref target="RFC3986">URI</xref>, and can embed references
852+
to other schemas by specifying their URI.
852853
</t>
853854

854855
<section title="Initial Base URI">
@@ -858,7 +859,14 @@
858859
</t>
859860
<t>
860861
Informatively, the initial base URI of a schema is the URI at which it was
861-
found, or a suitable substitute URI if none is known.
862+
found, whether that was a network location, a local filesystem, or any other
863+
situation identifiable by a URI of any known scheme.
864+
</t>
865+
<t>
866+
If no source is known, or no URI scheme is known for the source, a suitable
867+
implementation-specific default URI MAY be used as described in
868+
<xref target="RFC3986"> RFC 3986 Section 5.1.4</xref>. It is RECOMMENDED
869+
that implementations document any default base URI that they assume.
862870
</t>
863871
</section>
864872

0 commit comments

Comments
 (0)