2025-10-01 GATF Meeting Notes - Americas
This TF schedules meetings as needed. Each meeting will be announced on the GSWG mailing list and the #governance-architecture-tf Slack channel.
The meetings (and Zoom links) are available on the ToIP meeting calendar:
https://zoom-lfx.platform.linuxfoundation.org/meetings/ToIP?view=month
Zoom Meeting Links / Recordings
JP: I note that the LF Zoom account is now generating AI summaries of the recording. The one for this meeting is here:
https://zoom-lfx.platform.linuxfoundation.org/meeting/97801574874-1759359600000/summaries?password=409f8259-b1d0-43ec-a5a2-f69ff6079679
However this doesn’t seem to be quite as good as the one generated from the transcript and chat below. However it is automatic and that’s a (very) good thing.
Attendees
@John Phillips
@Drummond Reed
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
3 min |
| Chairs |
|
2 min | Review of previous action items | Chairs |
|
| Topic #1 |
|
|
| Topic #2 |
|
|
| Topic #3 |
|
|
| Topic #4 |
|
|
5 mins |
| Chairs |
|
Summary of meeting:
Summary of meeting generated by NoteBookLM from the transcript and chat messages.
The prompt used is “Using a professional but friendly style, create a minutes of the meeting based on the selected sources. Summarise the key discussion points made by the speakers and list any decisions and agreed actions. Make any references explicit by citing the time at which they occur.”
Minutes of Meeting
Date: 1 October 2025 Time: 23:02 UTC Attendees: Drummond Reed, John Phillips (Sezoo)
1.0 Purpose of Meeting
The primary purpose of the meeting was to discuss feedback on the Trust over IP (ToIP) diagrams, specifically concerning the direction of arrows, and to review the status of related projects, including the Global Trust Registry and the Trust Registry Query Protocol (TRQP).
2.0 Summary of Discussion
2.1 ToIP Diagram Feedback and Revisions The conversation began by addressing feedback from Michael Herman on LinkedIn regarding the direction of arrows in the ToIP "third generation" diagrams.
Initial Problem: The feedback questioned whether arrows labelled "uses" were pointing in the correct direction. John Phillips noted that according to standard systems diagram conventions, if "System B uses System A," the arrow should point from B to A, which would make the current ToIP diagram technically incorrect.
Mental Models: Mr Phillips explained that his original design was likely influenced by a "data flow" mental model rather than a "dependency" model. He noted that the diagrams were created to be easily understood during a presentation, not to adhere to a formal methodology. When presented with the accompanying narrative, audiences generally understood the concepts without scrutinising the arrow directions.
Proposed Solutions: Two potential solutions were discussed to address the feedback:
Change the text label from "uses" to "used by" and "learns from," which would make the existing arrow direction correct from a data flow perspective.
Reverse the direction of the arrows to align with the standard dependency model, which Mr Phillips referred to as the "Herman one".
Usability and Tooling: The importance of usability over rigid adherence to a specific format like UML was highlighted. The speakers agreed that the diagrams are most effective when built up sequentially to reduce cognitive load, as the final version can be overwhelming. They also discussed the practicalities of editing the diagrams in Google Slides, noting its collaborative benefits despite not being a specialised diagramming tool. A key discovery was that Google Slides allows exporting to SVG, ensuring high-resolution, scalable images.
2.2 Global Trust Registry and Related Protocols The discussion shifted to the Global Trust Registry project and its technical underpinnings .
Project Naming: Mr Phillips proposed a new name for the project: the Global Registrar Information Directory (GRID).
Query Protocols (TRQP): The need for a query protocol like TRQP was debated. While a machine-readable protocol is necessary for exploration, an alternative decentralised model was also considered. This alternative would involve the directory issuing credentials back to registrars, allowing relying parties to verify the entire chain of trust within a single information space. Both speakers agreed that these two approaches (a central query protocol and a decentralised credential-based system) could coexist as an "AND" solution rather than an "either/or" choice.
Standardisation Path: Drummond Reed confirmed that the ideal path for protocols like TRQP and the Trust Spanning Protocol (TSP) is to be standardised through an organisation like the Internet Engineering Task Force (IETF).
Funding and Sustainability: A critical point was made that for GRID to be successful, it must be self-sustaining, similar to the ICAO Public Key Directory (PKD) model. It should not rely on charity but on a clear value proposition that incentivises participants to contribute a relatively small fee for its operation. Funding will be required to build the system professionally.
2.3 Project Updates and Coordination The final part of the meeting covered project logistics and upcoming events.
ToIP Foundational Documents: Mr Reed mentioned an initiative to update five foundational ToIP documents before the November symposium. The third-generation diagram deck was considered complete, making this the perfect time to incorporate the discussed revisions.
Generative AI for Documentation: Mr Phillips demonstrated how Generative AI (specifically Gemini) can create "storybooks" to explain complex concepts, such as the Global Trust Registry. He suggested this could be a valuable tool for rewriting outdated documents like the "Introduction to ToIP" and for gaining a fresh perspective on existing materials.
Global Trust Registry Meetings: Mr Phillips shared links to the project's website and calendar. He explained that participation is open and pragmatic, not strictly limited by official UN-CEFACT expert registration, and that project materials are managed on Google Drive and a Google Calendar. The meetings are held bi-weekly .
3.0 Decisions and Actions
The following decisions were made and actions were agreed upon:
# | Action Item | Owner | Due Date | Status |
|---|---|---|---|---|
A1 | Update the ToIP "third generation" diagrams. This involves reversing the arrows for "uses" and "learns from" to align with standard dependency diagram conventions (the "Herman one"). | John Phillips | Before Nov Symposium | Agreed |
A2 | Propagate the updated diagrams through the relevant ToIP foundational documents, specifically the "explainer deck". | John Phillips / Drummond Reed | Before Nov Symposium | Agreed |
A3 | Inform the Discord community about the updates to the diagrams. | John Phillips | After A1 is complete | Agreed |
A4 | Share the link to the RFC about IETF time zones with Drummond Reed. | John Phillips | Post-meeting | Agreed |
A5 | Share information on "Flipping the Bozo Bit" by Steve McConnell from the book "Code Complete". | Drummond Reed | Post-meeting | Agreed |
A potential next step would be to create a brief for the team working on the ToIP foundational documents, outlining the specific changes to the diagrams and ensuring the narrative in the explainer deck is consistent with the updated visuals. This would ensure alignment ahead of the November symposium.
Chat notes
00:52:39 John Phillips (Sezoo): https://sites.google.com/sezoo.digital/globaltrustregistry/home
00:53:35 John Phillips (Sezoo): Project Calendar (with meeting date/times/details and past meeting minutes):
https://calendar.google.com/calendar/embed?src=c_0f1b7a519c6ffaa8e9e50417e3688e37f485a6af1792ab0fcd9141b50ba3366c%40group.calendar.google.com
Public address in iCal format: https://calendar.google.com/calendar/ical/c_0f1b7a519c6ffaa8e9e50417e3688e37f485a6af1792ab0fcd9141b50ba3366c%40group.calendar.google.com/public/basic.ics
00:58:43 Drummond Reed: Steve McConnell - Flipping the Bozo Bit
00:58:52 Drummond Reed: Software Construction