Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Meeting Date

  • The TSWG holds plenary meetings once every four weeks on Tuesdays.
  • Two meetings are held each Wednesday to accommodate global time zones:
    • NA/EU Meeting: 08:00-09:00 PT / 15:00-16:00 UTC
    • APAC Meeting: 18:00-19:00 PT / 01:00-02:00 UTC
  • See the ToIP Calendar for all meeting dates, times and logistics, including Zoom links.

Zoom Meeting Link / Recording

(These links will be replaced with links to the recording of the meetings as soon as they are available)

Attendees

NA/EU:

APAC:

  • Add your name here

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:
1 minReminder - TSWG2 Mailing ListChairs

Reminder that the Technology Stack Working Group has a new mailing list. You need to join this as it involves the new charter that TSWG is operating under. You can do that here:

5 minGeneral announcementsAllUpdates from TSWG members of general interest to the group.
1 minReview of action items from the previous meetingChairs
15 minETSI Liaison DiscussionViky Manaila 

Viky will explain ETSI's role in setting standards for the European Digital Identity Wallets initiative, and the proposed liaison between ETSI and ToIP to facilitate ToIP providing relevant specifications to ETSI. 

See screenshots #1 - 11 below.

Judith Fleenor asked what we need to specify what standards or services ToIP can contribute.

Viky clarified that we just need to chose from the list in slide #11.

Drummond Reed asked where the Trust Spanning Protocol would fit. Viky thought it would primarily be #5.

Judith Fleenor suggested that Viky do a first draft of the proposed language.

We noted the conflict on the term "TSP" as eIDAS 2.0 uses that term for Trust Service Provider.

ACTION: Drummond Reed and Judith Fleenor 

15 minTask Force ReportsTF Leads

Technology Architecture TFWenjing Chu  Drummond Reed

Status on the three remaining primary tasks:

  • Use Cases: ready to insert into the Markdown doc
  • Glossary: tooling being prepared
  • Third generation ToIP stack diagram: work underway being led by John Phillips, with each WG and TF contributing their "view" and "detail" diagrams.

New work items:

  1. Move spec into Spec-Up format.
  2. Update wording in the ToIP Identifiers section to use VIDs.

Trust Registry TFAndor Antti Kettunen  Darrell O'Donnell

Trust Spanning Protocol TFDrummond Reed Wenjing Chu Sam Smith 

  • The current Working Draft should be ready to become the first Implementers Draft by early February.
  • At that point we anticipate another blog post and holding an Implementers Kickoff Meeting.

ACDC TF — Sam Smith Philip Feairheller 

Specification review continues, 84 open issues, 1 PR (smile)

AI & Metaverse (AIM) Technology TFWenjing Chu 

  • The major initiative for 2024 will be a paper on how to achieve trust and authenticity with AI
  • Proposing to use a ChatGPT-style AI for use over ToIP website, wiki and GitHub data.

Credential Exchange Protocols TFmathieu 

  • Task Force on pause - co-chairs meeting in January to decide next steps for the task force
  • 2023 Deliverables included:
    • Credential exchange protocol comparison criteria
    • Data collection for 4 credential issuance protocols, from experts, against the criteria (Issue Credential v2, OpenID4VCI, ISO 23220-3 and ACDC)
    • Credential issuance protocol comparison matrix (here)
  • If you want to learn more about the task force, we recommend reading the the October ToIP blog post

did:webs Task Force  Lance Byrd Philip Feairheller Markus Sabadello 

  • We have completed the initial 30 days of our public review. We will continue to extend the period until we've completed all of the updates. Currently the only major changes is a refactor of the spec to separate it into normative/informative statements and references.
  • The TF is also looking at how to make the did:webs method as simple as possible, i.e., by not having to implement the full KERI suite.

X.509 VID Task Force (X5VTF)Eric Scouten Wenjing Chu 

  • Contact has been made with the Microsoft developer of the did:x509 method specification. He is very willing to have us take that work forward (however he's not available to help work on it).
  • The next decision is about whether that is a good starting point.
  • The next step is to move it into Spec-Up.
5 minSpec Template Task Force ProposalKevin Griffin 

See the charter page here:
ZZZ - Proposal - Specification Template Task Force (STTF)  Kevin Griffin / EasyCLA updates Kevin Griffin 

ACTION: Drummond Reed to send out an email to the Technology Stack WG requesting a 7 day review of the proposed Specification Template Task Force (STTF).

5 minService Discovery Task Force ProposalDrummond Reed 

See the charter page prepared by Andor  here:

Service Discovery Task Force

This was just completed, so the proposal is to start a 7 day TSWG review.

ACTION: Drummond Reed to send out an email to the Technology Stack WG requesting a 7 day review of the proposed Service Discovery Task Force.

10 minVerifiable identifier ComplianceTim Bouma 

Review of https://github.com/dgc-cgn/CAS-Digital-Trade-Documentation/blob/main/scheme/objects/obj-verifiable-identifier.md

Tim explained his work on compliance assessment and how VIDs fit into it.


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

Screenshots/Diagrams (numbered for reference in notes above)

#1

#2

#3

#4

#5

#6

#7

#8

#9

#10

#11


Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels