Updates of general interest to TATF members.

• Ecosystem Foundry WG is going to be publishing Canonical Use Cases for ToIP — a set of 3 or 4 use cases, described in depth, that all other ToIP deliverables can reference.
• EFWG has also requested that when we are done with the ToIP Technology Architecture Specification, we produce a ToIP Tech for Muggles presentation (see KERI for Muggles and ACDC for Muggles as examples).
• The Governance Stack WG is preparing to launch a Governance Architecture Task Force (GATF) in September once the ToIP Technology Architecture Specification is ready. The GATF will focus on creating templates for each governance framework component that a particular digital trust ecosystem needs to implement (issuers, verifiers, trust registries, etc.)
• Neil Thomson said the terms wiki work is moving along.
• Vikas Malhotra said that the U.S. CISA has started work on a "software bill of materials" and that there is a connection with our work. https://www.cisa.gov/sbom

APAC

• Sam Smith shared that the ACDC Task Force completed an end-to-end demo of using ACDC credentials for GLEIF vLEIs. They will be doing a demo at the next ACDC meeting.
  
  • The new key management features will be discussed in the KERI meeting the following week.

• ACTION: Drummond Reed to implement the editorial revisions and restructuring reflected in the decisions above.
• ACTION: Wenjing Chu will add an additional bullet point to the Motivations section regarding "minimal design", "simplicity", or "spanning layers".
• ACTION: Vladimir Zubenko to add a use case about educational credentials to the table in section 5.
• ACTION: Darrell O'Donnell to revisit the use case table and propose a different set of use cases (Neil Thomson suggests a maximum of 12 that are as different as possible).
• ACTION: Wenjing Chu, Drummond Reed and Darrell O'Donnell to either close or move to GitHub as many issues as possible before next week's meeting.

• • Wenjing Chu said several issues existing issues can be closed, so all the comments addressing those areas can be closed.
  • ACTION: Drummond Reed mark the first four sections in the Google doc as frozen. DONE.

Darrell O'Donnell

Vladimir Zubenko  

Discussion of progress on the working draft of the ToIP Technology Architecture Specification:

• Google Doc version 
• GitHub Markdown version
• GitHub issues list

See use case action items above.

APAC:

• Darrell O'Donnell shared that we need a set of example use cases showing the full breadth of the stack.
• Sam Smith proposed that the "data supply use case" can be mapped to many other VC use cases.
• Wenjing Chu suggests that the use case descriptions should NOT use any use case terms.
• Vladimir Zubenko felt that what Sam described was a "super use case" that can be instantiated in many others.
• Neil Thomson felt that use cases that show the core concepts are most helpful. He suggests that we create a separate Use Case document that collects contributions from all ToIP WGs and members.
  • Such a document can go into much more analysis. 
  • Those use cases can be used by other groups.
  • Those use cases can be input to the Ecosystem Foundry WG for their Canonical Use Cases for ToIP document.
• Wenjing suggested we need to be able to use use cases to test the stack.

ACTION: Neil Thomson, Darrell O'Donnell  Judith Fleenor will coordinate with Ecosystem Foundry Working Group to create a separate Google doc for use cases and use that for discussion of different options with a table that adds a separate column for distinguishing that use case. (Judith has already created the Google doc.)

• First pass on ToIP Use Cases - see post in Slack (tswg-tech-arch-tf)

ACTION: Sam Smith to propose his meta use case on "data supply chain".

Wenjing Chu Drummond Reed

See proposed new text and open issues in section 6.

ACTION: Drummond Reed and Wenjing Chu to reflect the feedback from today's call on section 6 of the ToIP Technology Architecture Specification as soon as feasible.