This was a special call of the TSWG as requested in the Meeting Notes of the 2024-05-14 TSWG Plenary meeting. A full explanation of the topic of the call together with an excellent discussion of the issues is posted in this Github discussion thread in the tswg-did-method-webs-specification repo.

The GitHub discussion thread also includes this summary of the outcomes:

1. The Trust Spanning Protocol Task Force (TSPTF) has always been in agreement that the TSP must support different VID types. The question is what the "bar" should be for registering those VID types.
2. @wenjing make the point that security requirements are always relative to a context. Some contexts require high security/high assurance. Some do not. So it is reasonable that different VID types may have different capabilities to support different security/assurance contexts.
3. One conclusion on which there was complete consensus is that ToIP must produce a VID appraisability framework that enables adopters of the ToIP stack to have a full understanding of the security tradeoffs involved with any particular VID type.
4. It was also agreed that, instead of spinning up another task force, the VID appraisability framework should be a deliverable of the TSPTF because VID types (and VID type registration) is such a core component of the TSP specification.
5. Lastly, at the end of the call it was agreed that the proposed did:tdw Task Force should go forward because: a) it will be a place within ToIP that work can be done to determine if another VID type (in this case, a SCID-based DID method) can interoperate with other TSP VID types, and b) this TF will be able to contribute to the VID appraisability framework.

Drummond Reed also shared screenshot #1 on the call.