...
- Agenda Review (1 min)
- Announcements and New Business (5 min)
- Upcoming Meeting Dates Review (2 min)
- Guest Speaker:
- Allan Thompson Thomson - Avast
- Charles Walton - Avast
- Drummond Reed - Avast
- Open Discussion
...
| Item | Lead | Notes | |
| 1 min | Agenda Review | Judith Fleenor | |
| 5 min | Announcements and New Business | ||
2 min | Upcoming Meeting Dates Review | Judith Fleenor | |
Guest Speaker:
| Allan Thomson Drummond Reed Charlie Walton | ||
| As Time Allows | Open Discussion | All |
...
- Presentation (Google Slides)
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
...
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
Open Discussion -
Actions:
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.
Allan Thomson shared additional details regarding the ToIP Interoperability Profiles and how critical it is to think about the entire ecosystem from a systematic perspective so that we can leverage profiles to demonstrate the roadmap for the user/vendor experience.
Drummond Reed shared the next steps if we're in agreement that we need to form a ToIP Interoperability Working Group. Charlie Walton believes that we're in a position to take a stance in this area to help drive the needs at a large scale. Avast believes this is key to their engagement with ToIP Foundation. Drummond Reed shared a final slide that details the creation of a new working group focused on interoperability. The proposition that ToIP members who are serious about this strategic objective start the journey by forming this WG. The goal would be to form this group in December and then start meeting on a monthly cadence in January 2023.
Open Discussion -
Dmitry shared that from a technology perspective that he's excited to help drive the initiative for the ToIP Foundation. He shared that this discussion is happening in other forums.
Scott Perry shared that he understands the value of certification in the marketplace. He believes that we may have a challenge as we're providing an architecture in technology and governance for the marketplace and we don't have alignment. He also shared that be disagrees with self-certification
Actions:
- Judith Fleenor to send out email to all SC members to listen to the recording and weigh in via email list
- Judith Fleenor to take a consensus poll before IIW.
- 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