Skip to content

Commit ced9c21

Browse files
committed
clarify the relationship between resources and docs; clarify that external docs should specify their usage of json schema
1 parent 775b578 commit ced9c21

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

specs/jsonschema-core.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -252,13 +252,13 @@ is identical to the primary resource. This can occur with the empty fragment, or
252252
when one schema resource is embedded in another. Any such IRIs with fragments
253253
are considered to be non-canonical.
254254

255-
The root schema is the schema that comprises the entire JSON document in
256-
question. The root schema is always a schema resource, where the IRI is
257-
determined as described in {{initial-base}}.[^1]
255+
A root schema, which may comprise the entire JSON document, is the top-level
256+
schema that is identified by the absolute IRI. The root schema is always a
257+
schema resource, where the IRI is determined as described in {{initial-base}}.
258258

259-
[^1]: Note that documents that embed schemas in another format will not have a
260-
root schema resource in this sense. Exactly how such usages fit with the JSON
261-
Schema document and resource concepts will be clarified in a future draft.
259+
Documents formats which embed JSON Schemas within them will not necessarily have
260+
a single root schema in this sense. How root schemas are identified within such
261+
documents SHOULD be defined by the specifications which govern them.
262262

263263
Some keywords take schemas themselves, allowing JSON Schemas to be nested:
264264

0 commit comments

Comments
 (0)