2023-07-19 TSWG Meeting Notes

Meeting Date

  • The TSWG currently holds plenary meetings once every four weeks on Wednesdays.Ā The 2023 meeting dates are Jan 4, Feb 1, Mar 1, Mar 29, Apr 26, May 24, Jun 21, Jul 19. There will be a summer break in July, and then a new schedule will be adopted starting in Sept (see the ACTIONS list at the end of this page).
  • Two meetings are held each Wednesday to accommodate global time zones:
    • NA/EU Meeting: 08:00-09:00 PT / 16:00-17:00 UTC
    • APAC Meeting: 18:00-19:00 PT / 02:00-03:00 UTC
  • See the ToIP Calendar for all meeting dates, times and logistics, including Zoom links.

Zoom Meeting Link / Recording

Attendees

NA/EU:

APAC:

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
3 min
  • Start recording
  • Welcome &Ā antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members ofĀ ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
  • New Members:
    • Marcus Ubani from Atala and Larissa.Health. They are building on Cardano.
5 minGeneral announcementsAll

Updates from TSWG members of general interest to the group:

  • Judith Fleenor provided a reminder that our speaker for today's All-Member Meeting is not available, so that's been rescheduled to August 16th.Ā 
2 minReview of action items from the previous meetingChairs

This was not completed yet. See the final agenda item below.

20 minTask Force ReportsTF Leads200

TechnologyĀ Architecture TF ā€” Wenjing Chu Ā Drummond Reed

The primary progress has been on the ToIP Glossary Workspace. Drummond said that it currently has ~200 terms, with only four currently still required definitions. The next steps are:

  • Complete the remaining TODO definitions.
  • Identify any other terms missing from final or draft ToIP specifications or white papers.
  • Identify any terms for which consensus on the distinguishing criteria is particularly important and assign those to the relevant WGs or TFs.
  • Consolidate all the definitions into our standard glossary format.
  • Ingest the glossary into our TEv2 (Terminology Engine v2) tooling when ready.

Trust Registry TF ā€” Andor Antti Kettunen Ā Darrell O'Donnell

  • 3 proposals were made and recorded.Ā 
    1. Andor presented on June 15. Focus was at DID Document level to allow for discovery and integration via "Profiles"
    2. mathieu presented on June 29. Introduced a "Trust Input Protocol" concept that covers a future generic protocol that the Trust Registry Protocol should fit under.
    3. Darrell O'Donnell presented on July 6. Focused on interaction with existing systems-of-record that fill the role of "trust registry" and standardizing that interaction. This was essentially a new version of the first-generation protocol.
  • The first meeting on consolidation of the proposals was last week.
  • Great progress was made on how the 3 proposals relateā€”see the next agenda item below.

Trust Spanning Protocol TF ā€” Drummond ReedĀ Wenjing Chu Sam SmithĀ 

  • We had a hiatus for vacations the first half of July.
  • We hope to arrive at a consolidated strawman by early August.
  • Our goal is a complete Working Draft (and implementation!) by IIW #37 (Oct 10-12).

ACDC TFĀ ā€”Ā Sam SmithĀ Philip FeairhellerĀ 

  • Phil said the TF is continuing to refine the ACDC spec sections covering graduated disclosure.
  • They have recently completed a digital authorization and signing POC in Europe.
  • Kevin Griffin reported that he is in the process of bringing into ToIP repos the full suite of specs listed on the ACDC TF charter page.
  • Kevin also updated that there is a new section of the proposed W3C Verifiable Credentials 2.0 specification called "Ecosystem References" that will reference other "digital credentials" such as ACDC.
  • Darrell O'Donnell noted that the W3C VCWG trying to own the term "verifiable credentials". Drummond Reed agrees that it is overreaching, especially given that their own definition of the term in the Terminology section of the W3C Verifiable Credentials Data Model 1.0 specification was generic to any digitally signed credential.
  • But there was a consensus that this is not a battle worth fighting as the market will ultimately dictate the use of the term "verifiable credential" anyway.

AI & Metaverse (AIM) Technology TF ā€” Wenjing ChuĀ 

  • Neil Thomson reported that the group is revisiting its charter given the steady growth of the space.

