agenda.md

DIF Identifiers & Discovery WG – Rolling Agenda & Minutes

WG projects | DIF page | Mailing list and Wiki | Recordings

For this call, you are encouraged to turn your video on. This is a good way to build rapport given we are a large, disparate group experiencing a lot of churn.

This document is live-edited DURING each call, or shortly after the call, and stable/authoritative copies live on our github repo under /agenda.md . Please note that we might not notice a pullrequest in time, but you are free to propose agenda items for future meetings via hackmd.

Meeting information - Bi-weekly Mondays 1400 ET

• Before your contribute - join DIF and sign the WG charter (both are required!)
• Time: Every other Monday, 14:00-15:00 ET
• Calendar entry
• Zoom room, Meeting ID: 81528204613, Passcode: 908914

Special Work Item Calls:

In addition to the regular I&D WG meetings, we also hold Work Item Calls dedicated to individual work items. Any work item lead can organize Work Item Calls about their work item.

did:tdw Work Item Call - Every second Thursday 0900 PT

This weekly Work Item Call is dedicated to the did:tdw work item. We discuss issues related to the specification, and how the Work Item could relate to other technologies.

Meeting page

DID Traits Work Item Call - Every second Tuesday 1700 CET

This weekly Work Item Call is dedicated to the DID Traits work item. We discuss issues related to the specification, and how the Work Item could relate to other technologies.

Meeting invite | Zoom room

Linked VP Work Item Call - Every second Thursday of the month 1900 CET

This weekly Work Item Call is dedicated to the Linked Verifiable Presentations work item. We discuss issues related to the specification, and how the Work Item could relate to other technologies.

Meeting invite | Zoom room

• Work Item Call - 11 Jul 2024 - (1900CET) canceled
• Work Item Call - 13 Jun 2024 - (1900CET) recording
• Work Item Call - 09 May 2024 - (1900CET) canceled
• Work Item Call - 11 Apr 2024 - (1900CET) recording
• Work Item Call - 14 Mar 2024 - (1900CET) recording
• Work Item Call - 08 Feb 2024 - (1900CET) recording
• Work Item Call - 11 Jan 2024 - (1900CET) recording
• Work Item Call - 14 Dec 2023 - (1900CET) recording

Universal Resolver Work Item Call - Wednesdays 0800 ET (discontinued)

This weekly Work Item Call is dedicated to the Universal Resolver work item. We discuss policy and governance topics (e.g. when to add/remove drivers), as well as technical topics (e.g. integration with the W3C DID test suite, monitoring, analytics, etc.).

Meeting invite | Zoom room

• Work Item Call - 19 May 2021 - (1300ET) recording
• Work Item Call - 26 May 2021 - (1300ET) cancelled
• Work Item Call - 02 Jun 2021 - (1300ET) recording
• Work Item Call - 09 Jun 2021 - (1300ET) recording
• Work Item Call - 16 Jun 2021 - (1300ET) recording
• Work Item Call - 23 Jun 2021 - (1300ET) recording
• Work Item Call - 30 Jun 2021 - (1300ET) recording
• Work Item Call - 07 Jul 2021 - (1300ET) canceled
• Work Item Call - 14 Jul 2021 - (1300ET) recording
• Work Item Call - 21 Jul 2021 - (0800ET) recording
• Work Item Call - 28 Jul 2021 - (0800ET) recording
• Work Item Call - 04 Aug 2021 - (0800ET) summer break
• Work Item Call - 11 Aug 2021 - (0800ET) summer break
• Work Item Call - 18 Aug 2021 - (0800ET) summer break
• Work Item Call - 25 Aug 2021 - (0800ET) summer break
• Work Item Call - 01 Sep 2021 - (0800ET) recording
• Work Item Call - 08 Sep 2021 - (0800ET) recording
• Work Item Call - 15 Sep 2021 - (0800ET) canceled
• Work Item Call - 22 Sep 2021 - (0800ET) canceled
• Work Item Call - 29 Sep 2021 - (0800ET) recording
• Work Item Call - 06 Oct 2021 - (0800ET) recording
• Work Item Call - 13 Oct 2021 - (0800ET) canceled
• Work Item Call - 20 Oct 2021 - (0800ET) canceled
• Work Item Call - 27 Oct 2021 - (0800ET)
• ...

DID Registration Work Item Call - Wednesdays 1100 CET (discontinued)

This weekly Work Item Call is dedicated to the DID Registration work item. We discuss scope and high-level architectural questions, work on the specification, and analyze other, related initiatives and specifications.

Meeting invite | Zoom room

• Work Item Call - 19 May 2021 - (1000ET) recording
• Work Item Call - 26 May 2021 - (1000ET) recording
• Work Item Call - 02 Jun 2021 - (1000ET) recording
• Work Item Call - 09 Jun 2021 - (1000ET) canceled
• Work Item Call - 16 Jun 2021 - (1000ET) rescheduled to 18 Jun 2021 - (0800ET)
• Work Item Call - 18 Jun 2021 - (0800ET) recording
• Work Item Call - 23 Jun 2021 - (1000ET) recording
• Work Item Call - 30 Jun 2021 - (1000ET) canceled
• Work Item Call - 07 Jul 2021 - (1000ET) canceled
• Work Item Call - 14 Jul 2021 - (1000ET) recording
• Work Item Call - 21 Jul 2021 - (1000ET) canceled
• Work Item Call - 28 Jul 2021 - (1000ET) canceled
• Work Item Call - 04 Aug 2021 - (1000ET) summer break
• Work Item Call - 11 Aug 2021 - (1000ET) summer break
• Work Item Call - 18 Aug 2021 - (1000ET) summer break
• Work Item Call - 25 Aug 2021 - (1000ET) summer break
• Work Item Call - 01 Sep 2021 - (1000ET) recording
• Work Item Call - 08 Sep 2021 - (1000ET) canceled
• Work Item Call - 15 Sep 2021 - (1000ET) canceled
• Work Item Call - 22 Sep 2021 - (1000ET) recording
• Work Item Call - 29 Sep 2021 - (1000ET) recording
• Work Item Call - 06 Oct 2021 - (1000ET) canceled
• Work Item Call - 13 Oct 2021 - (1000ET) canceled
• Work Item Call - 20 Oct 2021 - (1000ET) canceled
• Work Item Call - 27 Oct 2021 - (1000ET) recording
• Work Item Call - 03 Nov 2021 - (1000ET) recording
• Work Item Call - 10 Nov 2021 - (1000ET) canceled
• Work Item Call - 17 Nov 2021 - (1030ET) recording
• Work Item Call - 24 Nov 2021 - (1000ET) canceled
• Work Item Call - 01 Dec 2021 - (1000ET) canceled
• Work Item Call - 08 Dec 2021 - (1000ET) recording
• Work Item Call - 15 Dec 2021 - (1000ET) winter break
• Work Item Call - 22 Dec 2021 - (1000ET) winter break
• Work Item Call - 29 Dec 2021 - (1000ET) winter break
• Work Item Call - 05 Jan 2022 - (1000ET) winter break
• Work Item Call - 12 Jan 2022 - (1000ET) canceled
• Work Item Call - 19 Jan 2022 - (1000ET) canceled
• Work Item Call - 26 Jan 2022 - (1000ET) recording
• Work Item Call - 02 Feb 2022 - (1000ET) canceled
• Work Item Call - 09 Feb 2022 - (1100CET) recording
• Work Item Call - 16 Feb 2022 - (1100CET) recording
• Work Item Call - 23 Feb 2022 - (1100CET) canceled
• Work Item Call - 02 Mar 2022 - (1100CET) canceled
• Work Item Call - 09 Mar 2022 - (1100CET) canceled
• Work Item Call - 16 Mar 2022 - (1100CET) recording
• Work Item Call - 23 Mar 2022 - (1100CET) canceled
• Work Item Call - 30 Mar 2022 - (1100CET) canceled
• Work Item Call - 06 Apr 2022 - (1100CET) recording
• Work Item Call - 13 Apr 2022 - (1100CET) recording
• Work Item Call - 20 Apr 2022 - (1100CET) recording
• Work Item Call - 27 Apr 2022 - (1100CET) canceled (due to IIW)
• Work Item Call - 04 May 2022 - (1100CET) canceled
• Work Item Call - 11 May 2022 - (1100CET) canceled
• Work Item Call - 18 May 2022 - (1100CET) canceled
• Work Item Call - 25 May 2022 - (1100CET)
• ...

Draft Meeting - 16 Dec 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work item updates
5. Other topics?

Attendees

• TODO

Meeting - 02 Dec 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discuss work item proposal for <did>/whois (postponed)
5. [Sid Lamichhane] did:ipfs - https://www.youtube.com/watch?v=aabA1dFT-hI
6. Work item updates
7. Other topics?

Attendees

• TODO

Meeting - 18 Nov 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discuss work item proposal for <did>/whois (postponed)
5. Work item updates
   • DID Traits:
     • Timeline for 0.8 release has been set → Dec 10
     • Submissions of traits for this release are still open until the call next week.
6. Other topics?

Attendees

• Markus Sabadello
• Rob Aaron
• Tom Jones
• Jan Christoph Ebersbach

Meeting - 4 Nov 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Update from IIW
5. Work item updates
6. Other topics?

Attendees

• TODO

