ANNOUNCEMENT: The did:tdw  Task Force will not be convened at ToIP

We have decided **NOT** to convene the `did:tdw `Task Force at ToIP after all. We're working with folks at DIF and W3C and will be incubating the specification there.  The IP provisions at ToIP were a bit problematic and we are leaving open the possiblity of merging `did:web` and `did:tdw` into a single DID Method, so being at W3C makes the most sense.

Progress has been excellent on the spec and implementations.  We have more contributors even without a formal working group, and have an additional implementation in Go.  The full featured Python and TS implementations are still clocking in at about 1500 lines of code, with minimal dependencies, so we're pleased with that. New contributors, implementers and deployers are welcome!

For those interested, the latest spec is here: https://bcgov.github.io/trustdidweb/

The remainder of this content is obsolete, but retained for the time being for those that might be interested.

=====================================

This page is the charter of the Trust DID Web (did:tdw) DID Method Task Force (TDWTF). The Meeting Page has links to the meeting agenda and notes of ongoing meetings.

...

The "Trust DID Web" (or "Trusted Web, if you same it fast) is a web-based DID method that improves (or extends) did:web  by providing a verifiable history of authorized (optionally with multiple keys) DIDDoc updates, portability, and (optional) key pre-rotation support in a small, simple package with minimal dependencies. "did:tdw" has what we think are the important features of an easy to use DID Method. DID Controllers (owners) can easily publish the same DIDDoc content as a did:web and did:tdw together to enable an easy transition -- the "did:tdw" JSON Lines log file "did.jsonl" resides beside the did:web "did.json" file. We believe that "did:tdw", with its simplicity, and adequate "ledger-type" features (without a ledger), combined with the publishing simplicity of "did:web," has the potential to be the ultimate DID Method.

DID portability is based on the inclusion of a self-certifying identifier (SCID) -- a GUID that is a required component of the DID string that is derived from the DID's initial DIDDoc. A DID with the same SCID can be moved -- history and all -- to a new web location.

did:tdw includes two DID Core-compliant services for handling DID URL paths in the "expected" way for a web-based DID Method. Their compliance with the DID Core specification means that the techniques that can also be used with other DID Methods – although the simplicty of the semantics might be lost. Notably: 

...

The primary objective of this Task Force is to incubate the did:tdw DID Method Specification as a ToIP deliverable. The purpose of this deliverable to define an easy to use, better than did:web, web-based DID method, and to possibly submit the specification to an appropriate standards developing organization (SDO),

...

• Stephen Curran 
• John Jordan 
• Drummond Reed 
• Eric Scouten 
• Brian Richter 

Deliverables

1. The did:tdw DID Method Specification
2. The did:tdw Implementor's Guide (currently part of the specification)

3. An instance of the VID Appraisability Framework for the did:tdw method once the VID Appraisability Framework (being developed by the Trust Spanning Protocol Task Force) is ready.

...

The TDWTF meeting scheduled is still being established. Please see the ToIP Calendar for the exact meeting times and Zoom links.

...