8000 Add warning about comparing DID URLs containing query parameters. by msporny · Pull Request #895 · w3c/did · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

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

Conversation

msporny
Copy link
Member
@msporny msporny commented May 31, 2025

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

@msporny msporny added the class 2 Changes that do not functionally affect interpretation of the document label May 31, 2025
@msporny msporny requested a review from ottomorac May 31, 2025 21:31
Comment on lines +1201 to +1205
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.
Copy link
Contributor

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:

Suggested change
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.

Copy link
Member

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...

Suggested change
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.

@w3cbot
Copy link
w3cbot commented Jun 19, 2025

This was discussed during the #did meeting on 19 June 2025.

View the transcript

Add 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.
… Just calling this out for review from folks


Copy link
Member
@TallTed TallTed left a 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
class 2 Changes that do not functionally affect interpretation of the document
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0