2023-04-27 TRTF Meeting Notes

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:
30-40 minReview of previous action items

Review on Trust Registry -related topics from IIW.

  • Reviewing Andor's overview on IIW:
    https://docs.google.com/document/d/1dYbTi-qNnx-7fJQM1BCPJ2vn2KtDCcqA7YjFE6SU2uk/edit
  • 7 TR related sessions
  • Agreement on the need of TR's, but varying viewpoints and differences in maturity of thinking
  • Not all TR working groups are even naming themselves a trust registry. Similar goals and development points, but naming different.
  • Chat (mathieu ): "One comment from someone from GS1 was “why can’t we simply use VCs instead of a TR”"
  • Alex from Cheqd presented DID Resource linking.
  • Marine corps reputation system seemed interesting.
  • Michael Herman presented Web7.0 (also available here: https://youtu.be/214-aKNBCAU

Key takeaways regarding TR's:

10-15 minsTrust Registry demomathieu 

Demo on the trust registry work done by CIRA & Northern Block

[See screenshots below]


TR RequirementsChairs

The current requirements document is becoming a bit hard to follow. We're creating a more structured document to guide TR Requirements work. 

https://docs.google.com/document/d/1p8rapJlVQ09CGR6vLeadQq-_sj_icfWfcyTPJMjC18Y/edit

We discussed approaches and experiences in how should we use requirements statements (MUST, SHOULD, MAY).

Darrell O'Donnell

"A MUST will get done.
A SHOULD may get done.
A MAY will likely not get done."

Sam Curren 
"We might consider reducing the scope of our work to eliminate MAYs and SHOULDs."

Neil Thomson 

"If there are sub markets which has variations where SHOULDs become MUSTs, then that is a separate standard/mechanism/protocol

Mirrors the Trust Spanning Protocol approach - there is a base (root Musts), which can be built on, for variations."

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

Screenshots/Diagrams (numbered for reference in notes above)

#1 Northern Block's NB ORBIT platform (ACAPY-based)

#2 Example on how trust registry can be referenced


#3Trust reegistry entry


#4 DNS entries referencing DIDs



#5 Trust Decision helper dialog


#6 Trust Decision helper to verify issuer information from DNS as well.

#7 Records queried from both trust registry and DNS, gaining multi-source assurance




Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item