-
Notifications
You must be signed in to change notification settings - Fork 14
Summary of actions on a number of enhancements #121
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
Comments
+1 to the actions above. |
This was discussed during the #did meeting on 07 February 2025. |
Thanks for putting this together @peacekeeper, the proposed actions look great. The only issue I was unsure about was #40, I thought @msporny was advocating for it to be in the did resolution spec. But since @msporny has +1's to moving this to DID extensions then that clears things up for me. |
This was discussed during the #did meeting on 13 February 2025. View the transcriptw3c/did-resolution#121markus_sabadello: This is a meta issue, summarize conclusions -- enhancements, links to seven other issues, for all of them, discussion around DID Resolution specification itself -- new parameters, resolution options, proposed enhancements, trying to summarize that here. That would take care of 7 open issues, specific enhancements, specific topics have to go somewhere, but an attempt to close discussion around some of these topics we've discussed in last few meetings. markus_sabadello: Please take a look, we can create PRs or move things to extensions. Wip: I appreciate you putting this together, get issues closed; can we just close issue when all actions have been done? <Wip> w3c/did-resolution#40 Wip: Manu, you said these actions are fine, my memory of issue 40 is that you thought that should go in resolution. <ivan> +1 to joe! manu: I'm non-blocking on that... I have a preference, but not blocking preference. Fine to do whatever the group wants. JoeAndrieu: We need to be specific about DID Core vs. DID Resolution (we need to not use those interchangeably) -- we're talking about DID Resolution. |
I just updated the table to reflect this. |
Status update here is that the only enhancement that's still open is this:
After this PR #122 is merged, I think this issue here can also be closed. |
Marking as pending-close, since all proposed enhancements in the table have been addressed. |
This issue summarizes actions to be taken on a number of proposed enhancement issues that can be supported via new DID resolution options or parameters:
followServiceDid
verificationRelationship
serviceType
transformKeys
expandRelativeUrls
expandReferencedVerificationMethods
returnDeactivatedDidDocument
Feel free to comment either here or in the issues about the specific enhancements.
The text was updated successfully, but these errors were encountered: