Skip to content

docs and resources and external docs #1599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 16, 2025
Merged

docs and resources and external docs #1599

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ced9c21
clarify the relationship between resources and docs; clarify that ext…
gregsdennis Apr 26, 2025
3445c0d
Update specs/jsonschema-core.md
gregsdennis Apr 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions specs/jsonschema-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,13 +252,13 @@ is identical to the primary resource. This can occur with the empty fragment, or
when one schema resource is embedded in another. Any such IRIs with fragments
are considered to be non-canonical.

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

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

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

Expand Down