Meeting Date

02 May 2024 The GSWG meets bi-weekly on Thursdays at 11:00-12:00 PT / 19:00-20:00 UTC. Check the ToIP Calendar for meeting dates.

Zoom Meeting Link / Recording

Attendees

Main Goal of this Meeting

Bi-weekly Plenary reviewing Task Force updates.

Agenda Items and Notes (including all relevant links)

Time	Agenda Item	Lead	Notes
5 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:
5 min	Review of action items from the previous meetings	Chairs	(These are leftovers from previous meetings) Scott Perry - Will solicit interest in creating a Verifier Requirements Guide Judith Fleenor Follow-up on how to solicit feedback from the marketplace How is Spec-up going to fit into the average members' workflow, or do we continue with Google Docs Can we get Issuer Requirements Guide feedback from market Issuers'? Same for other docs in draft state and solicit feedback
5 min	Announcements	TF Lead	News or events of interest to Governance Stack WG members: Neil Thomson Attraction Pass will be going on hold Scott Perry : Original intent was to put together a use case to implement ToIP deliverables Has interest dropped off? Moved over to DIF Travel & Hospitality Judith Fleenor : DIF has been operating for 3 years Invitation to Sam Curran on DIF Trust Establishment work - proposed date Thurs May 16 in Gov Stack timeslot Defined base verifiable credential Look to catalogue components in an ecosystem Audit trail like Trust Chain, "delegated authority path" Drummond Reed :"DIF Trust Establishment is essentially “a trust registry in a file”." DIF option is Trust Establishment Bridge - contains a subset of the Trust Registry Bridge: Protocol to query the file https://trustoverip.slack.com/archives/C024WE961F1/p1714662752741779 Scott Perry : Metatdata for Trust Chain starting with the root of trust x509: Bridge: An intermediary step where an entity in a Trust Chain exists. May have more governance based on members participating. Example: University Bridge for all California universities Also the Credential Trust Establishment spec , which is a tool for capturing the above map (ecosystem relationships) Neil Thomson The ecosystem map version, using the Trust Establishment file as a template - is the Credential Trust Establishment spec https://github.com/decentralized-identity/credential-trust-establishment/blob/main/credential-trust-establishment/spec.md
10 min	Task Force Updates	Chairs	Drummond Reed Second-generation ToIP Governance Specs: overall proposal and timeline Terminology Tooling is nearly complete in Spec-Up HTML Link to each definition/version Generate version of glossary to GitHub Term per GitHub page Links to any referenced Spec-Up document with pop-up Ready for revisions Another generation of trust ecosystems will require glossary What other tooling and guidance is required Judith Fleenor Karla @ GLEIF has offered feedback Potential for C2PA Risk Assessment use Gather feedback as requirements for updates Scott Perry Promote use of ToIP tools ToIP Trust Canvas Guide Book A chapter per working group
20 min	IIW Updates		Scott Perry Governance Stack Model slides Drummond Reed IIW Highlights
10 min	Any other business		Judith Fleenor Content Authenticity Group? Using the risk assessment tools to assess Creator Assertions or C2PA to validate and update the tool as needed Try to get some of the people from those groups to participate
5 min	Review decisions/action items Planning for the next meeting

Meeting notes (using ChatGPT)

Verifier Requirements guide
Scott Perry discussed the potential need for verifier requirements, especially in the context of bridging between X.509 certificates and decentralized identifiers (DIDs). He mentioned the importance of feedback from the market and noted that the X.509 task force could potentially drive the development of verifier requirements. Action items included reviewing feedback on the issuer requirements guide and initiating work on the verifier requirements guide. Scott highlighted the need for additional resources to work on verifier activities.
Trust Establishment - DIF.
- The discussion revolved around a proposal by the DIF'sTrust Establishment regarding a credential map aimed at documenting relationships within an ecosystem, such as those between educational institutions and credential issuers. Here are more technical details of the discussion:
  - Credential Map Proposal: The proposal involves defining a standard format for a verifiable document, referred to as the "base verifiable document." This document would contain signed information, simplifying the process of verifying credentials within an ecosystem.
  - Purpose of the Proposal: The primary objective of the proposal is to establish a mechanism for cataloging relationships between entities within an ecosystem. For example, it could document the authority relationships within an educational institution's ecosystem, tracing from federal accreditation bodies down to individual certificates issued by the institution.
  - Metadata and Verifiability: The proposal emphasises the use of verifiable credentials and metadata to establish and trace relationships. Each entity's authority and relationships within the ecosystem would be documented in a signed, verifiable manner.
  - Trust Registries and Governance: There was discussion about how this proposal relates to trust registries and governance. While not explicitly labeled as a trust registry, the proposal shares similarities with the concept. It aims to provide a mechanism for capturing and storing trust-related information in a secure manner.
  - Trust Chaining and Roots of Trust: Questions were raised about whether this proposal could facilitate trust chaining and establish roots of trust within an ecosystem. Trust chaining involves establishing a chain of trust from one entity to another, while roots of trust represent authoritative sources within the ecosystem.
  - Clarification: Drummond Reed clarified that the proposal aligns with the concept of a trust registry. He shared a diagram illustrating how different sources of trust information could interact using a trust registry protocol. This protocol would enable various entities to access and share trust-related information effectively.
Update on Attraction Pass and its future direction
There is a concern the interest in Attraction Pass has waned and the discussion centred around the reasons for it and what needed to be done next. Here's a summary of the main points discussed:
- Original Intent: The original goal was to create a model or case study for implementing an Attraction Pass using techniques learned within the group.
- Lack of Interest: Interest in the project seems to have waned, possibly due to misunderstandings about the scope, expectations of software development, or other business priorities taking precedence.
- Proposal for Outreach: There's a suggestion to reach out to industry stakeholders to gauge interest in sponsoring the completion of the study.
- Shift in Focus: There's also discussion about potentially shifting focus to using Trust over IP tools for content authenticity rather than pursuing the Attraction Pass project further.
- Future action: There's a desire to either move forward with it by engaging with similar WGs in DIF or pivot to other initiatives.

Decisions
Action Items

Scott Perry Get & respond to feedback in Issure Requirements Guide
Scott Perry See if we can find other resources to provide input for Verifiers Requirements GuideExplore
Neil Thomson , Judith Fleenor , Scott Perry Explore Attraction Pass TF interest in continuing. ToIP is the only place to implement Governance
Judith Fleenor Ask Karla @GLEIF to provide ToIP tooling feedback, Content Authenticity. Create Risk Assessment Task Force for August?

2024-05-02 GSWG Meeting Notes

Zoom Meeting Link / Recording

Attendees

Agenda Items and Notes (including all relevant links)

Meeting notes (using ChatGPT)