Skip to content

Latest commit

 

History

History
96 lines (78 loc) · 5.57 KB

agenda.md

File metadata and controls

96 lines (78 loc) · 5.57 KB

Trust DID Web Work Item Rolling Agenda

Zoom Link: https://us02web.zoom.us/j/83119969275?pwd=IZTuXgGLtdLPjPLuB6q8zHXazxHSsU.1

Agenda: HackMD, TrustDIDWeb Repository (synchronized after each meeting)

WG projects | DIF page | Mailing list and Wiki | Meeting recordings

Table of Contents

Meeting Information

Participants are encouraged to turn your video on. This is a good way to build rapport across the contributor community.

This document is live-edited DURING each call, and stable/authoritative copies live on our github repo under /agenda.md, link: Agenda.

Future Topics

  • Using the did:tdw log format with other DID Methods
  • Merging did:tdw features into did:web?
  • Implementor's experiences -- architectures, learnings
  • Trust DID Web Server -- implementations, such as this one, specification
  • A did:tdw test suite -- such as proposed here

Meeting - 12 Sept 2024

Time: 9:00 Pacific / 18:00 Central Europe

Meeting Recording: Zoom Recording

Attendees:

  • Stephen Curran
  • Dmitri Zagidulin
  • Cole Davis
  • Brian Richter
  • Andrew Whitehead
  • Sylvain Martel
  • Martina Kolpondinos
  • John Jordan
  • Patrick St. Louis
  1. Welcome and Adminstrivia
    1. Recording on?
    2. Please make sure you: join DIF, sign the WG Charter, and follow the DIF Code of Conduct. Questions? Please contact operations@identity.foundation.
    3. did:tdw Specification license -- W3C Mode
    4. Introductions and Agenda Topics
  2. Introduction to the did:tdw Work Item at DIF
    1. CCG Presentation on did:tdw (starts at the 5:40 mark of recording)
  3. Brief(!) introduction to did:tdw
  4. Discussion:
    1. What do you want this group to achieve?
    2. What would help you the most?
      1. Get to 1.0!
      2. Web server
      3. Next step topics -- witnesses, deactivation -- how does a diploma remain verifiable when the isssuer disappears -- with their web server. Aka durability.
      4. Acceptance of the method broadly.
      5. How did:tdw compares with KERI.
      6. Test suite!!!!! Implementation consistency.
      7. Cryptographic audit on the techniques used -- hashing use, etc.
      8. Governemnt acceptance of the cryptographic suites being used.
      9. Switchcord is running live use cases based on did:web -- would like to transition to did:tdw and its features.
  5. Feature list feedback document -- importance of features?
  6. Future Topics
  7. Next Meeting -- next week, same time
    1. Input to TPAC.
  8. Spec. PRs and Issues
  9. Action items and next steps:
    1. Stephen to create a PR to change the spec. to say that a version is an object, JSON Patch is no longer used, and that the Data Integrity Proof is across the version object, without a challenge.
    2. Everyone to look at the list of did:tdw features and comment on the features.
    3. Everyone to review issues and open others as needed, to drive future discussions.