Skip to content
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

Clarify that fragment identifier parsing algorithm is specific to HTTPS URLs? #133

Open
msporny opened this issue Dec 12, 2024 · 1 comment
Assignees
Labels
editorial This item is editorial in nature. ready for pr This issue is ready to have a pull request created for it.

Comments

@msporny
Copy link
Member

msporny commented Dec 12, 2024

From issue #126 (comment), @iherman noted that it would be good for us to

  • add a sentence to the new section noting that the referred algorithm (retrieve verification method) is one of the possible ways to get to the controller document, and that application areas and/or implementations may decide to choose a different approach
  • add a similar note to the algorithmic part emphasizing that manipulating the URL and its fragment part is an approach that VC-s and DID-s may use? usually use? (I do not know which), but this is not the only way to do this.
@msporny msporny added ready for pr This issue is ready to have a pull request created for it. editorial This item is editorial in nature. labels Dec 12, 2024
@msporny msporny self-assigned this Dec 12, 2024
@TallTed
Copy link
Member

TallTed commented Dec 13, 2024

for the first bullet...
s/ways to get to the controller document/ways to get to the controlled identifier document/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial This item is editorial in nature. ready for pr This issue is ready to have a pull request created for it.
Projects
None yet
Development

No branches or pull requests

2 participants