Meeting - 21 Oct 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work item updates
   • did:tdw:
     • 0.4 version is almost ready.
     • 4-5 implementations exist.
     • Custom website for did:tdw didtdw.org
     • DID method will be registered.
     • Universal Resolver implementation is being planned.
     • Presentations will be held at the upcoming IIW.
     • Merger of did:web and did:tdw is being dicussed.
     • did:tdw server is being implemented with UNTP.
   • DID Traits:
     • Important meeting last week with the conclusion that "metadata" like "is a universal resolver driver available" will not be part of the traits specification. The specification will solely focus on binary traits like "is key pre-rotation supported".
     • The next step is to define what will be part of the 0.1 release.
5. Other topics?

Attendees

• Stephen Curran
• Rob Aaron
• Dolores Macauley
• João Otávio Cano
• Joao Pedro Alonso Almeida
• Jan Christoph Ebersbach

Meeting - 07 Oct 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
   • Markus informs the group: there are currently two new calls in addition to the bi-weekly regular working group call.
   • Markus informs the group: https://blog.identity.foundation/did-method-standardization-initiative-progress-update-and-next-steps/
4. Work item updates
   • did:tdw:
     • Version 0.4 has been merged. This is likely the last big change before releasing version 1.0.
     • The implementation of a witness has been updated.
     • The plan is deploy the implementations in production scenarios in the next few weeks.
   • DID Traits: The first deliverable of an aligned list of traits is under way. More feedback is needed from more people.
5. DID portability, DID rotation, redirecting a DID
   • Joao and Christoph: a specification and implementation has been created that allows a DID to have a successor DID.
   • The functionality could be added as a trait to the DID Traits effort.
   • The W3C DID specification could also reference this DID rotation specification.
   • Idea: The functionality could be added to the Universal Registrar, so adding references and deactivating the old identifier becomes one function call to the registrar.
   • Potential issue: The semantics of the current specification that uses the "also known as" attribute are not entirely clear. This could be resolved in an official specification.
6. Other topics?

Attendees

• Jao Pedro Alonso Almeida
• João Otávio Cano
• Stephen Curran
• Christoph Fabianek
• Markus Sabadello
• Jan Christoph Ebersbach

Meeting - 23 Sep 2024 - (1400 ET) canceled due W3C TPAC 2024

Meeting - 09 Sep 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Update on DID Traits
5. Update on did:tdw
6. Other topics?

Attendees

• TODO

Meeting - 26 Aug 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. New work item: did:tdw
   • did:tdw addresses some of the feedback that was expressed about did:web.
   • This working group has a history of working on DID method standardization, did:tdw fits in well.
   • Stephan Curran gives an overview of did:tdw. The goal of did:tdw is to improve did:web. [Link to presentation](Presentation: https://docs.google.com/presentation/d/12NSbKbE3YfjjPuq8m0uEdn6hQ43wbW3YrW5auksbASQ/edit?usp=sharing)
   • An important reason for bringing did:tdw to DIF is to find a neutral place to standardize and merge it with did:web eventually.
   • Next steps:
     • The work item will be presented to the working group.
     • Once the working group approves it, the work item can be started and repositories will be transferred and set up at DIF.
5. Update DID Traits
   • The call will be a bi-weekly call on Tuesday, 5pm CEST. The first call will be on 03.09. 5pm CEST.
6. Review: ID WG work items (remainder)
   • Universal Resolver and Registrar - is maintained with little resources.
   • did-common-java - dependency of registrar, etc. is maintained.
   • did-common-dotnet - appears abandoned.
   • did:peer - not yet ratified, should be pushed forward so it can be ratified.
   • secret recovery - abandoned, not enough interest.
   • did-resolver and did-jwt are active.
   • DID spec extensions - extensions that are registered in the W3C did spec registries, maintained by Markus.
   • Rust did:key - appears abandoned.
   • DID registration - spec is complete and active.
   • DID Method Enumeration - spec is not complete, yet. Align with Sam.
   • Markus will update the list of work items.
7. Other topics?

Attendees

• Stephan Curran
• Kim Duffy
• Markus Sabadello
• Patrick St. Louis
• Rob Aaron
• Przemek
• PmcB
• Jan Christoph Ebersbach

Meeting - 12 Aug 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Approval DID Traits Work Item
   • The work item has been accepted by the working group.
   • A repository will be set up to store the results.
   • A separate call will be set up to align and work on this item.
   • Christoph brought up the idea of testing traits in an automated manner. Guidance and test harnesses could be additional deliverables for this work item.
5. Review: ID WG work items (remainder)
   • postponed to next week.
6. Other topics?

Attendees

• Christoph F.
• Jan Christoph Ebersbach

Meeting - 29 Jul 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Jack] Delegating from one DID to another, signing VCs on behalf of another DID
   • Jack shares about key delegtation that they have implemented at Tonomy Foundation. However, the solution is not very privacy preserving.
   • The proposal is to create a delegated DID that just lives in the browser and that can be trace back to the origintal DID.
   • All existing delegation approaches require an update of the original DID document.
   • Idea: create a new DID method that encodes a delegation VC into the DID. The VC proves the delegation, because the VC is signed by the original DID.
   • Use case: Single Sign-on via an "authorized" DID.
   • Challenge: capability delegation / DID linking could also be done via plain Verifiable Credentials.
   • Next step: Jack will take the feedback and get back to the WG once the idea becomes more mature.
5. Update on DID Traits
   • Updated document: https://gist.github.com/jceb/8e37e4900e815eb14b207ad7e8d02a6c
   • Feedback:
     • DID Traits is a useful work item.
     • Use a better word for "Trait", maybe "Characteristics".
     • Add a trait the show whether the document is hosted some, e.g. relevant for privacy purposes.
   • Next step: request feedback from the working group for the next two weeks and then officially accept the work item at the next call in 2 weeks.
6. Proposal: ID WG Survey
   • Didn't get to it.
7. Review: ID WG work items (remainder)
   • Didn't get to it
8. Other topics?

Attendees

• Markus Sabadello
• Jack Tanner
• Tom Jones
• Jan Christoph Ebersbach

Meeting - 15 Jul 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. Update: Completion of Linked-VP work item
   • Work item is complete.
   • It received much interest from people and entities around the world.
   • The monthly call isn't needed anymore and will be canceled.
3. Proposal: New work item DID Traits (including update on discussion with ToIP and OpenWallet Foundation)
   • Jan Christoph presents current status of proposal https://gist.github.com/jceb/8e37e4900e815eb14b207ad7e8d02a6c
   • Alignment with Trust over IP Foundation (Drummond Reed) and OpenWallet Foundation (Mirko Mollik) happened, they are very interested in the results and will selectively support the work item.
   • Feedback in the call concerning the proposal:
     • Participants find work item useful.
     • Suggestion: in the work item we should think about the presentation of the traits in other places, e.g. a DID method specification document, as a "food nutrition label".
     • Suggestion: create a formal definition of each trait, ideally with test vectors that could be applied to DID methods.
     • Suggestion: Interconnect the work with W3C did-wg by linking back and forth between the specifications.
   • Jan Christoph raises the question of how the work item should be called: Identifier Traits vs DID Traits. Feedback:
     • Mixed feedback, the idea to apply the traits framework to other types of identifiers is a noble cause that could also become very difficult to maintain.
     • We conclude that the introduction will state that the framework could be applied to other identifier schemes without providing any guarantees of how well it fits.
   • Who should participate:
     • People who created the rubric.
     • Everyone on the call + ID WG.
     • Joe Andrew.
     • Google and Apple - people who evaluated the DID specification / methods.
   • Next step: Create draft and propose work item to the working group.
4. Review: ID WG work items
   • Universal Resolver and Registrar - is maintained with little resources.
   • did-common-java - dependency of registrar, etc. is maintained.
   • did-common-dotnet - appears abandoned.
   • did:peer - not yet ratified, should be pushed forward so it can be ratified.
   • secret recovery - abandoned, not enough interest.
   • did-resolver and did-jwt are active.
   • DID spec extensions - extensions that are registered in the W3C did spec registries, maintained by Markus.
   • We didn't managed to finish the list of work items (https://github.com/decentralized-identity/identifiers-discovery/blob/main/README.md). Next one is: Rust did:key Implementation.
5. Proposal: ID WG Survey
   • We didn't get to this topic.
6. Move meeting to a different time
   • We didn't get to this topic.
7. Other topics?

Attendees

• JC Ebersbach
• Markus Sabadello
• Bumblefudge
• Brian
• Sam Curren
• Tom Jones

Work Item Meeting - Linked Verifiable Presentations - 11 Jul 2024 - (1900 CET) canceled

Meeting - 01 Jul 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Linked-VP work item approved by Steering Committee
5. New Co-chair proposal JC Ebersbach
6. Updates on DID Traits
7. Response by DIF to EUDI Wallet Architecture Reference Framework
8. ID WG summer meeting schedule
9. Other topics?

Attendees

• JC Ebersbach
• Kim Hamilton Duffy
• Markus Sabadello

Meeting - 17 Jun 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. New work item for describing DID method functionalities ("DID Traits"), e.g.
   • Can DIDs be updated/deactivated?
   • Is it possible to view the history of a DID (using versionId, versionTime)?
   • Is the DID always resolvable without extra information?
   • Is it possible to enumerate all DIDs that exist globally?
   • Also see here, initial work by JC Ebersbach: https://gist.github.com/jceb/8e37e4900e815eb14b207ad7e8d02a6c
