Skip to content

Issues: w3c/did-resolution

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

46 Open 38 Closed
46 Open 38 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Summary of actions on a number of enhancements
#121 opened Feb 6, 2025 by peacekeeper
2
Is the openAPI spec (eventually) normative or informative?
#118 opened Jan 31, 2025 by iherman
2
https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json may not be correct
#117 opened Jan 31, 2025 by iherman
4
Model accept as the HTTP accept header
#116 opened Jan 31, 2025 by iherman
Is it graph merge or graph equivalence?
#115 opened Jan 31, 2025 by iherman
3
Can we simplify the API to remove resolveRespresentation?
#114 opened Jan 29, 2025 by wip-abramson
3
Language clarification "A DID document is a representation of information describing a DID subject."
#113 opened Jan 29, 2025 by wip-abramson
4
Various issues with links to DID core editorial Editors should update the spec then close
#112 opened Jan 29, 2025 by wip-abramson
Explain that the HTTP(S) binding can also be used locally editorial Editors should update the spec then close
#111 opened Jan 22, 2025 by peacekeeper
Define DID document metadata property for providing proofs of correctness enhancement New feature or request
#110 opened Jan 17, 2025 by wip-abramson
Use made-up example URLs for resolver endpoints editorial Editors should update the spec then close good first issue Good for newcomers ready-for-pr Issue is ready for a PR
#109 opened Jan 10, 2025 by peacekeeper
@swcurran
1
DID service parameter does not account for cases where id of service is a full IRI external to the DID document bug Something isn't working
#97 opened Nov 19, 2024 by trwnh
2
Minimizing the extent of profiling of requestors privacy Issue related to privacy.
#95 opened Nov 14, 2024 by peacekeeper
Should the HTTPS binding be mandatory?
#93 opened Oct 25, 2024 by peacekeeper
1
DID Resolution Test Suite
#92 opened Oct 4, 2024 by wip-abramson
4
Separate "Security and Privacy Considerations" editorial Editors should update the spec then close good first issue Good for newcomers ready-for-pr Issue is ready for a PR
#91 opened Sep 24, 2024 by peacekeeper
@jandrieu
1
More advanced DID URL dereferencing for verificationMethods? enhancement New feature or request
#90 opened Sep 13, 2024 by wip-abramson
@wip-abramson
6
Consider use of "Problem Details" in case of errors enhancement New feature or request
#87 opened Aug 29, 2024 by peacekeeper
@msporny
3
Request service by type enhancement New feature or request ready-for-pr Issue is ready for a PR
#85 opened Aug 21, 2024 by philarcher
@peacekeeper
5
Scope of sub-topics: trust in did resolution / authentication / encryption / selective disclosure
#79 opened Jul 25, 2024 by ChristopherA
1
DID Resolution: Proof of inclusion of DID document in state of Verifiable Data Registry
#102 opened Jun 23, 2023 by Therecanbeonlyone1969
11
DID Resolution Result for DID URL Dereferencing enhancement New feature or request pending-close Issue will be closed shortly if no objections
#69 opened Dec 30, 2021 by clehner
4
versionId/versionTime are not defined for DID resolution enhancement New feature or request
#66 opened Jul 15, 2021 by letmaik
7
Service Endpoint Construction inconsistency bug Something isn't working ready-for-pr Issue is ready for a PR
#61 opened Feb 4, 2021 by clehner
@peacekeeper
6
Disallow JSON-LD remote context retrieval enhancement New feature or request ready-for-pr Issue is ready for a PR
#53 opened Feb 3, 2020 by peacekeeper
2
ProTip! Follow long discussions with comments:>50.