Skip to content

Clarify IRI comparison for identity tokens (#1623) #1625

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

Closed
wants to merge 1 commit into from
Closed

Clarify IRI comparison for identity tokens (#1623) #1625

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: 12 additions & 3 deletions specs/jsonschema-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -978,9 +978,18 @@ To differentiate between schemas in a vast ecosystem, schema resources are
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.
schema resources. ### IRI comparison for identity tokens

When IRIs are used as **identity tokens** (not locators), implementations **MUST use Simple String Comparison** as defined in RFC 3987 section 5.3.1.
Normalization or scheme-based comparison is **not required** in this context.

Example:

- `https://example.com/schema/α`
- `https://example.com/schema/α`

These two IRIs are considered identical only if their strings match exactly, without performing additional normalization.


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