Skip to content

Commit 49e58a5

Browse files
authored
Merge pull request #1435 from json-schema-org/gregsdennis/locatable-iri-adjustments
Gregsdennis/locatable iri adjustments
2 parents 1db4168 + 9920bd8 commit 49e58a5

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

jsonschema-core.md

+8-7
Original file line numberDiff line numberDiff line change
@@ -1167,9 +1167,8 @@ provides the ability to validate recursive structures through self-reference.
11671167

11681168
The resolved IRI produced by these keywords is not necessarily a network
11691169
locator, only an identifier. A schema need not be downloadable from the address
1170-
if it is a network-addressable URL, and implementations SHOULD NOT assume they
1171-
should perform a network operation when they encounter a network-addressable
1172-
IRI.
1170+
if it is a network-addressable URL. Implementations which can access the network
1171+
SHOULD default to operating offline.
11731172

11741173
##### Direct References with `$ref` {#ref}
11751174

@@ -1299,17 +1298,19 @@ The use of IRIs to identify remote schemas does not necessarily mean anything is
12991298
downloaded, but instead JSON Schema implementations SHOULD understand ahead of
13001299
time which schemas they will be using, and the IRIs that identify them.
13011300

1302-
When schemas are downloaded, for example by a generic user-agent that does not
1303-
know until runtime which schemas to download, see [Usage for
1304-
Hypermedia](#hypermedia).
1305-
13061301
Implementations SHOULD be able to associate arbitrary IRIs with an arbitrary
13071302
schema and/or automatically associate a schema's `$id`-given IRI, depending on
13081303
the trust that the validator has in the schema. Such IRIs and schemas can be
13091304
supplied to an implementation prior to processing instances, or may be noted
13101305
within a schema document as it is processed, producing associations as shown in
13111306
{{idexamples}}.
13121307

1308+
Implementations MAY provide functionality to automatically fetch schemas based
1309+
on location semantics expressed by the IRI, however such functionality SHOULD be
1310+
disabled by default to prefer offline operation. When schemas are downloaded,
1311+
for example by a generic user-agent that does not know until runtime which
1312+
schemas to download, see {{hypermedia}}.
1313+
13131314
#### Detecting a Meta-Schema
13141315

13151316
Implementations MUST recognize a schema as a meta-schema if it is being examined

0 commit comments

Comments
 (0)