@@ -1167,9 +1167,8 @@ provides the ability to validate recursive structures through self-reference.
1167
1167
1168
1168
The resolved IRI produced by these keywords is not necessarily a network
1169
1169
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.
1173
1172
1174
1173
##### Direct References with ` $ref ` {#ref}
1175
1174
@@ -1299,17 +1298,19 @@ The use of IRIs to identify remote schemas does not necessarily mean anything is
1299
1298
downloaded, but instead JSON Schema implementations SHOULD understand ahead of
1300
1299
time which schemas they will be using, and the IRIs that identify them.
1301
1300
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
-
1306
1301
Implementations SHOULD be able to associate arbitrary IRIs with an arbitrary
1307
1302
schema and/or automatically associate a schema's ` $id ` -given IRI, depending on
1308
1303
the trust that the validator has in the schema. Such IRIs and schemas can be
1309
1304
supplied to an implementation prior to processing instances, or may be noted
1310
1305
within a schema document as it is processed, producing associations as shown in
1311
1306
{{idexamples}}.
1312
1307
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
+
1313
1314
#### Detecting a Meta-Schema
1314
1315
1315
1316
Implementations MUST recognize a schema as a meta-schema if it is being examined
0 commit comments