Page Comparison

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.

• Note on attendence:

  • USA in Thanksgiving. Happy Gobbling USA.

    

• New Members:

5 min

Review of previous action items

Chairs

15 mins

Issue/PR Review

https://docs.google.com/spreadsheets/d/1UTzCvFr8np652cnyt-WB3R3TjYjZdL0egw5wX5b5Pf0/edit?usp=sharing

10 mins

Previous TRTF Call Review

Andor Kesselman

2024-11-21 TRTF Meeting Notes

• Scope : What’s a problem for us vs. a problem for the ecosystem to figure out?

  • Desire for an implementers guide was requested.

• Interaction Pattern Documentation : Discussed as Supporting but informs spec. Non-normative.

Image Removed

Image Added

10 mins

TRQP Common Data Model Work 

Andor

Starting point: Common Data Model

Review and then follow up :

A. Crowdsource: What fundamental questions must be supported by the TRQP?

• https://gist.github.com/andorsk/3c1f1d869644d4d0c58f9cb3f78028b5

• FromDrummond Reed : It seems like we have two categories of queries: graph traversal queries (to get to the authoritative TR) and then authorization queries (once you have located the authoritative TR).

• What about “provide me a certificate I can use to verify a signature”? Is that an authorisation query?

• With OID federation,

  • Do we have a common root?

  • Are you authorized to issue attestations?

  • Do we share a governance framework that governs this authorization

  • Do we have a common ancestor?

  • Multiple small questions.

https://gist.github.com/andorsk/3c1f1d869644d4d0c58f9cb3f78028b5

• From 11/21/2024

  • Abstract Data Model Formalization Introduce an abstract data model that serves as a foundation for formalizing implementations. This model will standardize core concepts and provide a consistent framework for compliant systems and variants. 

    • Needs a simple and clear way to traverse trust networks.

    • Tim Bouma Context. Represented by an identifier. Signature is applied to context. Tuple. 

    • Fabrice Rochette: @Drummond Reed agree, that’s why we should keep it simple, and maybe focus on authorization queries first.

    • Has Z granted Y to X. 

    • Drummond Reed: Context: Governance Framework. Authorization can expressed as an identifier in a way that other systems don't need to understand semantics.

    • Tim Bouma : Simplicity of the spec

Proposal: To answer A either must understand the following :

• Possible topological configurations of a network ensure the network interaction requirements are met by the common data model. I.e how do I resolve multi-chain vs. single chain.

• The type of data within a query context needed to properly resolve the networkor

  • Or we need to be able to reduce the scope of the solution to a specific section of a full interaction until we figure it out.

Content

https://gist.github.com/andorsk/3c1f1d869644d4d0c58f9cb3f78028b5

5 mins

• Review decisions/action items

• Planning for next meeting 

Chairs