| | | |
|---|
5 mins | • Welcome & antitrust notice • Introduction of new members • Agenda review • Recording with transcription is now automatic | Chairs | Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws.
ToIP Policy: Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
ToIP AIMWG IPR Policy: see WG wiki |
5 mins | • Introduction of new members • Any general announcements news that could be of interest to the WG • To review of action items that are not in the agenda below | All | • Any new members to introduce • Quick follow up of open action items (see below) |
5 mins | Schedule for next few weeks | | Next week - April 30. Overlaps with IIW. Recommend we cancel: Agreed to CANCEL. May 7: Continue on #Duties May 14: Continue on #TEA Spec May 21: @Eric Drury May 28: Continue on #Duties. @Steve Vitka June 4: I am back - #TEA Spec
|
45 mins | Standing Topic Series: #TEA Specification | @Wenjing Chu | @Wenjing Chu Review progress on TEA spec - proposal on a generic trust task of verifiable proposals and agreements @Wenjing Chu Proposal to use ACDC as container over TSP, and design a generic Exchange Protocol - discussed and agreed - it addresses both authorization and accountability in a symmetric protocol. Agreed on the approach - will proceed with detailed spec sections. This defines a generic protocol which can be instantiated by many use cases/context and patterns. This spec defines the generic protocol and if necessary some core patterns but most are for other specs to instantiate. Call for instantiations or examples (in English or spec) of use patterns of the protocol.
@Drummond Reed volunteered to propose DTG trust tasks as such instantiations. Work on strong DID or other IDs are complimentary to us. We do not define new VIDs. Work at DIF - delegated authority and governance are also complimentary in the capabilities being discussed. Although DIDComm and TSP are not compatible, and we are building on top of TSP as the foundational layer. Comparison - postponed to next/future #TEA meeting
|
0 mins | Other 2026 Priorities (still open for leads to substantiate these topics) | Initiative Leads | • Continue to refine/organize other priorities in this 2026 spreadsheet: https://docs.google.com/spreadsheets/d/1GorGyPHWGJ5T00WnmLZ8bHGUF0dhCGn5MxwyJsxrb5s/edit?gid=0#gid=0 |
0 mins | Action Items to Follow Up | All | • AIMWG in Google Drive is still under Tech Stack WFG - needed to elevate AIM to WG level • Move from Confluence to GitHub - Why? What does it take? How? On Why: it will make AI agent use a lot easier.
Topic 3: Disclosure, retention, re-purpose of personal data. Let’s discuss these privacy related features and see how the current proposed architecture would support. Others ------- if we have more time Topic 2: SOUL.md, AGENT.md, CLAUDE.md, and discussion thread on informal data Topic 4: How TEA relates to DTG, MCP-I, VerifEye, MCP, A2A, … maybe compile into a FAQ Other priorities - dormant now but we don’t want to lose them
|