search

w3c-ccg / community

COMMUNITY: W3C Credentials Community Group Community Repo
https://w3c-ccg.github.io/community
Other
41 stars 6 forks source link

[PROPOSED WORK ITEM] did:tag Method Specification #216

Closed bobwyman closed 10 months ago

bobwyman commented 3 years ago

New Work Item Proposal

Define a new DID method, did:tag, derived from IETF tagURIs.

Include Link to Abstract or Draft

List Owners

Bob Wyman, @bobwyman

Work Item Questions

Answer the following questions in order to document how you are meeting the requirements for a new work item at the W3C Credentials Community Group. Please note if this work item supports the Silicon Valley Innovation program or another government or private sector project.

  1. Explain what you are trying to do using no jargon or acronyms.

I define a did:tag Decentralized Identifier (DID) method that provides a combination of capabilities and qualities not currently provided by any single previously defined DID method. Those capabilities of most interest include: DIDs which are unique over time, a DID resolution method which can be implemented with minimal software or system support, a DID resolution method which supports asynchronous use, and a means to specify an alternative DID resolution service.

  1. How is it done today, and what are the limits of the current practice?

A great many DID methods have been defined. However, most of have one or more of the following characteristics:

  1. What is new in your approach and why do you think it will be successful?

The proposed method is derived from the RFC4151 tagURI specification and thus incorporates a ``date'' component which eases the facility with which DID controllers are able to ensure that DIDs are unique over potentially long periods of time. Additionally, by supporting the minting of DIDs from tagURIs that use an email address as an authorityName, support is provided for asychronous resolution of DIDs. Given that the vast majority of online users have access to an email account, yet only a small subset of them are able or wiling to maintain a website, the support of asynchronous resolution via well established email protocols dramatically increases the universe of those who are able to usefully create and manage DIDs.

The AltResolution service provides a means by which a DID document may specify alternative means by which it might be resolved in the future. This mechanism is particularly useful when supporting asynchronous resolution.

I believe this specification will be successful since it provides a super-set of capabilities provided by the already well-received did:web method, but addresses some important issues not satisfactorily addressed by that method. Of particular interest, when comparing to did:web, is the fact that did:tag allows asynchronous resolution via widely used email protocols and thus overcomes the objection that did:web is too limited in the universe of users who can make use of it.

  1. How are you involving participants from multiple skill sets and global locations in this work item? (Skill sets: technical, design, product, marketing, anthropological, and UX. Global locations: the Americas, APAC, Europe, Middle East.)

By publishing this proposal to this community group, it is my hope to attract that participation of those who could either provide the diversity of viewpoint described in the question or who could provide suggestions on how to obtain such diverse feedback.

  1. What actions are you taking to make this work item accessible to a non-technical audience?

If CCG review indicates that doing so will have value, I will do my best to prepare easily understood documentation and explanations for the method as well as develop easy to use reference implementations.

Note: This is my first submission to the CCG. If there are any errors in format, content, or whatever, please do not hesitate to let me know.

bumblefudge commented 3 years ago

paging @jandrieu

vsnt commented 3 years ago

@bobwyman would you be able to attend the Nov 2 call to explain this work item to the community and answer questions?

Also, you will need to have a second co-lead to satisfy the work item requirements: https://w3c-ccg.github.io/workitem-process/#w3c-requirements

(You can ask for a second co-lead at the call. Glad to see you submitting a work item!)

bobwyman commented 3 years ago

I would be pleased to discuss the did:tag proposal during the Nov 2 call. I hope that others recognize that this proposal is still very raw. I expect that it benefit greatly from others' review and improvement suggestions.

I will ask for a second co-lead during the call.

bob wyman

bobwyman commented 3 years ago

Please note that I have updated the draft. Also, attached, you'll find the core slides I intend to present to the CCG tomorrow. I'm assuming that the presentation should be brief.

PresentationToCCG-20211102.odp

vsnt commented 3 years ago

Rescheduling this proposed work item for Nov 9.

mprorock commented 3 years ago

Per CCG Call as soon as we have a co-owner on this we can move it forward - great work!

mprorock commented 2 years ago

@bobwyman any updates on a co-owner?

kwlinson commented 1 year ago

Hi @bobwyman. Trying to organize this list. Let me know if you have a second sponsor and want to revisit in the new year. Thanks!

wip-abramson commented 10 months ago

What is the status of this work item. It has been pending close for a year now. Should it be closed?

bobwyman commented 10 months ago

I do not object to its being closed.

bob wyman

On Tue, Jan 16, 2024 at 2:44 PM Will Abramson @.***> wrote:

What is the status of this work item. It has been pending close for a year now. Should it be closed?

— Reply to this email directly, view it on GitHub https://github.com/w3c-ccg/community/issues/216#issuecomment-1894400969, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF3QS2XVOEXJ2UJ4AHCA4DTYO3KBBAVCNFSM5G3M63H2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBZGQ2DAMBZGY4Q . You are receiving this because you were mentioned.Message ID: @.***>