-
Notifications
You must be signed in to change notification settings - Fork 63
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
[wg/did] reword charter to not assume a specific browser development process #447
Comments
This is a duplicate of #436. |
Oh, except it's targeted at the DID charter instead of the charter template. Don't mind me. |
pchampin
added a commit
that referenced
this issue
Nov 30, 2023
* address #447 * remove DID methods, and make DID resolution a REC track deliverable addresses - #427 (DID resolution on REC track) - #431 (remove DID methods) - #434 (now moot, as DID methods have been removed) * add specific exit criteria discussed during TPAC * Update 2023/did-wg.html Co-authored-by: Ivan Herman <ivan@w3.org> * Update 2023/did-wg.html Co-authored-by: Ivan Herman <ivan@w3.org> * rephrase the requirement for two independant DID methods * typo * Change DID Resolution success criteria removed the "dummy DID method" and the "provide evidence of existing DID methods" instead, the "evidence of existing DID methods" is deferred to DID Resolver implementations. Interoperability will be demonstrated by ensuring that resolvers support DID methods in common. * Brent Zundel is now an IE --------- Co-authored-by: Ivan Herman <ivan@w3.org>
The charter was announced |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[[
The following text is problematic, as only some implementers have an "intent to X" process:
To resolve this concern, please reword that sentence to not assume a specific browser development process.
]]
From 2023 AC Review (member-only)
The text was updated successfully, but these errors were encountered: