Updates from TSWG members of general interest to the group.

• Special announcement of a webinar tomorrow highly relevant to the TSWG: Demystifying the EUDI Wallet Architecture Reference Framework (ARF). It runs tomorrow (Thursday 2 March) from 6-7:30AM PT / 15:00-16:30 CET. ToIP members Viky Manaila  and Andy Tobin (Gen) are two of the three speakers; ARF architect Peter Altmann from Sweden is the third. If you want to understand the ARF, come to this webinar. See screenshot #1 below.
• Jo Spencer mentioned that APAC Digital ID unconference (inspired by IIW) is happening in Bangkok. Eric Drury is there now.
• sankarshan: Links for later (don’t want to derail the conversation): [1] A new report around language on usability, accessibility, trustworthiness of digital platforms www.arewetogether.com [2] UIDAI has recently announced that a new AI/ML approach has been deployed to manage the concerns around biometrics/fingerprint spoofing. No additional technical details are available at the moment https://economictimes.indiatimes.com/news/india/uidai-rolls-out-new-security-mechanism-for-robust-fingerprint-based-aadhaar-authentication/articleshow/98291146.cms

Technology Architecture TF — Wenjing Chu  Drummond Reed

• Progress has all been in the background.
• Proposed goal would be to publish public review draft #2 by IIW (April 18-20)
• We may want to hold off on finalizing until any final feedback on requirements is received from Trust Registry TF or Trust Spanning Protocol TF.
• The three primary remaining tasks are:
  1. Glossary — Drummond intends to put in time on this in March
  2. Use cases — needs a volunteer to drive it to closure
  3. Revised conceptual diagram of the ToIP stack <== see topic below
• Likely a meeting will be called mid-March to handle issues and action items. 

APAC:

• Jo Spencer agreed that we need to get feedback from the work going on in the TRTF and TSPTF before going final.
• Darrell O'Donnell said that it would be best to get the maximum feedback from the TRTF and TSPTF first.

Trust Registry TF — Andor Antti Kettunen  Darrell O'Donnell

• Multitudes of discussions have been converging into understanding two pronged scope for TRTF:
  1. Trust Registry specification to cover key trust questions that can be answered via Ecosystem Governance -backed Trust Registry. 
  2. Contextual Trust Decision protocol, which is essentially a collection of Trust Tasks and partially features coming from the Trust spanning layer. It will try to create a mechanism to cover wider range of Trust questions and trust input sources than just Trust Registry.
• Decision has been to put work the contextual trust decision protocol on hold, until TSPTF is further along, as there is strong dependency and need to understand the input it provides.
• Currently working on Trust Registry Requirements. Once requirement gathering is finished, we can move on to proposal stage for TR spec.

APAC:

• Jo Spencer likes the separation of the TR V2 protocol, but that both will be needed over time.

Trust Spanning Protocol TF — Drummond Reed Daniel Hardman Wenjing Chu Sam Smith 

• 3 proposals already made, with a fourth published but not yet presented. Links to the Github Discussions for each:
  • Proposal #1: Sam Smith
  • Proposal #2: Daniel Hardman
  • Proposal #3: Wenjing Chu
  • Proposal #4: Michael Herman
• Expected to move into the consolidation stage in March.

APAC:

• Jo Spencer is not planning on a separate proposal.
• Darrell O'Donnell is seeing convergence, so that we're ready to move into the consolidation phase.
• Drummond Reed agrees.
• We also discussed how the TSP will put "pressure" on the Layer 1 support protocols.
• Darrell O'Donnell pointed out the importance of interop test suites in applying that "pressure". He hold a story about the geospatial industry and the many flavors of the standard. Even though all the vendors said they were compatible with each other, but finally a company created a test suite that the government required interoperability with. The ultimate result was Google Maps. That is the same pattern we're likely to see here.
• Darrell: "Here's how we win: when the Armed Forces (of various countries) put it in their specs."

