Skip to content

IRI normalization requirements #1638

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

IRI normalization requirements #1638

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 13 additions & 2 deletions specs/jsonschema-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -951,8 +951,19 @@ identified by
[absolute IRIs](https://www.rfc-editor.org/rfc/rfc3987.html#section-2.2)
(without fragments). These identifiers are used to create references between
schema resources. When comparing IRIs for the purposes of resource
identification, implementations SHOULD first follow the IRI normalization
procedures defined in [RFC 3987][rfc3987], section 5.3.
identification, implementations MUST apply the Syntax-Based IRI normalization
procedures defined in [RFC 3987][rfc3987], section 5.3.2.[^12] Implementations
MAY also apply Scheme-Based and Protocol-Based Normalization.[^13]

[^12]: [RFC 3987][rfc3987], section 5.1, requires that applications using IRIs
as non-locating, identifier-only tokens MUST use Simple String Comparison. JSON
Schema deviates from that requirement by specifying normalization requirements.

[^13]: We expect implementations to use whatever IRI libraries they have
available to them and therefore don't always have control over which
normalization rules are applied. Supporting Scheme-Based and Protocol-Based
Normalization is allowed to accommodate those situations, but it is discouraged
otherwise.

Several keywords can accept a relative IRI reference, or a value
used to construct a relative IRI reference. For these keywords, it is necessary
Expand Down
Loading