Add Trust DID Web did:tdw DID Method to Registry

[swcurran]

Signed-off-by: Stephen Curran [email protected]

----- DID METHOD REGISTRATION FORM: DELETE EVERYTHING ABOVE THIS LINE ------

DID Method Registration

As a DID method registrant, I have ensured that my DID method registration complies with the following statements:

• The DID Method specification defines the DID Method Syntax.
• The DID Method specification defines the Create, Read, Update, and Deactivate DID Method Operations.
• The DID Method specification contains a Security Considerations section.
• The DID Method specification contains a Privacy Considerations section.
• The JSON file I am submitting has passed all automated validation tests below.
• The JSON file contains a contactEmail address [OPTIONAL].
• The JSON file contains a verifiableDataRegistry entry [OPTIONAL].

[mwherman2000]

I have a commercial objection to the approval of did:tdw.
"tdw" overlaps significantly with the Trusted Digital Web (TDW), the parent project of the Web 7.0 Ultraweb.

1. GitHub Reference

• https://github.com/mwherman2000/TrustedDigitalWeb
• https://github.com/mwherman2000/BlueToqueTools

1.1 Additional References

Partial List

• https://github.com/w3c/did-extensions/blob/main/methods%2Fmesh.json
• https://github.com/w3c/did-extensions/blob/main/methods%2Fobject.json

2. Prior Use of "tdw" and "Trusted Digital Web"

Dating back to 2018

2.1 Trusted Digital Web whitepaper

The oldest reference to the "Trusted Digital Web" appears to be from a whitepaper published by Michael Herman in conjunction with the November 7-8, 2019 Malta Blockchain Summit¹. This whitepaper outlines the concept of a universal, trusted, frictionless, integrated, standards-based platform for global commerce, communication, and collaboration¹.

Source: Conversation with Copilot, 11/7/2024

(1) TRUSTED DIGITAL WEB: WHITEPAPER - ResearchGate. https://www.researchgate.net/profile/Michael-Herman-4/publication/348558565_TRUSTED_DIGITAL_WEB_WHITEPAPER_THE_FUTURE_OF_THE_INTERNET_AND_THE_WORLD_WIDE_WEB_A_SOLUTION_FOR_A_WORLD_STEEPED_IN_FUNDAMENTAL_DISTRUST/links/60046b5a299bf14088a2cbc8/TRUSTED-DIGITAL-WEB-WHITEPAPER-THE-FUTURE-OF-THE-INTERNET-AND-THE-WORLD-WIDE-WEB-A-SOLUTION-FOR-A-WORLD-STEEPED-IN-FUNDAMENTAL-DISTRUST.pdf.
(2) How Digital Trust Varies Around the World - Harvard Business Review. https://hbr.org/2021/02/how-digital-trust-varies-around-the-world.
(3) Michael Herman (Web 7.0 Ultraweb) mwherman2000 - GitHub. https://github.com/mwherman2000.
(4) undefined. https://maltablockchainsummit.com/.

NOTE: "tdw" appears 13 times in the 2019 version of the Trusted Digital Web white paper.

2.2 Hyperonomy Digital Identity Lab Blog (TDW Blog)

• References dating back to 2018:
  https://hyperonomy.com/?s=Trusted+Digital+Web+
• TDW: https://hyperonomy.com/category/tdw/
• Conversation with @swcurran : https://hyperonomy.com/2021/07/26/bootstrapping-a-vdr-based-decentralized-credential-object-platform-von-example/

Examples (dating back to 2018):

• https://hyperonomy.com/wp-content/uploads/2018/12/Trusted-Digital-Web-v0.2.png
• https://hyperonomy.com/2018/12/31/the-trusted-digital-web/
• https://hyperonomy.com/2019/01/10/did-comprehensive-architecture-reference-model-arm/
• https://hyperonomy.com/2019/01/13/hyperledger-indy-sovrin-comprehensive-architecture-reference-model-arm/
• https://hyperonomy.com/2019/11/06/trusted-digital-web-whitepaper/
• https://hyperonomy.com/2019/12/03/trusted-digital-web-first-trusted-web-page-delivered-today-dec-3-2019/

2.3 Trusted Digital Web (TDW) YouTube playlist

