Wenjing Chu 

OWF GitHub repo: https://github.com/openwallet-foundation-labs/tsp

Discord: https://discord.gg/dCKN4cnu

Wenjing explained that the team is developing the architecture and exploring language bindings for Python, Javascript, and something for Android.

Darrell O'Donnell asked if there is an iOS binding, e.g., SWIFT. Wenjing said and SamS confirmed that iOS could use the native Rust libraries.

He said the code is working quite well within the project. They have also built a test harness for the protocol. To test intermediary systems, one has to use VMs or cloud nodes, so the project has set up some test intermediaries at tsp-test.org. 

Wenjing is proposed to hold a dedicated informational session for developers interested in the project to learn about the best ways to get involved or contribute.

Wenjing suggested that the Discord channel is a good place for anyone to engage in the open source work.

Eric Drury asked about what work would go on at OWF vs. here at ToIP. Wenjing and Drummond clarified that OWF is where work on that specific open source implementation will happen; all else about the protocol and spec will be here at ToIP, including any feedback about the specification.

Wenjing and Sam discussed testing interop between their independent implementations.

Wenjing also mentioned that several small trust task protocols are being developed. One is for verified timestamps. 

We discussed how to "get the word out" more broadly about TSP and this implementation project. Wenjing plans to do an protocol overview session, and then also a project orientation session. He also wants to start exploring integration with specific VID types including KERI AIDs.

Wenjing suggested two special meetings:

1. Introduction to the Trust Spanning Protocol
2. Introduction to the OWF TSP Project

Judith suggested that we do "a little bit of a roadshow" with these two sessions, e.g., do a guest meeting at DIF and at OWF. 

Wenjing suggested starting with a ToIP meeting that would cover both topics above. This meeting could also cover how TSP could work with different VID types. Such a meeting could also include folks from other DID method types. It could also explain how the TSP could work with other projects.

Judith asked if there should be a blog post about this meeting and the OWF project.

ACTION: Drummond Reed, Wenjing Chu, Sam Smith to circle with Judith Fleenor on doing a blog post.

Wenjing Chu Drummond Reed Daniel Bachenheimer Darrell O'Donnell 

Judith Fleenor 

Wenjing first noted that decentralized identity was THE major topic of this EIC, starting right from the opening keynote. 

Secondly he noted that, for EIC, this was the first year of looking at what AI means for digital identity. He was on four panels discussing the topic and how AI would affect the EUDI wallet and credentials.

Thirdly, he noted that most of the sessions were not very technical, however they did have some discussions about the TSP with a technical team from Germany. His sense was that, even though there is strong interest in decentralized identity and ToIP, the EU architects still tend to be drawn to conventional centralized/federated architectures. Their mode is still to try to figure out how to make the older systems work.

Darrell shared that he had a discussion with Sam Curren who reviewed the TSP Implementers Draft. SamC shared a few thoughts, including asking about whether the TSP could just use CBOR instead of CESR. He also suggested that most interactions were unidirectional, so that could make it easier. It could also make the data structures simpler.

Darrell said that Sam Curren's biggest issue was about the term "verifiable identifier". For him it was unclear what the spec specifically meant by that term. Sam Curren wanted to clarify whether a DID was a verifiable identifier or not.

Wenjing suggested that the spec could use wording that could clarify that issue.

ACTION: Darrell O'Donnell and Drummond Reed to work on improved language about verifiable identifiers (VIDs).