5. Other topics?

Attendees

• JC Ebersbach
• Rob Aaron
• Victor Lu
• Markus Sabadello

Work Item Meeting - Linked Verifiable Presentations - 13 Jun 2024 - (1900 CET) recording

Meeting invite | Zoom room

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work Item - Linked Verifiable Presentations: https://github.com/decentralized-identity/linked-vp
5. Other topics?

Attendees

• Jan Christoph Ebersbach
• Rob Aaron
• Markus Sabadello

Meeting - 03 Jun 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Important attributes when comparing DID methods, see thread https://difdn.slack.com/archives/C4WED8JSH/p1714988601534219?thread_ts=1714988601.534219&cid=C4WED8JSH
5. Other topics?

Attendees

• JC Ebersbach
• Rob Aaron
• Markus Sabadello

Meeting - 20 May 2024 - (1400 ET) canceled

Work Item Meeting - Linked Verifiable Presentations - 09 May 2024 - (1900 CET) canceled

Meeting - 06 May 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [MG] Updates from GoPlausible about a universal DID resolver with extra features
5. [ezequiel] Key rotation, and identifying specific versions
6. Other topics?

Attendees

• M G
• ezequiel
• Rob Aaron
• Markus Sabadello

Meeting - 22 Apr 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [MG] Next steps for Universal DID resolver on ChatGPT
5. Other topics?

Attendees

• M G
• Markus Sabadello
• Oleksandr Brezhniev

Work Item Meeting - Linked Verifiable Presentations - 11 Apr 2024 - (1900 CET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work Item - Linked Verifiable Presentations: https://github.com/decentralized-identity/linked-vp
5. Other topics?

Attendees

• https://us02web.zoom.us/rec/share/uyFPBbcHesiDsfa47EP5yqgN0dzvPUq_Bk2Fy0v5Yx6FYWX-MfkfA9TLP0CZS8dA.QkdHmcInTq4Az4ob

Meeting - 08 Apr 2024 - (1400 ET)

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [JCEbersbach] Status update on Linked VP Work Item: https://github.com/decentralized-identity/linked-vp
5. [MG] Alternatives to Universal Resolver/Registrar in other languages
6. Other topics?

Attendees

Meeting - 25 Mar 2024 - (1400 ET) canceled due to Easter holidays

Work Item Meeting - Linked Verifiable Presentations - 14 Mar 2024 - (1900 CET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work Item - Linked Verifiable Presentations: https://github.com/decentralized-identity/linked-vp
5. Other topics?

Attendees

• Markus Sabadello
• Jan Christoph Ebersbach

Meeting - 11 Mar 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [DanielB] Update on potential did:dht Work Item: https://did-dht.com/
5. [JCEbersbach] Update on Linked VP Work Item: https://github.com/decentralized-identity/linked-vp
6. [AndorK] Work on service profiles: https://github.com/trustoverip/tswg-trust-registry-service-profile, https://service-profiles.andor.us/
7. Other topics?

Attendees

• Markus Sabadello
• andor
• Limari Navarrete
• Rob Aaron
• Tom Jones

Meeting - 26 Feb 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [AndorK] Announcement about work on service profiles: https://github.com/trustoverip/tswg-trust-registry-service-profile
5. [DanielB] Proposed new did:dht Work Item: https://did-dht.com/
6. [JCEbersbach] Review of Linked VP Work Item: https://github.com/decentralized-identity/linked-vp
7. Other topics?

Attendees

• Daniel Buchner
• Jan Christoph Ebersbach (Identinet)
• andor
• Tom Jones
• Brian Richter
• Markus Sabadello

Meeting - 12 Feb 2024 - (1400 ET) canceled

Work Item Meeting - Linked Verifiable Presentations - 08 Feb 2024 - (1900 CET) recording

Meeting invite | Zoom room

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work Item - Linked Verifiable Presentations: https://github.com/decentralized-identity/linked-vp
5. Other topics?

Attendees

Meeting - 29 Jan 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [MarkusS, ChristophF] Update on DID Rotation, and integration with Universal Resolver/Registrar
5. [FrankH, MarkusS] Work at TBD / Block related to DID Registration spec (https://identity.foundation/did-registration/)
6. Other topics?

Attendees

• Markus Sabadello
• Frank Hinek
• George Padvorac
• Rob Aaron
• Christoph Fabianek

Meeting - 15 Jan 2024 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Christoph] DID Rotation, integration with Universal Resolver/Registrar
5. Other topics?

Attendees

• Christoph Fabianek
• Rob Aaron
• Victor Lu
• Kabir Maiga
• Markus Sabadello
• Nikos Fotiou

Work Item Meeting - Linked Verifiable Presentations - 11 Jan 2024 - (1900 CET) recording

Meeting invite | Zoom room

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work Item - Linked Verifiable Presentations: https://github.com/decentralized-identity/linked-vp
5. Other topics?

Attendees

• Jan Christoph Ebersbach (identinet)
• Brian Richter
• George Padvorac
• Markus Sabadello
• Tom Jones

Meeting - 01 Jan 2023 - (1400 ET) canceled due to New Year holiday

Meeting - 18 Dec 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Christoph] DID Rotation
5. Other topics?

Attendees

• Markus Sabadello
• Christoph Fabianek
• Tom Jones
• Victor Lu

Work Item Meeting - Linked Verifiable Presentations - 14 Dec 2023 - (1900 CET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Work Item - Linked Verifiable Presentations: https://github.com/decentralized-identity/linked-vp
5. Other topics?

Attendees

• Markus Sabadello
• Limari
• Jan Christoph Ebersbach
• Brian Richter

Meeting - 04 Dec 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Gabe] Intro and discussion about did:dht - https://did-dht.com/
5. Other topics?

Attendees

• Daniel Buchner
• Gabe Cohen
• Christoph Fabianek
• Otto Mora
• Markus Sabadello

Meeting - 20 Nov 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [JC Ebersach] Status update about linked-vp work item
5. [Toby Bolton] .zkdid - .zkdns - A vision for a publicly owned, zero-knowledge decentralized DNS system
6. Other topics?

Attendees

• Markus Sabadello
• Tobes ZKDID
• George Padvorac
• Jan Christoph Ebersbach (Identinet)
• Limari
• Otto Mora
• Sam Curren (TelegramSam)
• William Lee
• Phil Wolff
• Nikos Fotiou

Meeting - 06 Nov 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Nikos] Representing DID documents as x509 certificates, the did:self case.
   • https://1drv.ms/p/s!AqzRT7TbXn4WhL141QGxh8V_83doxA?e=QDi6dF
5. Other topics?

Attendees

• Nikos Fotiou
• Christoph Fabianek
• Limari Navarrete
• Ruben Wolff
• Przemek Praszczalek
• Toni Akinjiola
• Markus Sabadello

Meeting - 23 Oct 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discussion about did:webs
5. Work item proposal: Well Known Verifiable Credential Configuration Specification

Attendees

• Markus Sabadello
• Jan Christoph (JC) Ebersbach

Meeting - 09 Oct 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [马若龙 / Ma Ruolong] Presentation of Xinghuo BIF and did:bid by China Academy of Information and Communications Technology (CAICT) slides
5. Other topics?

Attendees

• Chiye Sun - CAICT
• ma ruolong
• Markus Sabadello
• JC (identinet)
• Tom Jones
• Alen Horvat