Television interviews, international keynote presentations, and worldwide videocasts beginning in 2019

• https://youtube.com/playlist?list=PLU-rWqHm5p45dzXF2LJZjuNVJrOUR6DaD&si=yJjZDF_vn-MaH3Cp

2.4 W3C pubic-credentials mailing list

First reference: 2019

• https://www.w3.org/Search/Mail/Public/search?subject=Trusted+Digital+Web+&lists=public-credentials&resultsperpage=100&sortby=date-asc

2.5 Hyperledger email archives

From 2019 referencing a TDW blog post from 2018:

2.6 Twitter/X Archives

From 2019 referencing TDW whitepaper from 2018

• https://x.com/search?q=%22Trusted%20Digital%20Web%22&t=6nP8a-AxCIVprkMavZUaWQ&s=09

2.7 Domain Name System (DNS) Registries

Partial List

• trusteddigitalweb.com registered October 2019: https://ca.godaddy.com/whois/results.aspx?itc=dlp_domain_whois&domain=Trusteddigitalweb.com

2.8 Internet Identity Workshop proceedings

• IIW 34 Spring 2022: https://github.com/windley/IIW_homepage/blob/f34a48da50bc9f5b8d97b3c655e2a2b91d681d56/assets/proceedings-iiw/iiw-34-book-of-proceedings-xxxiv-spring-2022.pdf?raw=true/

2.9 DICE proceedings

• DICE 2023 Zurich https://github.com/windley/IIW_homepage/blob/f34a48da50bc9f5b8d97b3c655e2a2b91d681d56/assets/proceedings-dice/dice-book-of-proceedings-zurich-2023.pdf?raw=true/

2.10 LinkedIn references

• Michael Herman (Trusted Digital Web): http://linkedin.com/in/mwherman
• "trusted digital web": https://www.linkedin.com/search/results/all/?keywords=%22trusted%20digital%20web%22&origin=HISTORY&sid=jM4

2.11 Medium references

• Michael Herman (Trusted Digital Web) https://medium.com/@mwherman2000

3. Prior Use of did:tdw

• Using Paper-Based Structured Credentials to Humanize Verifiable Credentials [Rough Cut] https://youtu.be/kM30pd3w8qE?si=EUp0LQC10K0xOwa9

4. Legal References

• The Differences between Unregistered and Registered Trademarks in Canada,
  https://www.heerlaw.com/differences-unregistered-registered-trademarks

[swcurran]

It was definitely not our intention to create any confusion. While I am well aware of @mwherman2000’s work in this area. The association I have with that is work is “Hyperonomy” and “Web 7.0". I’m not aware of the use of the “Trusted Digital Web" term in the context of that work — and definitely not the acronym, nor any confusion it would have with what we are working on — a trusted version of did:web.

In the specification and all presentations explained why we chose it — nothing to do with @mwherman2000’s work.

We did check the DID Method Registry prior to choosing the name to verify it was not taken. AFAIK, the DID Method Registry uses a first come, first serve namespace process, and while @mwherman2000 has a number of DID Methods Registered, he did not register did:tdw, and with this PR, we have done so.

At this point, the term did:tdw (as opposed to the pure TDW acronym) is well-known in the community as being the specification for the DID method that we have been working on and talking about. I’m sorry the topic did not come up earlier, but given the reputation we have established with the term (references to did:tdw are common, including in a recent RFI from the Government of Canada), we’d prefer not to change it now.

[mwherman2000]

This issue specifically relates to the W3C being complicit if this PR is approved. Comments such as being used in a government RFI or that you have no recollection are irrelevant to the issue at hand.
Beyond this, the infringement extends to the use of the term "Trust DID Web" - an obvious collision with the long established use of the original term "Trusted Digital Web" which dates back to 2018.

[mwherman2000]

did:webby is a suggested alternative method name.

[mwherman2000]

Legal References

From: #586 (comment)

The Differences between Unregistered and Registered Trademarks in Canada,
https://www.heerlaw.com/differences-unregistered-registered-trademarks

[peacekeeper]

While I am well aware of @mwherman2000’s work in this area. The association I have with that is work is “Hyperonomy” and “Web 7.0". I’m not aware of the use of the “Trusted Digital Web" term in the context of that work

