Meeting Date & Time

Jul 14, 2022 This Task Force holds TWO meetings weekly on Thursdays at the following times (to cover global time zones):
- NA/EU 07:00-8:00 PT / 14:00-15:00 UTC
- APAC 18:00-19:00 PT / 01:00-02:00 UTC

Zoom Meeting Recordings

Attendees

NA/EU Meeting

@Drummond Reed
@Wenjing Chu
@Daniel Bachenheimer
@Neil Thomson
@Kevin Dean
@Tim Bouma
@Vikas Malhotra
@Judith Fleenor (Deactivated)
@Vladimir Simjanoski
@isaac henderson
@Mattia Zago
@sankarshan
@Vladimir Zubenko

APAC Meeting

@Drummond Reed
@Darrell O'Donnell
@Wenjing Chu
@Neil Thomson
@Sam Smith
@Vladimir Zubenko
@Judith Fleenor (Deactivated)
@Jo Spencer
@Dima Postnikov

Main Goals of this Meeting

1) Review updates to the ToIP Technology Architecture Specification Section 5: Example Use Cases, 2) Review new text and diagrams in Section 6: Reference Architecture Overview, 3) Plan how to complete the rest of the primary content this month.

Agenda Items and Notes (including all relevant links)

Time	Agenda Item	Lead	Notes
3 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: Dima works in the banking industry in Australia and specializes in identity schemes.
7 min	Announcements	All	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.
10 min	Review of previous action items	Chairs	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.
15 min	Section 5: Example Use Cases	@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 (Deactivated) 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".
15 mins	Section 6: Reference Architecture Overview	@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.
5 mins	Plan for progress the rest of the month	All	Suggestions for how to accelerate completion of the rest of the main sections of the spec this month in order to meet our deadline of the first Public Review Draft by Sept 8. ACTION: ALL MEMBERS to review sections 7 through 11 of the ToIP Technology Architecture Specification to add any comments or suggestions.
5 mins	Review decisions/action items Planning for next meeting	Chairs	The next meeting will focus on closing any remaining issues with section 6 and making as much progress on additional sections as possible.

Decisions

None

Action Items

ACTION: @Neil Thomson, @Darrell O'Donnell @Judith Fleenor (Deactivated) will coordinate with Ecosystem Foundry Working Group to create a separate Google doc for use cases. They will then: a) copy the content from our existing section 5 to that document so it can be worked on independently, b) add a separate column to the table for noting what distinguishes each use case, c) make sure it is handed off to the EFWG chairs. (Judith has already created the Google doc.)

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.

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

ACTION: ALL MEMBERS to review sections 7 through 11 of the ToIP Technology Architecture Specification to add any comments or suggestions.