Meeting - 25 Sep 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. (Bryan Newbold, Dmitri Zagidulin, Alex Colgan, others) Continue discussion about did:plc, did:web(s), etc.

   • links:

     • did:webplus https://didwebplus.com/ && https://github.com/LedgerDomain/did-webplus
     • did:webs https://trustoverip.github.io/tswg-did-method-webs-specification/
     • did:web 2.0 proposal: https://github.com/WebOfTrustInfo/rwot12-cologne/blob/main/advance-readings/did-web-2.0.md
     • did:web improvement proposals https://docs.google.com/presentation/d/1_Iy7W3ONnVUvunH6MTX13bup0Kiy5zC1XG8DGLCqX_I/
     • RWoT paper https://github.com/WebOfTrustInfo/rwot12-cologne/blob/main/draft-documents/beyond-did-web.md

   • Dmitri - features people want that did:web doesn't have

   • signing DID docs

   • hashlinks forward and backward

     • did:webs uses KERI KELs (key event logs) to link versions verifiable
     • did:webplus uses a self-signature
     • hash of "pre-rotation key" (next key that key will roll thru) in KERI and "recovery keys" (hash of backup key) in did:plc
       • bryan: we have a window within which a recovery key can restore control
       • bryan: signing key can also be a rotation key, no injunction against it

   • dmitri: historical doc query (does this VC verify with January 18 2021 8pm's key?)

     • mirko: I have heard of this requirement in court/legal cases
       • "retention period" obligations - see https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03125/TR-03125_node.html
     • mirko: aviation industry has this kind of 30year audit window, even if plane is decommissioned (download while chain of trust/x509 chain and attach to any documents; the DLT was appealing here as a more effective historical lookup mechanism at scale, to avoid huge attachments to each document)
     • bryan: moderators would need historical lookup in appeals, but the current trust model is that all previous did doc states are hosted by the current did controller's datastore, so it's not that high-trust;
     • alex: pharma supply chain use-cases definitely require this (needs to go back many years)

   • bengo: non-revocation check per vM, i.e., "to verify a signature from this DID, first check against a revocation registry for this key/DID, then check signature"

     • bengo: that need not be did-method-specific; could be did-core/cross-cutting
     • markus: vM rotation/revocation IS discussed in did core
       • https://www.w3.org/TR/did-core/#verification-method-revocation
       • https://w3c.github.io/vc-data-integrity/#controller-documents
       • stephen: revoked VERSUS rotated? i.e. revoking a past key kills all sigs, but rotation allows historical query?
       • mirko: x509 prior art: createdFrom and createdUntil set at time of issuance of a cert;
       • mirko: delete method in DID:WEB - just delete it (that's normal to versioned documents); adding a revoked flag would more explicitly kill it

   • bengo: hashlink to CURRENT did doc

     • (could be non-breaking change?)
     • did:web:bengo.is?hl={didDocHash}
     • sidebar: which hashlinks, tho? sporny's IETF draft is abandoned, but subresource integrity standard in use in browsers and specified at W3C

   • tombstoning

     • did:web just deletes the wellknown doc instead of having a separate semantic fo empty/dead ones
     • bryan: if a did is tombstoned, and someone else buys the domain, can they publish a new doc?
       • dmitri: account mobility in social web use-case
       • mirko: did:web has only one witness (current domain owner)

   • Bengo - is anyone committed to implementing any of these?

   • Stephen C: backwards compat is a goal for my use-cases

   • Alex: Presi of did:webplus work to date for the recording/record - https://didwebplus.com/

     • Markus: any known features of KERI you chose to leave out of scope?
       • OOBI (out-of-band introduction) from did:peer/didcomm tradition
       • "forking" of DID doc/microledger - KERI has elaborate protections against that, this we don't know how to protect against that without a formal witness/snapshot device
         • mirror on CDNs or other VDRs = commonsense protection against revisionist/collusive did controllers
         • mirko: static backend allowed by did:web (and a target of did:webs/KERI, which publishes snapshots to static backend); did:webplus and did:web2 seem to require a dynamic backend, don't they?
         • alex: active backend isn't a problem for our use-case, external frameworks and unfamiliar standards (much less trusted clients) are, tho
       • mirko: size of downloaded resources?
         • alex: not at benchmarking stage yet
         • mirko: bandwidth to download and walk a series of docs
           • KELs are strings of delta/patch doc that only contain the rotated keys
           • compute - processing a KEL versus checking hashlinks on a series of whole-did docs

   • next steps

     • open issues on did:webplus, did:webs and elsewhere!
     • future installments of this call? propose an agenda, yall!
5. Other topics?

Attendees

• Juan Caballero
• Mirko Mollik
• Alex Colgan
• bengo
• Byran Newbold
• Christoph Fabianek
• Dmitri Zagidulin
• Przemek Praszczalek
• Sam Curren
• Stephen Curran
• hans boone
• Markus Sabadello

Meeting - 11 Sep 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. (JC Ebersbach) Lifecycle of did:web identifiers
   • CRUD operations for did:web
   • Integration with Universal Registrar
   • Slides: https://slidesdown.github.io/?slides=https%3A%2F%2Fgist.githubusercontent.com%2Fjceb%2F4bfcfdcddd2020e5b7e521b9e1044f3b%2Fraw
   • Gist: https://gist.github.com/jceb/4bfcfdcddd2020e5b7e521b9e1044f3b
5. (JC Ebersbach) Browser plugin that displays and verifies DIDs and VCs from .well-known
   • Started as a project during did:hack
   • https://github.com/identinet/identinet-plugin
6. Other topics?

Attendees

• JC Ebersach
• Lance B
• Sam Curren
• Markus Sabadello
• Patrick Herbke
• Tom Jones

Meeting - 28 Aug 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. (Sam) Expressing support for DID methods
   • https://hackmd.io/qz2Mbx7_RuOVLf9YQnz_rA?view
5. Other topics?

Attendees

• Markus Sabadello
• Sam Curren
• DNaicker
• Toni Akinjiola
• Przemek Praszczalek

Meeting - 14 Aug 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Special Topic: BlueSky and did:plc (Bryan Newbold)
   • https://github.com/bluesky-social/did-method-plc
   • https://plc.directory/did:plc:44ybard66vv44zksje25o7dz
   • https://plc.directory/did:plc:44ybard66vv44zksje25o7dz/log/audit [email protected]
5. did:web Improvement Proposals (Dmitri Zagidulin)
   • https://docs.google.com/presentation/d/1_Iy7W3ONnVUvunH6MTX13bup0Kiy5zC1XG8DGLCqX_I/

Attendees

• Markus Sabadello
• Dmitri Zagidulin
• Bryan Newbold
• Benjamin Goering
• Christoph Fabianek
• Clare Nelson
• Denver Naicker
• Limari
• Wendy Seltzer
• bumblefudge

Meeting - 31 Jul 2023 - (1400 ET) canceled

Meeting - 17 Jul 2023 - (1400 ET) canceled

Meeting - 03 Jul 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Update on JSON Schema for DID documents
5. [Christoph] DID document validation approaches with SHACL, JSON Schema, JSON-LD
   • DID Document validation through API endpoints (interim solution):
   • with SHACL: https://didlint.ownyourdata.eu/api/validate_shacl/did:oyd:zQmYc4PjcDZde9NmAb2WPFHZqt6WFdY4tSA37moJgtR3agj
   • definition: https://soya.ownyourdata.eu/Did/yaml
   • with JSON-Schema: https://didlint.ownyourdata.eu/api/validate_json-schema/did:oyd:zQmYc4PjcDZde9NmAb2WPFHZqt6WFdY4tSA37moJgtR3agj
   • definition: https://github.com/w3c/did-spec-registries/blob/main/json_schemas/core.schema.json
   • for JSON-LD compliance: https://didlint.ownyourdata.eu/api/validate_jsonld/did:algo:c93fdef1-8a0a-4c65-8c54-fd33117c9e82
   • based on: https://json-ld.org/playground/
   • YAML templating: https://www.json2yaml.com/
6. Other topics?

Attendees

• Markus Sabadello
• Andor Kesselman
• Christoph Fabianek
• Toni Akinjiola
• Przemek

Meeting - 19 Jun 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Conversation on DIDs and Nostr at 1500 ET: https://meet.jit.si/ImagineNostrAndDIDs
5. New work item proposal: JSON Schema for DID documents
6. Discussion about Proof of Humanity / Proof of Personhood
7. Other topics?

Attendees

• Markus Sabadello
• Andor Kesselman
• Christoph Fabianek
• Alen Horvat
• Clare Nelson
• Otto Mora
• Toni Akinjiola

Meeting - 05 Jun 2023 - (1400 ET) canceled

Meeting - 22 May 2023 - (1400 ET) canceled

Meeting - 08 May 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Brian Richter] Bitcoin Ordinals DID Method (did:btco)
5. Other topics?

Attendees

• Markus Sabadello
• Christoph Fabianek
• Angeles Costarelli
• Brent Shambaugh
• Brian Richter

Meeting - 24 April 2023 - (1400 ET) canceled

Meeting - 10 April 2023 - (1400 ET) canceled due to vacation

Meeting - 27 March 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. DIDs for legal entities and natural persons
   • GDPR, unlinking VCs from DIDs, account abstraction, ZKs, etc.
5. Introduction of did:polygonid by Otto Mora
6. Other topics?

Attendees

• Markus Sabadello
• Otto Mora
• Christoph Fabianek
• Clare Nelson
• Juan Caballero
• Limari Navarrete
• Toni Akinjiola

Meeting - 13 March 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Cheqd] New Universal Registrar driver for did:cheqd:
   • https://docs.cheqd.io/identity/architecture/adr-list/adr-004-did-registrar
   • https://did-registrar.cheqd.net/api-docs/
5. Other topics?

Attendees

• Markus Sabadello
• Tom Jones
• Toni Akinjiola
• Ankur Banerjee
• Fábio Pinheiro
• Angeles Costarelli

Meeting - 27 February 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. New Universal Registrar driver for did:cheqd
5. Driver development for Universal Resolver and Universal Registrar
   • https://github.com/decentralized-identity/universal-resolver/blob/main/docs/driver-development.md
   • https://github.com/decentralized-identity/universal-registrar/blob/main/docs/driver-development.md
6. Continued discussion about versionTime parameter, in combination with timestamping service on a VC
7. DID document validation with DID Lint
   • Discussion about integrating DID Lint with Universal Resolver, to highlight problems with methods/drivers
   • Use of Github actions and Github pages
   • Structure of a .json file with DID Lint results
   • https://didlint.ownyourdata.eu/
8. Other topics?

Attendees

• Markus Sabadello
• Toni Akinjiola
• Angeles Costarelli
• Christoph Fabianek
• Fábio Pinheiro

Meeting - 13 February 2023 - (1400 ET) canceled

Meeting - 30 January 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Timing issues and guarantees
   • Time of rotating and revoking keys in DID documents (versionId, versionTime, etc.)
   • Time of credential issuance (validFrom, validUntil, iat, exp, etc.)
5. Other topics?

Attendees

• Alen Horvat
• Christoph Fabianek
• Toni Akinjiola
• Salustiano Zavalía
• Angeles Costarelli