This has been my perception as well, I don't remember having heard of a project called "Trusted Digital Web" before. Also, "Trust DID Web and "Trusted Digital Web" are clearly not the same, and besides, to me "Trusted Digital Web" sounds like a generic term rather than a trademark.

[davidlehn]

Possibly related:

• How to handle duplicates #569
• Consider allowing multiple registrations by the same "name" in a given category #304

This is the only request for did:tdw at the moment, so there is no conflict to resolve yet.

[mwherman2000]

This issue specifically relates to the W3C being complicit [in the infringement] if this PR is approved.

Reminder: This issue is very specific ...and I believe/suggest it should be considered via W3C's legal processes.

[brianorwhatever]

did:tdw (Trust DID Web) is an entirely different name and is completely unrelated to Trusted Digital Web (TDW). There is no conflict here.

[msporny]

@mwherman2000 wrote:

This issue specifically relates to the W3C being complicit if this PR is approved.

To be clear, the list of extensions (and DID Methods) is NOT authoritative (yes, we know some of that text needs to be updated in the current document) and is maintained by a group of volunteers that have no connection with W3C, Inc. The W3C VCWG does have authority over the list, but again, they do not represent W3C. Asserting that W3C, Inc. has anything to do with this list is not a correct interpretation of the relationship between W3C, Inc. and the management and operation of this list.

A few things to consider:

• There has been a notion that we allow the registration of duplicates to avoid this issue, and then let the market decide which one developers implement and use.
• I have performed a search for "TDW" in both the Canadian and US trademark databases and there is no such registration for this class of usage.
• All references that @mwherman2000 provided do not attempt to claim the unregistered trademark (by placing "(tm)") or any variation thereof in the initial paper or the subsequent discussion of the topic beside the "TDW" acronym. There seems to have been no attempt to protect the acronym since its inception, even as an unregistered trademark, until this point.
• There don't seem to have been any uses of the "TDW" acronym in commerce and proving damages in this case would be exceedingly dicey.
• The phrases "Trusted Digital Web" and "Trust DID Web" are, arguably, different enough as to not cause confusion -- but then, the finality of that opinion would be for an arduous legal process to decide.

As one of the reviewers, I see no issue with registering this DID Method. The burden of proof of trademark ownership, registered or not, has not been met.

That said, due to the nature of the objection, we will have to discuss this in the DID WG to determine what path the group will want to take. We will hold off the merging of this DID Method until that discussion happens. After that discussion happens, we'll report next steps here.

[mwherman2000]

Related Discussions

• Withdrawal of did:idc by IBM: Add idc method #402 (comment)
• did:keri Update to the correct location of the did:keri specification. #395 (comment)

[mwherman2000]

• Who is or should be considered to be the spokesperson for the other party/this application?
• Which person or organization is or should considered to be the "owner" of the other DID method specification/this application?
  #DIF?
  @kimdhamilton, your thoughts?

[peacekeeper]

DIF?

The did:tdw method is currently a work item of the Identifiers&Discovery WG at DIF. It was approved after @swcurran proposed and presented it multiple times in August/September this year, and no concerns or objections were raised against this new work item. @mwherman2000 if I remember correctly, you are also a member of that same DIF WG.

[mwherman2000]

@peacekeeper Thank you. For several reasons including jumpstarting the Web 7.0 Foundation, I haven't been active in or monitoring any of the SDOs or their working groups (with exception of the DID Methods registry). There's no requirement to do so.

August/September was only a couple months ago. I posted my objection in a timely manner after this PR was created.

Who is the best person from DIF to address this matter? I've reached out to @swcurran but have not heard back yet.

[kimdhamilton]

• Who is or should be considered to be the spokesperson for the other party/this application?
• Which person or organization is or should considered to be the "owner" of the other DID method specification/this application?
  #DIF?
  @kimdhamilton, your thoughts?

Hi @mwherman2000, sorry, I'm just seeing this. My thoughts on what?

[mwherman2000]

@kimdhamilton Who is the best person from DIF to address this matter (did:tdw infringement)?
I've reached out to @swcurran but have not heard back yet.
See @peacekeeper 's remarks above.

[kimdhamilton]

Thanks Michael. Yes, @peacekeeper is correct that Trust DID Web is a work item in the Identifiers & Discovery Working Group.