Credential Exchange Protocol TF - mathieuĀ 

  • Mathieu reported that the group is working to complete its analysis of four issuance protocols and four presentation protocols.
  • They have been spending the last few weeks developing criteria for evaluating the protocols.
  • They are taking a hiatus for the next two weeks, then planning to finish a first version by roughly the end of August.
10 minTrust Registry ProtocolĀ Darrell O'DonnellĀ 

Darrell presented an overview (see screenshot #1 below) of how the three protocol proposals relate.

This clarifies the scope of the Trust Registry Protocol (TRP) and the TIP ā€” see screenshots #2 and #3 below.

Darrell then showed screenshot #4 that explains how these three protocols relate.

Darrell also pointed out the key role of registrar as opposed to registry as shown in screenshot #5.

5 minCanonical Uses Cases for the ToIP StackDrummond ReedĀ 

See this Google doc: Canonical Uses Cases for the ToIP Stack. We presented this last month, but please provide feedback on these 25 use cases so they broadly representative of the many common trusted relationship management actions and trust tasks that the ToIP stack can be used for.

10 minsProposed New Task Force: did:websKevin GriffinĀ 

See the draft charter page for details about this new TF to draft a new DID method specification for a more secure version of did:web. The basic idea is summarized in a graphic from that page copied as screenshot #6 below.

There was a discussion about whether the self-certifying identifier embedded in the did:webs identifier should be restricted to be a "generic" AID or a KERI-specific AID.

Philip Feairheller said that the spec could be defined to support any AID, and the first implementation could be specified to use KERI AIDs.

Neil Thomson: "++1 AID as a (Requirements) Specification vs. implementation."

Stephen Curran said he favors the details provided by the KERI specifications.

ACTION: Drummond Reed will contact the proposers of the DID WebS Method Task Force to clarify the licensing listed in the charter.

ACTION: Drummond Reed to send an email to the TSWG mailing list notifying all TSWG members of a 7 day review period for the proposed DID WebS Method Task Force, followed by a 7 day email vote seeing if there are any objections.

5 minsRevised TSWG Plenary and Trust Spanning Protocol TF Meeting SchedulesDrummond ReedĀ 

For the first half of 2023, we have tried a four-week cycle of meetings for the Wednesday 8AM Pacific Time meeting slot: 3 Trust Spanning Protocol TF meetings followed by one TSWG Plenary meeting. It has proved to be very confusing. Thus we propose to simplify things by:

  • Holding Trust Spanning Protocol TF meetings every Wednesday (both NA/EU and APAC) in their current time slots.
  • Scheduling a monthly TSWG Plenary meeting in a different time slot.

In our last meeting, we decided we will move the monthly TSWG Plenary meeting to a new time slot and dedicate the current time slot to the Trust Spanning Protocol Task Force meetings. After a short discussion, we agreed that:

ACTION: Drummond Reed will: a) send an email to the TSWG mailing list proposing to move our TSWG Plenary meeting to every fourth Tuesday with two meeting slots: NA/EU at 08:00-09:00 PT / 15:00-16:00 UTC, and APAC at 18:00-19:00 PT / 02:00-03:00 UTC, b) coordinate with W3C VC WG co-chair Brent Zundel to schedule those meetings so they don't conflict with W3C VC WG special meetings that happen at that same time every two weeks.


  • Review decisions/action items
  • Planning for next meetingĀ 
Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1


#2


#3


#4


#5


#6


Decisions

  • None

Action Items

  • ACTION: Drummond Reed will: a) send an email to the TSWG mailing list proposing to move our TSWG Plenary meeting to every fourth Tuesday with two meeting slots: NA/EU at 08:00-09:00 PT / 15:00-16:00 UTC, and APAC at 18:00-19:00 PT / 02:00-03:00 UTC, b) coordinate with W3C VC WG co-chair Brent Zundel to schedule those meetings so they don't conflict with W3C VC WG special meetings that happen at that same time every two weeks.
  • ACTION: Drummond Reed will contact the proposers of the DID WebS Method Task Force to clarify the licensing listed in the charter.
  • ACTION: Drummond Reed to send an email to the TSWG mailing list notifying all TSWG members of a 7 day review period for the proposed DID WebS Method Task Force, followed by a 7 day email vote seeing if there are any objections.