...
Judith Fleenor shared the Steering Committee Calendar changes due to holidays and notified the group that the November meeting it cancelled due to holidays, conference and travel scheduled. Additionally, it was announced that the December Steering Committee meeting Plenary will be help on December 7th at noon PT as a hour and a half meeting to discuss and finalize the ToIP Foundation 2023 Budget, with a secondary meeting scheduled for December 14th in the event that a decision is not made during the December 7th meeting.
All Member meetings were also canceled for the month of November and the December meeting has been pushed up to Wednesday December 14th at 10am PT. This will be a holiday celebration via zoom.
ToIP Interoperability Certification Framework
Judith Fleenor introduced the Avast team for the Avast Interoperability Certification Framework presentation.
Drummond Reed wanted to share a deep dive proposal for creating an Interoperability Certification Framework and kicked off the presentation. He shared the JDF charter for the ToIP Foundation that includes the following scope statement "The Purpose of the Trust over IP Foundation (alternatively, "ToIP Foundation") is to define and support a complete architecture and interoperability certification framework for Internet-scale digital trust that combines both cryptographic trust at the machine layer and human trust at the business, legal and social layers as defined in Hyperledger Aries RFC 0289 (or its successor as identified in the RFC document itself). As a point of reference to be clear about what that means for the ToIP Foundation. He shared that the work that they've been doing in the TSWG has provided them direction to illustrate the work that they're doing.
Proposed Strategic Objective
Drummond Reed mentioned that the work on the Technology Architecture Spec has helped to create a roadmap and the specific development tracks we are following to fully realize the ToIP stack. Additionally he shared the work they're doing to create a companion document called the Evolution of the ToIP Stack that illustrates the progress of each development track. Drummond Reed shared the newest roadmap diagram of the illustration that explains the ToIp ToIP Technology Architecture Specification. He went on to shared that Avast would liek to propose that the Steering Committee make it an explicit strategic objective of the Foundation to establish an interoperatnbility interoperability certification framework within two years. Drummond Reed and the Avast team would like to propose achieving this goal within two years of publishing the V1 ToIp Technology Architecture Specification. Open standards experts within Avast believe the planning and development of such a framework–designed to test commercial-grade implementations at scale–is a two year project.
Allan Thomson shared that there's a significant effort to achieve interoperability certification frameworks that can talk to other things. He believe that we need to 1. Help advance the necessary component specifications at all four layers. 2. as a Foundation will need to develop a ToIP Interoperatibiltuy Certification Framework against which third parties can perform certification of implementation and use cases. a. This framework will identity roles/Persona/Profiles of technology and how they may certify software acting as that persona. 3. one or more ToIp members will need to produce at least one Technology that matches at least one ToIP Interoperability Profile.
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 on.
- 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
...