...
Allan Thomson he shared a diagram that illustrates the necessity for a Component Specifications Track that is essential. He shared that the advancing component specifications is critical to help identify which component specs will be mature enough when it not entirely in our control. ToIp members and our community as a whole can push to finish enough component specs to create at least onone full-stack interoperability profile.
- Layer 1 DID registry specs (both tech and governance)
- Layer 2 wallet/agent specs (especially EU & Canada)
- Layer 2 trust spanning protocol specs (DIDComm et al)
- Layer 3 credential exchange specs (Aries, OIDC4VC, ISO)
- Layer 4 UI/UX specs (FIDO, Secure QR codes, etc.)
Developing a ToIP Interoperability Certification Framework
Allan Thomson believes that just delivering a document for interoperability is not enough in the market. He believes we have two options to achieve success. 1. Self-certification with published results/verification/reviews (similar to STIXPreferred, Wifi Alliance) 2. Certification lab funding or partner that agrees to act as certification lab based on TICF. We need to define roles/personas/profiles that fit into relevant use cases for interoperability. He went on to share that depending on which option is chosen, define what additional resources, review boards, and infrastructure must be setup to support certifications.
Open Discussion -
Actions:
- Judith Fleenor to connect Daniel Bachenheimer with Jim St.Clair on the GHP page updates for the website.
- Elisa Trevino to get the new membership agreement to reflect the new working group and remove the ISWG and IWG-GHP from our charter
- Judith Fleenor to make the Avast discussion the topic for October meeting & 2023 Budget
- Drummond Reed and Judith Fleenor to fill Darrell O'Donnell in on the topic