Update: I am discussing with Michael directly this week

[mwherman2000]

#FYHumor guard your soup kettles...interesting metaphor

[mwherman2000]

A couple people from the community have mentioned having no recollection of the prior use of Trusted Digital Web (a statement that is not actually relevant to the infringement). That being said, I invite community members to verify 2 things:

1. Search your email history (particularly your CCG emails) for Trusted Digital Web. You will likely find dozens if not hundreds of emails from "Michael Herman (Trusted Digital Web)".

2. Specifically wrt to DIF, the Trusted Digital Web project submitted the following WG proposal to the DIF Steering Committee: https://docs.google.com/document/d/1YEOQLVVSwhvIHkAELHVISufzyDjJqLLx/edit?usp=sharing&ouid=114156804688997110176&rtpof=true&sd=true

I don't know if I made it known at the time: this proposal was a litmus test for donating the entire TDW/Web 7.0 project to DIF. In the end, I went the route of incorporating the Web 7.0 Foundation.

3. Section 6 of the LF Member Charter requires all Contributors to own the exclusive copyright on any contributions they make. One of the implications is that you can't contribute another organization's material unless you have expressed permission to do so.

[brianorwhatever]

Specifically wrt to DIF, the Trusted Digital Web project submitted the following WG proposal to the DIF Steering Committee: https://docs.google.com/document/d/1YEOQLVVSwhvIHkAELHVISufzyDjJqLLx/edit?usp=sharing&ouid=114156804688997110176&rtpof=true&sd=true

This document doesn't mention "TDW", "Trusted" or anything involved in this conversation so not sure how it's relevant.

Section 6 of the LF Member Charter requires all Contributors to own the exclusive copyright on any contributions they make. One of the implications is that you can't contribute another organization's material unless you have expressed permission to do so.

Unclear how this is relevant as nobody is contributing another organization's material and to claim they are is quite disingenuous. To be clear the only conflict in conversation here is a naming collision between "did:tdw" and Trusted Digital Web (TDW). None of the work is related other than the fact that they are both related to decentralized identity and share an acronym.. but then again so does this 100 year old pipeline construction company, this Auto shop, this offshore vessel support company and I'm sure many other things..

[TallTed]

fwiw, the string TDW occurs in a number of places on the web. Here's a Google search which results include multiple pages answering "what does this acronym stand for?". So far as I can tell, none of these include "Trusted" in any expansion. I see no justification to block this requested registration of did:tds (typo) did:tdw.

[mwherman2000]

... registration of did:tds

1. @TallTed Nobody is trying to block the registration of did:tds

googling

2. @brianorwhatever @TallTed There's little value to googling for "TDW" or any other trademark. Trademark protection doesn't work that way. It's pointless; perhaps even a Code of Conduct violation: making claims that are false, threatening, and/or intimidating.

[swcurran]

A note here. We are going to change the name of this DID Method -- its just not worth the hassle. However, I'm keeping this PR open to prevent someone else from putting in another "did:tdw" method. That would actually create confusion.

I hope no one would do that.

[TallTed]

@mwherman2000

1. @TallTed Nobody is trying to block the registration of did:tds

did:tds was a typo. did:tdw was intended.

[mccown]

@swcurran a name change is probably the simplest path. I'm looking forward to the relaunch.

All:
I'm not sure how to resolve future naming issues like this. First to register, maybe? There are only so many 3-letter names to be had and there are already a lot of current collisions and reuses that are usually ignored. For example, there's another github project called ThreeDWorld that also uses the name "TDW". Given the current landscape, I'm skeptical that asserting a trademark on short letter names is feasible these days.

Back in 2001, there was an ACM article describing the DNS naming & trademark collisions. It's worth a read to recall that mess, so we can avoid it here.

The Collision of Trademarks, Domain Names, and due Process in Cyberspace

[mwherman2000]

@mccown I postulated a possible solution here: #590 ...as well as a super/meta solution here: #597

[mwherman2000]

However, I'm keeping this PR open to prevent someone else from putting in another "did:tdw" method. That would actually create confusion.

This would still amount to a form of infringement (in addition to being a possible Code of Conduct violation).

[w3cbot]

This was discussed during the #did meeting on 21 November 2024.