Understand the opportunity to create a governance framework for dual-stack interoperability.
Agenda Items and Notes (including all relevant links)
Time
Agenda Item
Lead
Notes
5 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:
5 mins
Review of action items from previous meeting
Chairs
5 mins
Announcements
TF Leads
News or events of interest to Governance Stack WG members:
Driven by insights gained in completing the Technical Architecture specification last year but getting very little feedback from others including governance who have a completely different viewpoint
Trust registries are not represented in the current diagram and there is no good way to fit it in the stack, we need a good alternative diagram.
Earlier stack diagram with the governance first/left and technology on the right/second (see Fig. 1) hasn't really worked.
Trust Registries & DID Utilities: need to depict these correctly as these are supporting systems for every layer.
Visions for 3rd generation diagram - canonical examples
Fig.2 is from Darrell O'Donnell who suggested 'Trust Registry' and 'Governance Architecture' to span all layers. Trust Registries will provide 'governed information' for helping make trust decisions on any layer of the stack.
Dennis Landi liked it while Anita Rao indicated she had a hard time mapping some of information to the previous 4 layer diagrams. Savita Farooqui pointed out for her 'applications = business level applications' and wallet was a tool. Mary Lacity on chat highlighted that trust registries were only on one stack. Neil Thomson felt the diagram mixed components and processes Carly Huitema on chat "I agree with Neil - one diagram only needs to do a lot of lifting. The original diagram was a great message and easy to show and makes entry to the 'world of ToIP' simple. But when it comes time to start making decisions and design, you need other types of diagrams to guide." Kyle Robinson agreed with Carla and felt this diagram can be an interactive and inform audiences at different levels. Daniel Bachenheimer on chat "I think the diagram is fine for capturing our point in time discussion but too much disparate info... we should not attack OPERATIONS at this point, for example" Brent Zundel on chat "I will appreciate the hourglass translation on the left-hand side, this makes sense to me now. But I would have difficulty translating this to second generation stack"