Re: Propose vc-examples-registry work item.

> And rightfully so since the core DID spec  explicitly states that DID-stuff belongs on DLTs
>
I think you need to re-read the spec again, as that is clearly *NOT* the case.

Right in Section 1 (Introduction), the first note is very clear on the topic:

NOTE: DID methods can also be developed for identifiers registered in federated or centralized identity management systems. Indeed, all types of identifier systems can add support for DIDs. This creates an interoperability bridge between the worlds of centralized, federated, and decentralized identifiers.

> the DID-stuff aims to enable interaction (communication) with the entity identified by the DID
>
That’s also not something that I see mentioned anywhere in the DID spec.  Can you please quote a source?

Leonard

From: "Joosten, H.J.M. (Rieks)" <rieks.joosten@tno.nl>
Date: Wednesday, March 18, 2020 at 4:27 AM
To: "daniel.hardman@evernym.com" <daniel.hardman@evernym.com>, Leonard Rosenthol <lrosenth@adobe.com>
Cc: Orie Steele <orie@transmute.industries>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Subject: Re: Propose vc-examples-registry work item.

And rightfully so since the core DID spec  explicitly states that DID-stuff belongs on DLTs. Also, according to the same spec (see the abstract), the DID-stuff aims to enable interaction (communication) with the entity identified by the DID, which is quite different from schemas.

So why specify that you need a DID to refer to a schema if we can generalize this to a URI? Doing so does not exclude DIDs since they are a specialization of URIs so you can still use the examples.

Rieks
________________________________
Van: Daniel Hardman <daniel.hardman@evernym.com>
verzonden: woensdag 18 maart 2020 01:32
Aan: Leonard Rosenthol
Cc: Orie Steele; W3C Credentials CG (Public List)
Onderwerp: Re: Propose vc-examples-registry work item.

There is a clear bias there towards DIDs (and VC’s in general) that are based on ledgers of some fashion.

Touché. :-)

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.