ACDC TF — Sam Smith Philip Feairheller 

• Phil had an exciting announcement: GLEIF joined the W3C in order to influence the direction of the W3C Verifiable Credentials 2.0 Working Group. The Miami F2F meeting last week resulted in a decision that other non JSON-LD representations of verifiable credentials could be officially recognized as a W3C VC-compliant format.
  • The requirement is only that the representation can be converted in one direction into the VC Data Model (which is JSON-LD with @context). But the native non-JSON-LD representation does NOT need to use @context. 
  • The ACDC TF is now going to submit a work item to the W3C VC WG for ACDC credentials (where it will join JWTs and AnonCreds).
  • This should enable the full value of ACDC containers to the W3C VC family.
  • Markus Sabadello asked if the ACDC TF plans to define a rich transformation of ACDC credentials into JSON-LD, or a minimal one.
    • Sam and Phil said that all fields in the VCDM will be covered.
    • Phil said that it would be a very interesting to explore how to do a full rich transformation.
    • Markus agreed that it would be very helpful to have that full rich transformation.
    • Sam pointed out that they didn't have to do a two-way transformation.
• Sam reported that Provenant (where Daniel Hardman is CTO) is now issuing vLEIs using the ACDC format.

AI & Metaverse (AIM) Technology TF — Wenjing Chu Vikas Malhotra 

• Wenjing shared screenshot #3 below.
• The main work is falling into these areas:
  1. Summary of challenges.
  2. Blogs/white papers
  3. New principles.
  4. New recommendations.

Drummond Reed Neil Thomson 

It is time to make a dedicated push to build out the TSWG terms wiki. The goal is to have it fully population in April to be ready to use the Concepts and Terminology WG Terminology Engine V2 to produce glossaries needed for the ToIP Technology Architecture Specification V1.0 (and soon for the ToIP Trust Registry Protocol Specification and Trust Spanning Protocol Specification).

Proposal (Neil Thomson) : Set up a Terms "Discussion" under each of the TATF, TR and TSP GIT Repositories.

• Single GH Discussion post for additional terms for which no definition exists (yet) 
• Each term gets a discussion post (discuss in replies).

Neil Thomson created Term and Concept Discussions in each of these TFs:

• Tech Arch TF - Discussion #88
• Trust Registry TF — Discussion #79
• Trust Spanning Protocol TF — Discussion #29

ACTION ITEM: Drummond Reed and Neil Thomson to put together a video tutorial for how to use terms wikis.

One of the remaining action items for the ToIP Technology Architecture Specification V1.0 is a revised version of our conceptual diagram. On the Technology Stack, we need to revise our depiction of layers 1 and 2 — see screenshot #2 below. We also need to reconsider how/where we depict verifiable data registries/trust registries.

• Judith Fleenor volunteered to be part of the discussion.
• Wenjing Chu pointed out that there is a larger question that there are different views of the full conceptual picture. If it was just an endpoint system, it would be easier.
• Antti Kettunen acknowledged the importance of this conceptual diagram and how it communicates the bigger picture of how ToIP works. He too would like to volunteer for this work. He suggests we wait for a bit to see how the trust spanning protocol and trust registry protocols work out.
• Darrell O'Donnell shared a sketch of an overall way he is looking at the ToIP stack now in screenshot #4 below. This view emphasizes the role of verifiable data registries and trust registries as the "glue" between the Technology Stack and the Governance Stack.
  • Drummond Reed likes that approach.
• Wenjing Chu emphasized that any single view can only show one instance of the stack at a time. In actual operation, there are many different cooperating instances. So we need to compromise on how we can depict an overall conceptual picture.

ACTION: Drummond Reed to start a thread in the TATF Github Discussions to begin discussion of developing a third-generation version of the conceptual diagram of the ToIP stack that will be consistent with the ToIP Technology Architecture Specification V1.0.