-
-
Notifications
You must be signed in to change notification settings - Fork 350
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.
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
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This issue is not ready for PR. It has some pretty significant implications that we need to discuss and decide on what action (if any) to take.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...ison (#1623)
What kind of change does this PR introduce?
Documentation / specification clarification
Issue & Discussion References
Summary
This PR updates the JSON Schema specification to clarify that when IRIs are used as identity tokens (not locators), implementations must use Simple String Comparison according to RFC 3987 section 5.3.1.
Full normalization or scheme-based comparison is not required in this context.
Example for clarity:
https://example.com/schema/αhttps://example.com/schema/αThese two IRIs are considered identical only if their strings match exactly, without performing additional normalization.
This fixes the inconsistency between the spec and RFC 3987 recommendations.
Does this PR introduce a breaking change?
No. This is a documentation/specification update and does not affect existing implementations.