- From: Steve McCown <smccown@anonyome.com>
- Date: Mon, 24 Jun 2024 15:03:05 +0000
- To: Julien Fraichot <Julien.Fraichot@hyland.com>
- CC: W3C DID Working Group <public-did-wg@w3.org>
- Message-ID: <612DA5C4-68A1-4E6B-B82E-2C04C23A6396@anonyome.com>
For those wanting to get up to speed on did:tdw, Stephen Curran gave a couple of great presentations at the last IIW. See pages 43 and 142 IIW Proceedings (https://github.com/windley/IIW_homepage/blob/6b0308f951ce7bcd14efea3c53e553317d78d483/assets/proceedings/IIW38_Book_of_Proceedings.pdf?raw=true) Steve McCown On Jun 24, 2024, at 07:25, Julien Fraichot <Julien.Fraichot@hyland.com> wrote: You don't often get email from julien.fraichot@hyland.com<mailto:julien.fraichot@hyland.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi, At recent DICE in Zürich Stephen Curran presented the did:tdw spec. Trying to wrap my head around the differences with did:webs, it seems did:tdw borrows a lot of concepts from the latter. From what I’ve gathered so far, the main difference is that did:webs relies on KERI while did:tdw does not. Is that the only notable difference? I’m aware of the xkcd joke and the 196 did specs out there, so I’m trying to break down a sort of comparison table to facilitate decision making, at least between these 2 specs. Thanks -- Julien Fraichot Developer – Hyland Credentials ----------------------------------------- Please consider the environment before printing this e-mail ----------------------------------------- CONFIDENTIALITY NOTICE: This message and any attached documents may contain confidential information from Hyland Software, Inc. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for the delivery of this message to the intended recipient, the reader is hereby notified that any dissemination, distribution or copying of this message or of any attached documents, or the taking of any action or omission to take any action in reliance on the contents of this message or of any attached documents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail or telephone, at +1 (440) 788-5000, and delete the original message immediately. Thank you.
Received on Monday, 24 June 2024 15:03:22 UTC