Meeting - 16 January 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Quick note about "Grand Unified Theory of Trust" presentation by Daniel Hardman: https://us02web.zoom.us/rec/share/3T2MqVs6gUCnAosPzcegAPq_6dFN8i3zkuKI04nSlPnTaHTDs0tWusbX5G_-FH-Y.pS40kM3zazC_MaYz
5. [Christoph] DID Lint - The DID Validator: https://didlint.ownyourdata.eu
   • Based on SOyA (Semantic Overlay Architecture - https://www.ownyourdata.eu/en/soya/)
   • Start with a data structure description, then transform it to JSON-LD and SHACL to perform validation
   • Generic approach, can also be applied to VC, VP, etc.
   • Some discussion about resolvers, DID Lint could be integrated into a CI/CD pipeline
   • Can be run as API, or locally as Docker container
   • Discussion about relationship to DID test suite (https://github.com/w3c/did-test-suite/)
6. Other topics?

Attendees

• Christoph Fabianek
• Sebastian Haas
• Markus Sabadello
• Bernhard Fuchs
• Jan Lindquist
• Rob Aaron
• Tom Jones
• Toni Akinjiola
• Veikko E

Meeting - 02 January 2023 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Short discussion about DID Lint service available here: https://didlint.ownyourdata.eu
   • Relationship to W3C DID test suite (https://github.com/w3c/did-test-suite/) and DIF Universal Resolver (https://github.com/decentralized-identity/universal-resolver)
   • We will have a presentation by Christoph Fabianek about the DID Lint service on the next call

Attendees

• Christoph Fabianek
• Markus Sabadello
• Jan
• Sebastian Haas

Meeting - 19 December 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. General discussion, roadmap, plans for 2023
5. Other topics?

Meeting - 05 December 2022 - (1400 ET) canceled

Meeting - 21 November 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Report from Internet Identity Workshop #35
5. DIDs with public key as identifier
6. Other topics?

Meeting - 07 November 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. IIW plans?
4. Agenda creation/review/prioritization
5. [Nikos, Antonio, others] Off-chain DIDs, KILT "light DIDs", did:self, ...
6. Other topics?

Meeting - 24 October 2022 - (1400 ET) canceled

Meeting - 10 October 2022 - (1400 ET) canceled

Meeting - 26 September 2022 - (1400 ET) canceled due to Rebooting-the-Web-of-Trust 11

Meeting - 12 September 2022 - (1400 ET) canceled due to W3C TPAC

Meeting - 29 August 2022 - (1400 ET) summer break

Meeting - 15 August 2022 - (1400 ET) summer break

Meeting - 01 August 2022 - (1400 ET) summer break

Meeting - 18 July 2022 - (1400 ET) summer break

Meeting - 04 July 2022 - (1400 ET) summer break

Meeting - 20 June 2022 - (1400 ET) - canceled (due to travel)

Meeting - 06 June 2022 - (1400 ET) - canceled (due to holidays)

Meeting - 23 May 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Short discussion about EU Digital Identity Wallet, EBSI/ESSIF, eIDAS 2.0, VCs, ISO mDL, etc.
5. [Christoph] Displaying / rendering the content of a DID document
   • Presentation of Semantic Overlay Architecture (SOyA), work done together with IDunion
   • Definition of a data model using a .yml file, then transformation to different representations
   • Demo of command line tool, and automatically rendered UI
   • Some discussion about JSON-LD, RDF, content-addressing
   • Use of overlays, SHACL
   • Discussion about DID document data model, and how it could be modeled/transformed with SOyA
6. Other topics?

Attendees

• Chris Kelly
• Markus Sabadello
• Dan Bachenheimer
• Christoph Fabianek
• Tom Jones
• Kabir Maiga

Meeting - 09 May 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discussion about EU "Proposal for Ecodesign for Sustainable Products Regulation" - https://ec.europa.eu/environment/publications/proposal-ecodesign-sustainable-products-regulation_en
5. DIF comment on identifiers in above proposal: https://docs.google.com/document/d/1yMmu92iPWr7zBGjXUlgQhn3gGOwEiE59Iei1Y4stf7g/
6. Discussion about DIDs and GDPR, non-blockchain-based DID methods, "ephemeral" DID methods such as did:key, situation in various communities such as EBSI, IDuion
7. Discussion about key recovery
8. Discussion about key types, FIPS
9. Approaches to who can update a DID document, guardian use cases

Attendees

• Markus Sabadello
• Tom Jones
• Paul Grehan
• Keith Kowal

Meeting - 25 April 2022 - (1400 ET) - canceled (due to IIW)

Meeting - 11 April 2022 - (1400 ET) - canceled

Meeting - 28 March 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. did:oydid Universal Registrar driver: decentralized-identity/universal-registrar#53
5. DID Registration specification: https://identity.foundation/did-registration/
6. DID spec extension error codes for security policies: https://github.com/decentralized-identity/did-spec-extensions/#extension-errors
7. Other topics?

Attendees

• Markus Sabadello
• Christoph
• Chris Kelly
• Lance Byrd

Meeting - 14 March 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. How to move from one DID method to another?
   • Demonstation by Christoph of did:oydid
   • Discussion of DID document (metadata) properties: alsoKnownAs, equivalentId, canonicalId
   • Discussion of signing DIDs and DID documents
   • alsoKnownAs is also used by Mastodon when moving accounts: https://docs.joinmastodon.org/spec/activitypub/
   • did:peer has the concept of "grafting": https://identity.foundation/peer-did-method-spec/#grafting
   • KERI is designed to move identifiers between different underlying systems
5. Other topics?

Attendees

• Markus Sabadello
• Christoph
• Brian Richter

Meeting - 28 February 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discussion on key rotation and proving control/possession of DIDs
5. Discussion on EU funding for EIDAS, digital wallets
6. Other topics?

Attendees

• Markus Sabadello
• Alen Horvat
• Chris Kelly
• Christoph Fabianek
• TomJ

Meeting - 14 February 2022 - (1400 ET) - canceled

Meeting - 31 January 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Community browser extension and abstract wallet architecture (continued topic from last week)
   • Discussion mobile wallet app vs. extension
   • Extension comes with default, but other modules can replace certain parts, e.g. present a better dashboard
   • Community defines the (sets of) basic functions, then we define an extensibility model, e.g. what modules can you plug in
5. Presentations at DIFCON
   • https://docs.google.com/spreadsheets/d/1iX-JgpPdJMRm_Ie62oicKgFNU21zbPAI8Xix4MuyCjE/
   • https://docs.google.com/forms/d/e/1FAIpQLScvLp96rple1UaYp4LpGOGOjvoh-_KwuhIZjA7mtBaB8iOWqw/viewform
6. Other topics?

Attendees

• Markus Sabadello
• Chris Kelly
• Daniel Buchner
• Alen Horvat

Meeting - 17 January 2022 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Markus] Short update on W3C DID Core formal objections
5. [Oliver] Short introduction to https://github.com/idp2p/idp2p
6. [Daniel] Begin work on DID Authn and Authz DOM APIs as a first contribution to a set of Web platform enhancements
   • Identity on the web is not great if you don't have an extension.
   • It doesn't make sense to repeat the identity extension layer over and over again.
   • Generic methods should be available to pages, e.g. a "navigator.did.*" namespace
   • Functions such as what DID methods are supported, does the user have a wallet, directed DID Auth support, key management, signing
   • Overarching goal: Can we as a community ship a single extension? Enable vendors to have different UIs, but not constantly repeat the same thing over and over again. Vendors can differentiate and innovate on top of that.
   • Community-maintained extension, ships with some basic UI, which can be replaced by vendors.
   • Is this like Web3 Ethereum wallets, e.g. Metamask with snaps?
   • For the ethereum ecosystem, this might be related: VC: https://github.com/veramolabs/credential-provider-eip, DID: https://eips.ethereum.org/EIPS/eip-2844.
   • Make some things modular to allow for innovation, e.g. integrate with hardware, eIDAS, etc.
   • Overlap with other projects, e.g. Universal Wallet, CHAPI.
   • Also see presentation by Liam McCarty on 13 September 2021 about "Bridging Digital and Physical".

Attendees

• Markus Sabadello
• Daniel Buchner
• Brian Richter
• Oliver Terbu
• Tom Jones
• Alen Horvat

Meeting - 03 January 2022 - (1400 ET) winter break

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. (TBD) DIDs as personal data: https://hackmd.io/krdcNluqSnyv-hFdqpVRXQ
5. Other topics?

Attendees

Meeting - 20 December 2021 - (1400 ET) canceled

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Short updates regarding Universal Resolver
   • CVE-2021-44228 log4j vulnerability
   • Migration to Spring Boot: decentralized-identity/universal-resolver#259
5. Continued discussion of did:keri
   • Witnesses and resolution
6. Other topics?

Attendees

Meeting - 06 December 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
   • Christoph (OwnYourData)
   • Wolfgang Kampichler (OwnYourData)
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Vacation schedule?
5. Continued discussion of did:keri and relation to other DID methods
   • Work item: Type of identifiers this method supports and their intended use-cases (e.g., did:key)
   • Other work items: How to incept KERI-based DIDs and DID Documents with multiple keys associated with them
   • How to use events and how to use the KERI structure
   • Independent KERI key rotation
   • KERI and did:peer - efforts to align
   • Q: Open topic: How does the method prove uniquness?
   • KERI is described in a whitepaper. Goal: to summarise the core concepts and processing rules
   • https://github.com/decentralized-identity/keri/tree/master/kids
   • Q: Implementation maturity?
     • Implementation by Jolocom (in Rust) - implements the core
     • Other implementations - GO, Javascript
   • Q: KERI resolution
     • Multiple witnesses
     • Direct/indirect approach
     • Open question: how witnesses are defined? (public keys)
6. did:oyd method introduction: content-based addressing, does not rely on a blockchain, using event log for updates
   • did:oyd (https://github.com/OwnYourData/did-cmd/blob/main/docs/did-spec.md)
   • content-based addressing (verifiable mapping between DID and DID Document)
   • Present 3 artefacts of did:oyd: DID, DID Document, Log (events)
   • Presentation of the Create/Update/Deactivate methods
   • Presentation of the cloning method

Attendees

• Eugeniu Rusu
• Alen Horvat
• Juan Caballero
• Christoph Fabianek
• Wolfgang Kampichler
• David Waite
• Joachim
• Tom Jones

Meeting - 22 November 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Jolocom team] Current status of did:keri, and adding it as a work item to the ID WG.
   • Information and contextual documents: https://hackmd.io/@RYgJMHAGSlaLMaQzwYjvsQ/ByAYibtdF
   • Current did:keri method specification: https://identity.foundation/keri/did_methods/
   • Quick intro to KERI
     • KERI defines a number of events (e.g. inception, rotation, delegated inception, etc.), and also data structures and rules for processing them. Processing events leads to the current state of the identifier.
     • There are different types of identifiers, and different ways how events can get exchanged, e.g. ephemeral mode, exchange with counterparty (direct mode), exchange via witnesses (indirect mode).
     • The controller can select what witnesses they like, witnesses can also be rotated. This adds an abstraction layer, witnesses can be anything (ledger, or personal server, etc.)
   • Current status of did:keri
     • Previously there was did:un, some features were not yet supported. Jolocom had an implementation of direct mode, the intention was to use it on mobile wallets.
     • Then the intention was to switch from did:un to a more robust implementation of did:keri, using some good learnings from the initial experimentation work.
     • Some work is split across different environments, so besides a documentation effort there also needs to be some alignment.
     • The goal is to continue and further expand the work on the DID method specification, to figure out how all the KERI building blocks can be utilized together in a method spec.
     • In the future, the roadmap also includes globally resolvable (anywise) identifiers.
     • Some questions are still open, e.g.: How is a did:keri globally resolvable? How do I know what are the witnesses? How exactly do you contact the witness? How are different key purposes mapped to a key event log? How can additional metadata be associated with a DID? How do you implement discoverability?
     • Does did:keri by itself make sense, or only "KERI in the context of an existing DID method" (e.g. did:indy:keri)?
   • Next steps
     • The work in the KERI WG is in a special state. The goal is to "wrap" that current status of KERI so that the KERI spec work goes into a "sleep" state. There are two communities, one working in the Trust-over-IP Foundation (ToIP), one working at DIF.
     • The proposal is to contribute the KERI work itself to the Applied Cryptography Working Group, and the did:keri work to the Identifiers & Discovery Working Group (this group).
5. Other topics?

Attendees

• Markus Sabadello
• Eugeniu Rusu | Jolocom
• Alen Horvat
• Juan Caballero
• Brian Richter
• Christoph Fabianek
• David Waite
• Ezequiel
• joachim
• Stephen Curran

Meeting - 08 November 2021 - (1400 ET) canceled

Meeting - 25 October 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Check status of work items: https://github.com/decentralized-identity/identifiers-discovery/issues
5. Check status of work item calls: https://github.com/decentralized-identity/identifiers-discovery/blob/main/agenda.md#special-work-item-calls
6. Discuss next goals/milestones of the I&D WG.
7. Other topics?

Attendees

• Markus Sabadello
• Alen Horvat
• Kaliya
• Tom Jones
• Charles Lehner

Meeting - 11 October 2021 - (1400 ET) canceled

Meeting - 27 September 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. US mobile driver's license comment period: https://www.regulations.gov/commenton/DHS-2020-0028-0001
   • Discussion on RealID and ISO 18013-5: https://www.iso.org/standard/69084.html
   • Introduction to mDL technology
     • Hashes of each data element, bundle is signed
     • Age over X, selective disclosure is "clunky" but supported
     • No trust in user hardware, all calculation is done by issuer
   • Discussion on difference between ISO mDL and W3C VC standards
     • Competition or coexistence? Both have some support.
     • mDL written by issuers for issuers, more work needed on user and verifier perspectives.
     • mDL is not decentralized.
   • Digital wallets in Europe vs US
     • Who will isse the wallets? Centrally by the state, or free market with certification?

Attendees

• Markus Sabadello
• Alen Horvat
• Chris Kelly
• Andrew Hughes
• Tom Jones
• Kaliya Identity Woman

Meeting - 13 September 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Change call schedule to bi-weekly?
5. [Liam McCarty, Unum ID] Bridging Digital and Physical: Make Identifiers Identify
   • Summary:
   • Identifiers are only useful if they identify, which requires them to be reliably associated with people and things. In this talk, Liam McCarty of Unum ID will explain how to make such associations by leveraging the modern infrastructure of secure hardware and device biometrics. But he will also show that there’s currently a wide gap between how available this infrastructure is to different types of applications, and he will argue that this has been a significant barrier to adoption of decentralized identity systems. Finally, he will outline a path toward closing the gap and stress the importance of public advocacy in achieving that goal, which will finally make possible identifiers that identify.
   • Notes:
   • Association between physical world and digital identity is important.
   • In the physical world, we have "built-in private keys", we "are" a wallet.
   • There is a difference between access to hardware crypto on mobile vs. web.
   • Wallets in browsers are really hard, e.g. Safari deletes everything ter 1 week.
   • There is a need for generic hardware backed cryptographic signatures on the web.
   • Standards exist, but are of limited use:
     • WebAuthn allows access to hardware crypto, but only for authentication (no generic crypto operations): https://www.w3.org/TR/webauthn-2/
     • Web Crypto doesn't allow access to hardware crypto: https://www.w3.org/TR/WebCryptoAPI/
   • Calling for community action to support this, e.g. see these issues:
     • w3c/webauthn#1608
     • w3c/webcrypto#263
   • Some abandoned work on hardware based secure services:
     • https://www.w3.org/community/hb-secure-services/
     • https://rawgit.com/w3c/websec/gh-pages/hbss.html
   • Call to Action:
   • We need community action to advocate for general, hardware backed cryptographic signatures on the web! This would make it possible to build decentralized identity wallet web apps, not just mobile ones, dramatically improving odds of adoption. Please help the cause by commenting on the WebAuthn and WebCrypto GitHub issues pages, supporting my proposals there, and generally increasing awareness around this topic. This is a technical change that requires a decidedly nontechnical solution: community advocacy. Thanks for your help!

Attendees

• Markus Sabadello
• Alen Horvat
• Liam McCarty
• Chris Kelly
• Charles E. Lehner
• Tom Jones

Meeting - 06 September 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discussion in Slack: If you receive a message from a DID, what are approaches to information discovery on that DID?

Attendees

• Chris Kelly
• Cristopher Fabianek
• Tom Jones
• Alen Horvat

Meeting - 30 August 2021 - (1400 ET) summer break

Meeting - 23 August 2021 - (1400 ET) summer break

Meeting - 16 August 2021 - (1400 ET) summer break

Meeting - 09 August 2021 - (1400 ET) summer break

Meeting - 02 August 2021 - (1400 ET) summer break

Meeting - 26 July 2021 - (1400 ET)

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Update on Work Items
5. Continue discussion on historical key resolution?

Attendees

Meeting - 19 July 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Discuss ID WG call schedule
   • Proposal to move Universal Resolver Work Item Call to 0800ET instead of 1300ET.
   • Proposal to suspend main ID WG calls during August.
5. Short discussion around Solid and DIDs.
6. Universal Resolver returning a key in a given format (e.g., JWK(S))
   • Discussions on transform-keys DID URL parameter.
   • Specification is incomplete and needs more work. PoC has been implemented in Universal Resolver.
   • Parameter is registered in DID Spec Registries (which is a "note", not a "standard").
   • Discussion on trust boundaries and security implications of transforming keys in a DID document (only public keys!)
   • What are possible values? JWK, JWKS, base58, multibase, PEM, ...?
   • Discussion on this approach vs. use media types as in https://did.key.transmute.industries/.
7. Continue work on historical key resolution
   • Draft example of a data formats and DID URL here: https://hackmd.io/P45mLCRHTSWJX1oL1tZXKw
8. Other topics?

Attendees

• Markus Sabadello
• Alen Horvat
• Tom Jones
• Daniel Buchner

Meeting - 12 July 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Daniel] Historical key resolution
   • A DID document could point to a hub, which contains a list of historical keys associated with the DID. This list is signed by a current DID controller key.
   • Using DID URLs, it should be possible to point to a specific historical key at a specific point in time, and it can be dereferences publicly by anyone.
   • Maybe similar to this: did:example:123?service=IdentityHub&relativeRef=/CollectionsQuery?uri=https://identity.foundatio/KeyHistory#key-32
   • See https://identity.foundation/identity-hub/spec/#did-relative-urls
   • Discussion around how can this be trusted, since it's in your identity hub and you can change it at any time, and this information is separate from the underlying DID verifiable data registry.
   • Advantage: This is method-independent.
   • Discussion on relation between this approach and KERI's Key Event Logs.
   • Discussion on implementing this in the Universal Resolver. This could be supported as an extension of the UR; individual DID method drivers don't have to do anything.
   • The ID WG could start a new work item which defines the data structure of historical keys, as well as the format of DID URls that point to them.
5. Other topics?

Attendees

• Markus Sabadello
• Daniel Buchner
• Alen
• Juan Caballero
• Ezequiel
• Tom Jones
• Bradley Hinson
• Balázs Nemethi

Meeting - 05 July 2021 - (1400 ET) canceled

Meeting - 28 June 2021 - (1400 ET) - recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Special Work Item Calls
5. [Alen] EBSI Ledger and Trust
   • European Blockchain Service Infrastructure
   • List of Trusted Registries
   • Registry Properties
   • Discussion about "Onboarding Service"
   • Discussion LoA, key security, eIDAS
   • Current Status of EBSI
6. Other topics?

Attendees

• Markus Sabadello
• Alen Horvat
• Christoph (OYD)
• Juan Caballero (DIF)
• Kaliya Identity Woman
• Nikos Fotiou
• Steve Todd
• Tom Jones

Meeting - 21 June 2021 - (1400 ET) - recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Short update on Verifiable Conditions
5. Review of transform-keys DID parameter
   • Outdated in various ways (e.g. matrix parameters, "publicKey" property), needs to be updated to match latest DID Core
6. Discussion on DHS request for comments on mDL:
   • https://www.federalregister.gov/documents/2021/04/19/2021-07957/minimum-standards-for-drivers-licenses-and-identification-cards-acceptable-by-federal-agencies-for
   • https://www.govinfo.gov/content/pkg/FR-2021-04-19/pdf/2021-07957.pdf
   • Update: https://www.federalregister.gov/documents/2021/06/16/2021-12616/public-meeting-and-extension-of-comment-period-on-request-for-information-minimum-standards-for
7. Discussion on various eID projects in US and EU
8. Other topics?

Attendees

• Markus Sabadello
• Alen Horvat
• Tom Jones
• Juan Caballero
• Balázs Nemethi

Meeting - 14 June 2021 - (1400 ET) canceled

Meeting - 07 June 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Special Work Item Calls
   • Markus gave a quick update from the Special Work Item Calls about DID Registration and the Universal Resolver
5. [ezequiel] "controller" property in DID documents and verification methods.
   • "controller" on the top level seems clear, but on the "verificationMethod" is less clear.
   • "verificationMethod" can only have a single "controller", but verification methods can in fact be "controlled" by multiple entities (e.g. see the next topic - Verifiable Conditions)
   • See e.g. w3c/did-core#697
   • Seems like in practice we always have did_document.id === did_document.verificationMethod[N].controller
6. [Jack] Updates from Verifiable Conditions - https://github.com/w3c-ccg/verifiable-conditions
   • We discussed w3c-ccg/verifiable-conditions#3
   • Preference for second option ("Manu's proposal")
7. Other topics?

Attendees

• Markus Sabadello
• Ezequiel
• Jack Tanner
• Ajay Jadhav
• Samuel Smith

Meeting - 31 May 2021 - (1400 ET) canceled

Meeting - 24 May 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Special Work Item Calls
5. [ezequiel] "controller" property in DID documents and verification methods.
   • Ezequiel did not attend and the topic was skipped.
6. [Samuel Gómez Escalante] DID Key rotation/revocation
7. Other topics?

Discussion topic: DID Document signatures Samuel G.:

• DID Document owner signs the DID Document to protect the DID Document integrity.
• Purpose: to abstract the DID Registry implementation.
• The proof is static.
• The computation proof is automated.

Markus:

• The topic has been discussed many times.
• Outcome: DID Document signature by itself does not prove control of the DID.
• Only DID Document signature and anchoring (in a registry) can prove the actual ownership of the DID Document.

Alen: What is the added value of having a signature?

Samuel G.:

• DID Document integrity protection.
• Minimizing the technology dependence (of the registries).

Markus:

• DID Document signature only assures the DID Document integrity and not the link between the DID and DID Document. Ideally, you should run your own universal resolver and perform the full resolution.

Discussion outcomes:

• DID Documents may or may not require a signature, depending on the registry design.
• DID Document signature only proves the DID Document integrity.
• Only DID Document signature and anchoring (in a registry) can prove the actual ownership of the DID.
• Reliable DID resolution is important.

Discussion topic: DID key rotation and revocation

Open PRs

• w3c/did-core#741
• w3c/did-core#742

Samuel Smith clarifies the authorisation models

https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/IdentifierTheory_web.pdf

Tom points out the importance of machine-readable format for verification/validation.

Discussion outcome: Rotation/revocation topics should be addressed in the following meeting

Attendees

• Samuel Gomez - Gataca
• Juan Caballero
• Markus Sabadello
• Tom Jones
• David Waite
• Charles E. Lehner

• Balázs Nemethi

• Samuel Smith
• Alen Horvat

Meeting - 17 May 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. New Work Item Call schedule announced (DID Registration WI, Universal Resolver WI)
5. Universal Registrar - an overview
   • Universal Registrar - can obtaining access to registries be unified (from the wallet implementation perspective)?
     • References:
       • https://github.com/decentralized-identity/universal-registrar
       • https://uniregistrar.io/
     • Issue:
       • Onboarding/getting access to a DID registry is usually DID-registry-specific.
     • Proposals:
       • Consider the most frequent flows:
         • Redirect to a webpage (authentication or other operations are performed outside the wallet)
         • Authentication via API (some existing Universal Registrar drivers support this)
       • Proposal should work for most DID methods (e.g., did:web, Sovrin, sidetree)
       • A more detailed compatibility analysis is required
     • Outcomes
       • Proposals will be further analysed and discussed in the Universal Registration call
       • Issues will be opened in the Universal Registration repository
6. Short discussion about DID key rotation/revocation
   • DID Key rotation/revocation and trust

Attendees

• Markus Sabadello
• Juan (DIF/Spruce)
• Samuel Smith
• Balázs Némethi
• Steve Todd
• Tom Jones
• Alen Horvat

Meeting - 10 May 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. New repository donations:
   • https://github.com/danubetech/uni-registrar-driver-did-web
   • https://github.com/danubetech/uni-registrar-driver-did-ion
   • https://github.com/peacekeeper/did-registration/
5. Special Topic Calls: #1
   • Will discuss and find appropriate times via Slack/email.
6. [Boris Mann, Brooklyn Zelenka, Jeff Griffiths] Overview of Fission proposed approach to DID resolve / discovery in signing up for an account / linking DIDs
   • Fission's entire account system is built around DIDs.
   • App publishing platform and SDK.
   • Giving every user an end-to-end encrypted data store, using IPFS heavily.
   • In the account system, people select a username in a Fission namespace (e.g. boris.fission.name). The human-readable identifier can be used to discover a DID (using https://datatracker.ietf.org/doc/draft-mayrhofer-did-dns/). A did:key is created for users. The Fission server also has a DID.
   • Are there privacy issues with using domain names as user identifiers?
   • How can the auth system accept "remote" DIDs, i.e. interoperate with other DID methods (e.g. did:ion)? The "remote" DID could then "control" the Fission-internal DID.
   • How can the auth system advertise to someone that they can enter a DID to connect to the system?
   • Considering Webfinger discovery based on email-like identifiers; want to avoid NASCAR problem.
   • OIDC SIOP work seems relevant (ongoing at OpenID Foundation).
   • IIW had a session about SIOP Chooser (see https://docs.google.com/presentation/d/1OaMecHecTUexv1skJZoYzJoHKYH8H03REFpFstLRjPg/). Tom Jones is one of the people leading this effort.
7. Other topics?

Attendees

• Markus Sabadello
• Alen Horvat
• Boris Mann
• Ezequiel
• Balázs Némethi
• Brooklyn Zelenka
• Charles E. Lehner
• Jeff Griffiths
• Jeremie Miller
• Juan (DIF/Spruce)
• Samuel Smith
• Tom Jones

Meeting - 3 May 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Continue with organizational topics in ID WG
   • New co-chair Alen Horvat
   • Discussed regular call schedule, work items, special topic calls
5. Discussion around persistence and versioning of JSON-LD contexts, and implications on Linked Data Signatures
6. Discussion around data structures and other topics in the CCG's Universal Wallet 2020 specification
7. Other topics?

Attendees

• Markus Sabadello
• Orie Steele (Transmute)
• Samuel Smith
• Alen Horvat
• Balázs Némethi
• Tom Jones

Meeting - 26 Apr 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Organizational topics in ID WG
   • Sam Smith will step down as co-chair
   • Alen Horvat proposed as new co-chair
   • If there are any other proposals for co-chairs, or questions/feedback from the WG, please ask in our Slack channel
   • Consider changing the schedule of future calls (e.g. bi-weekly regular calls, with Special Topic calls)
5. Report-out from IIW
   • SIOP Chooser: https://docs.google.com/presentation/d/1OaMecHecTUexv1skJZoYzJoHKYH8H03REFpFstLRjPg/
   • Universal Resolver Driver Policy Discussion: https://docs.google.com/document/d/1LFl38lcJc1keadiyVUC-Q1Nm5vqPp8XjZFifyKcx9hg/
   • DID resolution over DIDComm to a Universal Resolver: https://docs.google.com/document/d/178qwAlv2nnRRtm7UcKUoo4NWOrYa1q_DAoE1Lq5VqHc/
6. Discussion around .well-known and did:web
   • Dmitri is willing to give an update on latest developments
7. Other topics?

Attendees

• Markus Sabadello
• Dmitri Zagidulin
• Juan Caballero
• Samuel Smith
• Alen Horvat
• Balázs Némethi
• Tom Jones

Meeting - 19 Apr 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Markus, Bernhard, Niclas] Updates to Universal Resolver/Registrar configuration, and work on Helm charts:
   • https://github.com/decentralized-identity/charts
5. [Philip Feairheller, Sam Smith] KERI-based DID methods, and use of DID Resolution metadata
   • https://identity.foundation/keri/did_methods/

Attendees

• Markus Sabadello
• Tom Jones
• Juan Caballero
• Balázs Némethi
• Bernhard Fuchs
• Niclas Mietz (Spherity)
• Philip Feairheller
• Samuel Smith

Meeting - 12 Apr 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Breaking changes in DID Core JSON-LD context:
   • w3c/did-extensions#277
   • Strictly speaking, all UR DID method implementations are now broken.
   • Discussion around changing JSON-LD contexts, caching, versioning, hashlinks
   • UR could implement a "fixing layer" for a transitional period, and simultaneously try to motivate implementers to fix their drivers.
5. Universal Resolver policy questions about driver submission and maintenance
   • decentralized-identity/universal-resolver#186
   • UR currently supports several DID methods that are not in the DID spec registries.
   • Probably we should have stricter policies going forward (e.g. only accept drivers for DID methods in the W3C method registry)
   • We will work on a proposal and present to the group.
6. Other topics?

Attendees

• Markus Sabadello
• Samuel Smith
• Bernhard Fuchs
• Charles E. Lehner
• David Waite
• Juan (DIF)
• Philip Feairheller
• Tom Jones

Meeting - 05 Apr 2021 - (1400 ET) canceled

(Canceled due to Easter holidays)

Meeting - 29 Mar 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Review DID WG test suite: https://github.com/w3c/did-test-suite/
   • The repo has issues for each part of the DID Core spec. Some PRs exist already to implement the tests.
   • Overall structure of test suite will probably still change (location of input files, re-use of test code, etc.)
   • Discussion if implementers will simply submit their result data, or if the test suite will have a "dynamic" execution component that automatically tests implementations.
5. Other news from W3C DID WG.
   • Discussed timeline and what the current "CR" state means: https://docs.google.com/presentation/d/1nSLk3cwJ8CanDoMLsO_JS3-ltBEeM8HZVXSsAZbrIl4/
   • Discussed policies of DID Spec Registries from last few DID WG calls:
     • https://www.w3.org/2019/did-wg/Meetings/Minutes/2021-03-11-did-topic
     • https://www.w3.org/2019/did-wg/Meetings/Minutes/2021-03-16-did-topic
     • https://www.w3.org/2019/did-wg/Meetings/Minutes/2021-03-23-did
6. Other topics?

Attendees

• Markus Sabadello
• Juan Caballero
• Tom Jones
• Charles E. Lehner
• Balázs Némethi

Meeting - 22 Mar 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [JackT] Updates on "VerifiableCondition"
   • https://github.com/Gimly-Blockchain/verifiable-conditions
5. Other topics?

Attendees

• Markus Sabadello
• Jack Tanner
• Caspar Roelofs (Gimly)
• Charles E. Lehner
• Daniel McGrogan
• Jeremie Miller
• Tomj

Meeting - 15 Mar 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions

2. ID WG participation tracking

3. Agenda creation/review/prioritization

4. [DanielK, JonC] New DID method on the Solana blockchain

   • did:solid, but not related to Solid (Social Linked Data) project
   • Solana blockchain is cheap and fast (1000s of transactions per dollar, but data storage is not as cheap). There is "rent", which can be decreased but never increased.
   • Version 0.1, will still be changed/optimized
   • Simple CRUD approach to put DIDs on blockchain. Solana has the concept of an "account", that's what you pay rent for. It will serialize a document and store the byte array on chain.
   • Daniel+Jon have worked on a driver for both the Universal Resolver and Universal Registrar. An instance of the Universal Resolver is running at:
   • https://did.civic.com/
   • Some discussion around design of Universal Registrar, e.g. what are the inputs, who pays for the transactions, etc.
   • [CharlesEL] Spruce Systems has also worked on a DID method based on Solana, perhaps there is potential to collaborate.
   • Links:
     • https://identity-com.github.io/solid-did/did-method-spec.html
     • https://github.com/identity-com/solid-did
     • https://www.npmjs.com/package/@identity.com/solid-did-client

5. Other topics?

Attendees

• Markus Sabadello
• Daniel Kelleher
• Charles E. Lehner
• Jeremie Miller
• Jon Cinque
• Samuel Smith
• Tom Jones
• Orie Steele

Meeting - 08 Mar 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. [Jack] Continue discussion on multisig and delegation in DID methods:
   • https://docs.google.com/document/d/1hxEMQxfNuB6Elmd6V-9bEt0kZqSx-DULycn6CjOpMYs/
   • Discussion of the document, and how it applies to different DID methods
   • Discussion of advanced verification methods involving smart contracts, etc.

Attendees

• Markus Sabadello
• Caspar Roelofs
• Charles E. Lehner
• David Waite
• Jeremie Miller
• Joel Thorstensson
• Juan Caballero
• Samuel Smith
• Tom Jones

Meeting - 01 Mar 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Controller, verification methods, authorization in DID Core
   • See issues in DID Core: w3c/did-core#697, w3c/did-core#693, w3c/did-core#694, w3c/did-core#695
5. [Jack] Support for multisig and delegation in EOSIO
   • Presentation by Jack about EOS chain and larger EOSIO ecosystem
   • EOS has an "account" concept as an abstraction layer; the account identifier is not derived from a key
   • Detailed discussions about multi-sig verification methods and delegation methods
   • There is a difference between 1. making a DID method that internally uses these features, and 2. exposing this in a DID document in a method-independent way. On the call, there was consensus that the latter would be highly desirable.
   • Consensus that a new cryptosuite should be defined (as a work item in W3C CCG or DIF)
   • If possible, the blockchainAccountId property should be re-used.
6. Related topics in other DID methods
   • Besides EOS, this is also relevant to did:indy, Ripple, and KERI-based DID methods

Attendees

• Markus Sabadello
• Jack Tanner
• Orie Steele
• Caspar Roelofs
• Jeremie Miller
• Juan Caballero
• Michael Herman
• Samuel Smith
• Tom Jones

Meeting - 22 Feb 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Updates on progress on DID Core in W3C DID WG
   • Discussion around data model and representations, e.g. see: w3c/did-core#679, w3c/did-core#596, w3c/did-core#597

Attendees

• Markus Sabadello
• Samuel Smith
• Charles E. Lehner
• Dmitri Zagidulin
• Jack Tanner
• Juan Caballero
• Tom Jones

Meeting - 15 Feb 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. Dillo plugin for DID URLs
   • Can resolve DIDs inside a browser, using a local instance of DIDkit
   • Can use Universal Resolver as a fallback
   • Built-in DID resolution in browser is preferable to remote resolver service
5. Updates on Universal Resolver/Registrar
   • Working on a DIDComm interface for the Universal Resolver
   • Alternative to using HTTP interface
   • Chicken-and-egg problem (you first need to resolve DIDs to do DIDComm)
6. Discussion on human-readable names and DIDs
   • Existing specifications to link web addresses and domain names to DIDs: https://identity.foundation/specs/did-configuration/, https://datatracker.ietf.org/doc/draft-mayrhofer-did-dns/
   • Pet names (can they be stored in the Universal Wallet?)
   • Some DID methods may use human-readable identifiers
7. Discussion on use of multiple keys for controlling a DID
   • How can you express in a DID document that you want to use multiple keys to authenticate? Define a verification method that consists of multiple other verification methods?

Attendees

• Markus Sabadello
• Jack Tanner
• Juan Caballero
• Kaliya Identity Woman
• Samuel Smith
• Tom Jones
• Charles E. Lehner
• Oliver Terbu

Meeting - 08 Feb 2021 - (1400 ET) recording

Agenda

1. Welcome and introductions
2. ID WG participation tracking
3. Agenda creation/review/prioritization
4. News on Fuzzy Encryption:
   • Finished work on a C++ implementation
   • Build script that generates WASM, can be consumed by JS
   • When not in native C++ form, it needs a wrapper for input of random bytes
   • Library can encrypt secrets, can decrypt with different inputs; technically different from Shamir, but has similar properties
   • The encrypted secret can be a symmetric key seed
5. News on KERI:
   • KERI is about to become its own Working Group, charter has been approved
6. Guidance on specifying a new DID method
   • Interest in creating a new DID method for eos.io
   • eos.io has existing concepts of "accounts" that could be used as a basis for DIDs
   • How to write a DID method specification? (needs to define DID syntax, DID operations