-
Notifications
You must be signed in to change notification settings - Fork 100
Add warning about comparing DID URLs containing query parameters. #895
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
base: main
Are you sure you want to change the base?
Conversation
Implementers are urged to avoid using [=DID URLs=] that contain more than a | ||
single query parameter when comparing [=DID URLs=] for equivalence. There are | ||
no normalization rules defined for query parameters in this specification and | ||
any query parameter normalization rules defined at the DID Method specification | ||
or application layer are not universally recognized rules. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could see another specification handling this for some ecosystem/use case in the future, so I have a slight suggestion. I also had some trouble following what the advice was here, so let me know if the additional rewording helps:
Implementers are urged to avoid using [=DID URLs=] that contain more than a | |
single query parameter when comparing [=DID URLs=] for equivalence. There are | |
no normalization rules defined for query parameters in this specification and | |
any query parameter normalization rules defined at the DID Method specification | |
or application layer are not universally recognized rules. | |
Implementers are urged to avoid comparing [=DID URLs=] with more than | |
one query parameter for equivalence without a specification specifically | |
designed for that purpose. There are no normalization rules defined for | |
query parameters in this specification and any query parameter normalization | |
rules defined at the DID Method specification or application layer are not | |
universally recognized rules. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A light tweak to @dlongley's suggestion...
Implementers are urged to avoid using [=DID URLs=] that contain more than a | |
single query parameter when comparing [=DID URLs=] for equivalence. There are | |
no normalization rules defined for query parameters in this specification and | |
any query parameter normalization rules defined at the DID Method specification | |
or application layer are not universally recognized rules. | |
Implementers are urged to avoid comparing [=DID URLs=] for equivalence when | |
they have more than one query parameter without a specification specifically | |
designed for that purpose. This specification defines no normalization rules | |
for query parameters, and any query parameter normalization rules defined at | |
the DID Method specification or application layer are not universally | |
recognized rules. |
This was discussed during the #did meeting on 19 June 2025. View the transcriptAdd warning about comparing DID URLs containing query parameters. #895<ottomorac> w3c/did#895 ottomorac: This attempts to clarify that the DID core spec defines no normalization rules for query parameters and warning when comparing DID URLs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved given that #895 (comment) is applied
This PR is an attempt to address issue #865 by adding a warning about comparing DID URLs that contain more than a single query parameter.
Preview | Diff