Meeting Date

  • The ToIP Trust Registry Task Force (TRTF) meets weekly twice every Thursday at the following times (to cover global time zones - see the Calendar of ToIP Meetings for full meeting info including Zoom links):
    • NA/EU 07:00-8:00 PT / 15:00-16:00 UTC 
    • APAC 18:00-19:00 PT / 02:00-03:00 UTC

Zoom Meeting Link / Recording

Attendees

NA/EU Meeting

APAC Meeting

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
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 minReview of previous action itemsChairs

Github Discussions Updates:

New Issues:

Updated Issues:

Action Items:

15 minsTiming And Phase DiscussionAndor Kesselman 

https://hackmd.io/opKrtCAfTrm2KV-cBorHZQ

Andor Kesselman proposed starting requirements gathering for the Trust Registry. Use of Trust Queries to scope the requirements for TR specifically.

Darrell O'Donnell noted that we need to understand what is done now and what should be the future work (i.e. affected by TSP work).

Tim Bouma we've understood the requirements, but haven't articulated it yet. We can start working on the methods and interactions. We should narrow our focus on the properties and attributes on the TR's and how it relates to governance etc. 

Neil Thomson (chat) Suggest that "Context" needs a lot of work from a terms defn and what are the factors/parameters/aspects included. I suspect that "Context" may "accumulated" as trust is established.

+1 to Andor - what is in a TR (and questions) and what questions are outside the scope of the TR (before or after in a trust chain/graph)

Drummond Reed IIW Option? April 18-20. Try to get something out by then. 

15 minsConcepts and Terminology Discussion and Updates

Neil Thomson feedback for next week. Ongoing effort. 


15 minsThinking Diagrams and BrainstormingTim Bouma 

https://github.com/trustoverip/tswg-trust-registry-tf/discussions/77

Tim Bouma presented thinking diagrams to simplify. Discussions on going on who controls the credential, holder binding, etc. There are uncertainties that we can model, and came up with a model to zero in on what we can solve. The basic part is the rule that is articulated. Rule is based on intention, acting according to authority, bound and governed by set of norms. These end up as actionable action.

What are the actions and what are the rules enabling that action. This is a framework understanding legitimization of the action that happens. I'm focusing efforts on Rules (i.e. Trust Registry)

https://github.com/trustoverip/tswg-trust-registry-tf/discussions/76


OAS Proposal

https://github.com/trustoverip/tswg-trust-registry-tf/discussions/61#discussioncomment-5075486


Andor Kesselman proposal on how to move from the proposal https://github.com/trustoverip/tswg-trust-registry-tf/pull/60 in to a deliverable: https://hackmd.io/uuVqrY6QTo29cci5cLIJMg

Savita Farooqui presented ToIP Governance Design plan, where use case is "Museum pass". Mapping the functional requirements to the API would help progress & aligning.

Darrell O'Donnell presented the object model below that describes TR queries & lookups. 

Savita Farooqui sees a lot of alignment with their functional requirements.

sankarshan (chat) How do we see an ecosystem GF arriving at a list of trusted wallets? Does it imply a certification and testing or merely self-registration and listing?

Darrell O'Donnell commented that it's part of wider accreditation consideration.

Scott Perry mentioned that ToIP can also rely on other accreditations. It depends on the risk & governance framework if it includes accrediation process.

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1


Decisions

  • Sample Decision Item

Action Items

  • Scoped work to focus on getting a Requirements Document Out. Work over a discussion. Provide a deliverable of a document. Exploration in parallel. 
  • Start thinking about how you would structure a proposal
  • Drummond Reed Neil Thomson feedback on concept and terminology next week. 


  • No labels