/
2025-05-21 Steering Committee meeting

2025-05-21 Steering Committee meeting

Jul 09, 2025

Meeting Schedule

  • May 21, 2025

Agenda and notes

    1. ANNOUNCEMENT—Drummond has transitioned from Gen to an individual member (for the time being). He is now working full time on the First Person Project.
      1. Here is his LinkedIn post.
    2. UPDATE—Carly: EGWG has been posting blogs based on presentations generated by NotebookLM (with presentation permission). https://trustoverip.org/category/blog/
    3. ENDORSEMENT APPROVAL—Steve McCown: Should ToIP endorse the NoPhoneHome initiative?
      1. At IIW, I gave a presentation on how mDL can be used to track individuals due to the way it authenticates credentials.  Here's my presentation.
      2. Our findings have been getting some notable attention and have even caused AAMVA to make changes to the US mDL requirements, which were announced at EIC.
      3. We're trying to raise awareness to this type of identity tracking, which we're calling "Phone Home". To do that, we've put out a statement at https://nophonehome.com/ and are collecting signatures in support of eliminating "phone home" functionality in government identity systems.
      4. I’m proposing that ToIP (and LFDT) join the list of supporters to help increase individual privacy in government identity systems.
  • PROPOSED MOTION: The ToIP Steering Committee approves ToIP becoming an endorser to the NoPhoneHome statement at NoPhoneHome and sharing that endorsement with our members. 
        1. This motion was approved by consensus with one dissent from John Phillips, who commented, “I dissent, as I would like the wording changed. But I accept the majority decision (as a fan of democracy!)”
        2. John noted: “Here is the one of the instances of the deep research report I've been generating using Gemini 2.5: Gemini: Mobile Driving Licenses: Legislative Adoption of ISO 18013-5 and -7 and Safeguards for Server-Based Retrieval
    1. UPDATE—Drummond and Daniela: The dilemma of the ToIP 2024 Annual Report and the template we’re supposed to fill out that doesn’t remotely work for JDF projects.
      1. Daniela agreed. Wenjing suggested that we propose an alternative format for an annual report on a JDF project.
      2. Drummond noted that Arun S M, who is also on the LFDT TAC, responded to Drummond’s message on the ToIP Discord channel saying, “I would be happy to get this feedback to the TAC in the upcoming meeting.I will also do the preliminary analysis on what factors to consider, would appreciate your feedback.”
  • ACTION: Daniela, Wenjing, and David Boswell will coordinate with Arun on proposing a new template format for JDF projects and then filling it out for the ToIP 2024 Annual Report.
    1. UPDATE—Daniela: Any fue rther prep for the Global Digital Collaboration July 1-2 in Geneva?
      1. Daniela and Wenjing discussed the proposed sessions on the second day. Two sessions are scheduled for First Person Credentials. One is scheduled for blockchains.
      2. Daniela emphasized that these are not “pitch sessions”, but need multiple sponsors and organizers.
      3. Kim mentioned that ToIP is a co-organizer on several sessions, including one on AI and Agentic Identity. 
  • ACTION: All SC members should send any suggestions to Scott for ToIP topics who will then work with Wenjing to coordinate what we want to see included in GDC Day 2 sessions.
    1. CHARTER APPROVAL—Drummond: Is the SC ready to approve the charter for the Decentralized Trust Graph Working Group? See agenda item #7 from the last meeting and the proposed charter here.
  • MOTION: The Decentralized Trust Graph Working Group is approved by the ToIP Steering Committee.
      1. The motion passed by consensus.
    1. CHARTER APPROVAL—Wenjing proposes a charter for a new AI & Human Trust WG. See the proposed charter here.
  • MOTION: The AI & Human Trust Working Group is approved by the ToIP Steering Committee.
      1. The motion passed by consensus.
    1. DISCUSSION—Carly: What is our policy for organizations who display the ToIP logo?
      1. Example: https://keri.foundation/
      2. John shared that we developed a brand guideline document here.
      3. John also shared that this folder contains several ToIP post LFDT merger icon versions (several I note have been produced by Carly 🙂 )
      4. Daniela explained that LFDT has a policy covering this: https://www.lfdecentralizedtrust.org/trademarks-guidelines.
      5. If there are any potential issues, send email to trademark@lfdecentralizedtrust.org and there is a committee that will look into it.
      6. LFDT guidelines https://www.lfdecentralizedtrust.org/logos-guidelines and  https://www.lfdecentralizedtrust.org/trademarks-guidelines 
      7. Daniela’s feedback about the usage at the https://keri.foundation site was that it just needed to be updated.
  • ACTION: Carly to review the policies and the current logos and provide any feedback to Nicholas.
  • ACTION: Daniela will talk to Henk van Cann about the KERI Foundation becoming an Associate Member of LFDT.
    1. DISCUSSION—Drummond & Daniela: What is our policy for approving ToIP publications and deliverables?
      1. The basic process is defined in the JDF charter.
      2. What refinements, if any, do we want to make? See this page and this page on the ToIP wiki.
  • ACTION: Daniela will have the link to this Google doc added to our LFX calendar invite for this meeting so it will be available to all SC members (present and future). [[COMPLETED: look at June 18th and future]
    1. DISCUSSION: Prep for the ToIP Fifth Anniversary Showcase
      1. Carly suggests a start-to-finish set of use cases around issuing, holding, and presenting a VC that attests to conformance with a governance framework with a trust mark. She suggests the example of a farmer receiving a VC with a trust mark for meeting regenerative agriculture practices.
      2. Carly showed a set of slides about her proposed demonstration program. Selected snapshots are below.
      3. John remarked: In UNTP terms, a Trust Mark becomes a "Digital Conformity Credential" 
      4. This still leaves room (necessarily) for how/who/why a DCC (which we could think of as Trustmark) is released. So my suggestion is to build the work s Carly is describing, and publish the Trustmark as a UNTP DCC VC and hence leverage tie into the global initiative …
      5. There was excellent discussion. 
  • ACTION: Carly will prepare a script for the ToIP 5th Anniversary Showcase and post it on the ToIP wiki.
  • ACTION: Carly will publicize to all ToIP members the next EGWG meeting where the Showcase event and script will be discussed.
  • ACTION: Carly and the SC members will then communicate to all WG and TF chairs the action item that they should provide feedback on the script and contribute a summary of what they plan to present in their section of the script.


AI & Human Trust Working Group—Proposed Charter

The AI and Human Trust Working Group (AIM) is to focus on studies and recommendations that (1) apply ToIP solutions to enhance human trust in AI technologies, and (2) integrate AI technologies to better solve trust challenges in the context of human and AI interactions.The Working Group’s deliverables may include insight reports, position white papers, and specifications and recommendations. 

Example areas of work include but not limited to White papers about strengthening trust in human and AI interactions leveraging the Trust Spanning Protocol (TSP) and other components of the ToIP stack, Communication protocols between AI agents, and between AI agents and non-AI data resources, services, tools etc., Authenticity and provenance of content and data, Personhood and AI agent identities, Delegation, accountability, and control of AI agents, and How to build trust in AI Agents frameworks.

LINK to current TF: https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22982892/AI+huMan+trust+Task+Force

All IPR options will remain the same as the latest TSWG charter (i.e. W3C patent mode).