•  ACTION: Drummond Reed to work with Wenjing Chu to finish the remaining formatting and editing tasks on the ToIP Technology Architecture Specification Public Review Draft 02 and then send an email by Friday 06 Sept to the full ToIP mailing list requesting a 7 day review period.

Not done, move to February

•  ACTION: When all reviews are finished, Drummond Reed to produce a PDF of the final version of the ToIP Technology Architecture Specification Public Review Draft 02 for posting on the website.

Not done, move to February

•  ACTION: Drummond Reed to check with Wenjing Chu about having the next blog post about the Trust Spanning Protocol ready for posting prior to Sept 16.

Not done, move to February

•  ACTION: Drummond Reed to reach out to Karen from Certizen to join the HAVTF and/orhave other Certizen X.509 experts join.

Carry forward

•  ACTION: Drummond Reed to update the TSWG home page with the following notification language about the patent exclusion requirement:
  NOTICE: In addition to the licensing terms of this Working Group’s JDF charter, this Working Group operates under the official policy that any Working Group Participant who makes a contribution to a Draft Deliverable shall have a maximum of 45 days from the date of that contribution to exclude any Essential Claims pertaining to that contribution.
•  ACTION: Drummond Reed to check if Alex Tweeddale wishes to be a Steward Council nominee.
•  ACTION: Drummond Reed to update this spreadsheet of 2025 meeting times to reflect TSWG meetings happening the first Tuesday of the month, beginning Tue Jan 7th, with two meetings one at 8AM PT / 16:00 UTC and one at 6PM PT / 02:00 UTC. 
•  ACTION: Drummond Reed to add the question of a secondary repo management person to the agenda for the first meeting in January, and also to contact LFDT staff about helping.

Partially done. Hart Montgomery gave me the contact info and now we need to follow through. Here are the two contact addresses:

• Ry Jones: rjones@linuxfoundation.org
• The LFDT community architects alias: community-architects@lfdecentralizedtrust.org

Is any TSWG member willing to volunteer to follow up on this repo management action item?

ACTION: Drummond Reed to talk to Hart Montgomery on Thursday to arrange repo management support. Jeff Braswell is willing to help. Jo Spencer is also willing to be contributor.

Technology Architecture TF — Wenjing Chu  Drummond Reed

• See the delayed action items above. The second public review draft of the ToIP Technology Architecture Specification is still pending some work by Drummond that he has not been able to get to (and likely cannot until later this month). Look for an update by our February plenary.

Trust Registry TF — Andor Antti Kettunen  Darrell O'Donnell

• Working hard on a second Implementers Draft.

Trust Spanning Protocol TF — Drummond Reed Wenjing Chu Sam Smith 

• Preparing to discuss the issues list to start working towards a second Implementers Draft.

AI & Metaverse (AIM) Technology TF — Wenjing Chu 

• Steven Milstein reported that the TF is wrapping up a blog post paper and starting to scope the work for 2025.
• Drummond said that the topic of personal AI agents is coming up everywhere. It feels like a perfect with the ToIP stack. 

High Assurance VIDs TF — Alex Tweeddale Jesse Carter Scott Perry mathieu Andre Kudra Drummond Reed

• Has adopted a bi-weekly meeting schedule alternating between NA/EU calls (new time: Thursdays at 10:00 PT / 18:00 UTC) and APAC calls (Thursdays 14:00 PT / 22:00 UTC).
• Is focused now on starting spec drafting of each trust bridge.

Chairs

See the Copy of 2024-11-15 Email to Technology Stack Working Group Mailing List (pasted in below these notes for easy reference). It explains the set of steps we need to take in today's meeting to move from the 2024 Technology Stack WG (TSWG-2) to the new 2025 Technology Stack WG (TSWG-3). We will need to approve the following set of motions:

DECISION #1: The Technology Stack Working Group officially closes the current Working Group and mailing list (referred to as TSWG-2) and agrees to contribute all outstanding deliverables (Working Drafts and Implementers Drafts) to the new Technology Stack WG (referred to as TSWG-3).

DECISION #2: The Technology Stack Working Group officially opens the new Working Group and mailing list (referred to as TSWG-3) that will operate under the IPR terms listed below and on the Technology Stack WG home page. There is no other change to the TSWG charter for TSWG-3.

• Copyright mode: Creative Commons Attribution 4.0. 

• Patent mode: W3C Mode (based on the W3C Patent Policy).

• Source code: Apache 2.0, available at http://www.apache.org/licenses/LICENSE-2.0.html.

DECISION #3: In addition to the new IPR terms now adopted, the Technology Stack WG adopts the following IPR policy and agrees to give this notice at the start of all TSWG meetings:

NOTICE: In addition to the licensing terms of this Working Group’s JDF charter, this Working Group operates under the official policy that any Working Group Participant who makes a contribution to a Draft Deliverable shall have a maximum of 45 days from the date of that contribution to exclude any Essential Claims pertaining to that contribution.

DECISION #4: The new Technology Stack WG (TSWG-3) is opened and agrees to accept the contributions from the previous Technology Stack WG (TSWG-2).

ACTION: Drummond Reed will inform Michelle Janata of these motions and approval of the new TSWG-3 and to prepare a new mailing list.

If there is time, let's discuss TSWG priorities for the New Year.

Drummond suggests that supporting the creation of an industry standard for personhood credentials should one of our priorities. 

Jo Spencer added that the challenges of being both pseudonymous (when needed) but still accountable is very important. He pointed out a new solution from New Zealand called ZKMe. Drummond agreed that "personhood" is now crossing over from Web3 to Web2 and the mainstream. Which is why it is such opportunity for ToIP in 2025.

Jeff is interested in the HAVTF and the concept of bridging between verifiable identifiers. He has been involved with matching identifiers in an LEI context, so was asking about how the HAV architecture works. Jeff explained that, with federated LEI issuers around the world, it was possible for a legal entity to obtain different LEIs from different LEI issuers, so they had to figure out how to detect duplicates. That matching process can be quite complex. Part of GLEIF's approach was to establish matching between LEIs and ISIN and BIC codes. The key to solving that was the the LEI reference data was always public.

Jeff pointed out that the problem is much more complex within an organization. 

Drummond suggested another priority for 2025: collaboration with DIF on two topics:

1. TSP and DIDComm alignment as a test case implementation for how to layer effectively.
2. Personhood credentials, particular with the opportunity for adoption by the Linux Foundation itself.

Rob Aaron agreed and said it would be ideal if both ToIP and DIF could agree on "one lane" for verified messaging.

APAC

Jo Spencer pointed out that the growth of AI agents will also push us more into both Organization ID and to IoT and device ID. And that this will be essential to supply chain, in which interest in trust solutions is growing quickly. It involves not just product passports, but the full provenance of who is making the assertions.