-
Notifications
You must be signed in to change notification settings - Fork 62
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] Remove "Decentralized Identifier (DID) Method Specifications" from deliverables. #431
Comments
[[ We object to standardizing any specific DID methods at W3C, especially In addition, since did methods by their nature deal with key material and |
From @jandrieu Our second technical objection is more prosaic: there are no DID Methods |
From @rxgrant Any bugs found in a then-current "Decentralized Identifiers (DIDs) |
* 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 |
From @OR13:
[[
Remove "Decentralized Identifier (DID) Method Specifications" from
deliverables.
In addition to reasoning for #427 :
Previous formal objections focused on several dimensions of the DID
specification including determining if “sufficient decentralization was
achieved” and “measuring the trade offs and cost for achieving
decentralization”... This included commentary on Proof of Work and Proof
of Stake, and their impact on the environment, securities laws, and
international trade related topics, including sanctions and political
acceptability.
Based on the discussions observed in community groups related to the
specification, and the dialog following the previous formal objections, it
is our assessment that W3C is not the correct venue to address these
political challenges, or the technologies underlying them.
We believe IETF might be a better venue to address some of these concerns,
evidenced by the recent interest in Detecting Unwanted Location Trackers
(https://datatracker.ietf.org/wg/dult/about/).
]]
From 2023 AC Review
The text was updated successfully, but these errors were encountered: