search

w3c-ccg / community

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

Collaborative, open specification of the did:tz method #202

Closed bumblefudge closed 2 years ago

bumblefudge commented 2 years ago

New Work Item Proposal

We would like to open up the design process for did:tz to a more open and consultative/deliberative conversation in the open.

Include Link to Abstract or Draft

Draft spec here (ReSpec)

List Owners

Wayne Chang, Spruce, @wyc Johannes Ebert, Gravity.earth, @GravityID

Work Item Questions

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

We would like to open up the design process for did:tz to a more open and consultative/deliberative conversation in the open to better serve the Tezos community.

did:tz is a multi-modal DID method design with many offchain, on-chain, and side-chain/L2 use cases in mind. A valid Tezos address (controlled by a private key from any of 3 supported curves) can control an "implicit" DID document (generatively created from the address like a did:key), an "onchain" DID document (published via smart contract on any Tezos ledger), or have "patches" applied to it that are published and governed by a closed network or authority (including, for example, a sidetree network). In particular, this third option has not been specified in any detail, and we would be particularly curious to hear from implementers of such systems before further specifying it.

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

There are already users of the first two kinds of did:tz mentioned above, and work has begun on at least one system that would utilize the third. For this reason, design and specification are timely.

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

We think that a method that specifies the three "layers" of resolution in common and outlines upgrade paths for moving from the simpler to the more complex forms of DID without rotation or additional set-up will, in time, simplify and strengthen the options available to relying systems.

  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.)

We are hoping that by opening up our DID method design process to be more open, we will hear from business and technical voices far and wide, particularly since the Tezos ecosystem is fairly international and open-source in nature. If many weeks pass without input, we may do active outreach via the Tezos community and DIF.

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

We have tried to craft a did method specification draft that is accessible and welcome PRs if it can be made more accessible.

bumblefudge commented 2 years ago

@mprorock should probably be tagged for review instead of kim!

vsnt commented 2 years ago

I'd like to discuss this item on the 7/27 call.

vsnt commented 2 years ago

Began discussion on 7/27, needed more time, so chairs will schedule for a future meeting agenda.

vsnt commented 2 years ago

I have added this work item to the 9/21 CCG call agenda to review+discuss with the community. Would the owners please attend this meeting. Thank you. https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0074.html

bumblefudge commented 2 years ago

Discussed on the call that CCG is leaning towards not working on DID methods in CCG that rely on one-vendor or one-community VDRs (particularly single public blockchains with substantial financial resources for blockchain development).

If the CCG decides not to accept the work item, the co-sponsors (Spruce Systems, NYC, and Gravity.Earth, Paris/Nairobi) will continue to work outside of CCG and interested parties are encouraged to email them if interested in participating. Interested parties can also reach out in the meantime if the process takes a few weeks either way.

vsnt commented 2 years ago

Per discussion at the 9/21 CCG call, this work item has entered the 7 day review period. If anyone has concerns about this becoming a work item, it should be raised prior to EOD Sept 29, 2021. If no concerns are raised, this will move to a work item at that time.

vsnt commented 2 years ago

@wyc what is Francois' github?

vsnt commented 2 years ago

Repo is here: https://github.com/w3c-ccg/did-tz Please add Francois github, as I do not have it.

TallTed commented 2 years ago

It appears likely that @frague59 is the correct Francois Guerin's Github handle. Hopefully this tag will get confirmation or denial. :-)

bumblefudge commented 2 years ago

I think we could switch the tag to @GravityID , as I'm not sure Francois is still the right person at https://gravity.earth . His old github handle was specifically for his Gravity.earth work.

vsnt commented 2 years ago

All, I tried adding @GravityID, but it didn't accept into the repo settings. Would the work item owners please take this and address it here: https://github.com/w3c-ccg/did-tz/issues/1/

Thanks, I am closing this issue.

frague59 commented 2 years ago

Even if my name has been cited, I'm not the right guy, sorry...

GravityID commented 2 years ago

Hello. I did not receive any invit on my side.

Le jeu. 13 janv. 2022 à 18:02, vsnt @.***> a écrit :

All, I tried adding @GravityID https://github.com/GravityID, but it didn't accept into the repo settings. Would the work item owners please take this and address it here: w3c-ccg/did-tz#1 https://github.com/w3c-ccg/did-tz/issues/1

Thanks, I am closing this issue.

— Reply to this email directly, view it on GitHub https://github.com/w3c-ccg/community/issues/202#issuecomment-1012329479, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARWCDCXKRSBXL254OWPJJ7LUV4ATLANCNFSM5AP7AUYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

vsnt commented 2 years ago

Hello Gravity, what's your github id, or can you login to github (click the link "view it on GitHub) and reply directly with it directly in the thread. Thanks!

On Thu, Jan 13, 2022 at 11:01 AM Gravity @.***> wrote:

Hello. I did not receive any invit on my side.

Le jeu. 13 janv. 2022 à 18:02, vsnt @.***> a écrit :

All, I tried adding @GravityID https://github.com/GravityID, but it didn't accept into the repo settings. Would the work item owners please take this and address it here: w3c-ccg/did-tz#1 https://github.com/w3c-ccg/did-tz/issues/1

Thanks, I am closing this issue.

— Reply to this email directly, view it on GitHub <https://github.com/w3c-ccg/community/issues/202#issuecomment-1012329479 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ARWCDCXKRSBXL254OWPJJ7LUV4ATLANCNFSM5AP7AUYQ

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/w3c-ccg/community/issues/202#issuecomment-1012421820, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADBNKK3VY2HJVXZTMPNHY73UV4OP3ANCNFSM5AP7AUYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you modified the open/close state.Message ID: @.***>

-- Heather Vescent http://www.heathervescent.com/ President, The Purple Tornado, Inc https://thepurpletornado.com/ ~ The Future in Present Tense ~ Co-Chair, Credentials Community Group @W3C https://www.w3.org/community/credentials/ Author, The Secret of Spies https://amzn.to/2GfJpXH Author, The Cyber Attack Survival Manual https://www.amazon.com/Cyber-Attack-Survival-Manual-Apocalypse/dp/1681886545/ Author, A Comprehensive Guide to Self Sovereign Identity https://ssiscoop.com/

@heathervescent https://twitter.com/heathervescent | Film Futures https://vimeo.com/heathervescent | Medium @.***/> | LinkedIn https://www.linkedin.com/in/heathervescent/ | Future of Security Updates https://app.convertkit.com/landing_pages/325779/

GravityID commented 2 years ago

My github id is 74195338