Re: Verifiable Data Registries

Yes, Leonard, I agree. The definition I'm trying to provide of a VDR for
the DID spec is indeed relative to the DID spec, and I will include a
reference to the definition of a VDR in the VC spec to clarify that it may
involve other uses beyond those required by DID methods.

=Drummond

On Sun, May 31, 2020 at 9:36 AM Leonard Rosenthol <lrosenth@adobe.com>
wrote:

> > The short answer is that a VDR can be any system for which: a) a
> developer wants to develop and publish a DID method, and b) verifiers will
> trust as a cryptographic root of trust for the DIDs or other verifiable
> data rooted there.
>
>
>
> That definition is strictly in the context of DID though, right
> Drummond?   As noted since the VDR term is also in the VC Data Model spec,
> it also applies to all sorts of uses that don’t involve DID at all, would
> you agree?
>
>
>
> Leonard
>
>
>
> *From: *Drummond Reed <drummond.reed@evernym.com>
> *Reply-To: *"drummond.reed@evernym.com" <drummond.reed@evernym.com>
> *Date: *Saturday, May 30, 2020 at 6:11 PM
> *To: *MXS Insights <mxsinsights@gmail.com>
> *Cc: *Credentials Community Group <public-credentials@w3.org>
> *Subject: *Re: Verifiable Data Registries
> *Resent-From: *<public-credentials@w3.org>
> *Resent-Date: *Saturday, May 30, 2020 at 6:09 PM
>
>
>
> On Fri, May 29, 2020 at 10:30 AM MXS Insights <mxsinsights@gmail.com>
> wrote:
>
> I’ve been going through the recent DID's Editor’s Draft and a question
> came to mind on what the characteristics of a Verifiable Data Registry
> are.  So, I started looking through the VC spec and Data Model and find
> similar language across all the different spec’s, data models,...
>
>
>
> A role a system might perform by mediating the creation and verification
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fvc-data-model%2F%23dfn-verify&data=02%7C01%7Clrosenth%40adobe.com%7C7ec05c6e0ed14a3cae5b08d804e661e2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637264734826824812&sdata=DKlrDO98SP2xcbGNeHWt69CWWQaNamAOLLtU%2FqFKrrA%3D&reserved=0>
> of identifiers, keys, and other relevant data, such as verifiable
> credential
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fvc-data-model%2F%23dfn-verifiable-credentials&data=02%7C01%7Clrosenth%40adobe.com%7C7ec05c6e0ed14a3cae5b08d804e661e2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637264734826834765&sdata=6MkKVMKACslIRoEe8943VOkGFjOzMeSPQUA9q%2FNYSCg%3D&reserved=0>
> schemas, revocation registries, issuer public keys, and so on, which might
> be required to use verifiable credentials
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fvc-data-model%2F%23dfn-verifiable-credentials&data=02%7C01%7Clrosenth%40adobe.com%7C7ec05c6e0ed14a3cae5b08d804e661e2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637264734826834765&sdata=6MkKVMKACslIRoEe8943VOkGFjOzMeSPQUA9q%2FNYSCg%3D&reserved=0>.
> Some configurations might require correlatable identifiers for subjects
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fvc-data-model%2F%23dfn-subjects&data=02%7C01%7Clrosenth%40adobe.com%7C7ec05c6e0ed14a3cae5b08d804e661e2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637264734826844721&sdata=oPe7%2Bw1Auchhhwu2te4mZDy06lfiH92yIa5Y%2FVKpovk%3D&reserved=0>.
> Example verifiable data registries include trusted databases, decentralized
> databases, government ID databases, and distributed ledgers. Often there is
> more than one type of verifiable data registry utilized in an ecosystem.
>
>
>
>
> From: VC Data Model
>
>
>
> The question that came to mind, is there a more definitive definition of
> what a Verifiable Data Registry is?  What characteristics must it have?
> Usually, i have been equating it to a DLT, but I know that I have heard
> conversations indicating that it specifically was not restricted to this
> technology.
>
>
>
> Michael, a verifiable data registry is definitely not limited to being a
> DLT. I am currently working on a definition of the term for section 2
> (Terminology) of the DID spec, since we made decision to switch from *DID
> Registry* (which has always been a very confusing term in the context of
> DIDs) to *Verifiable Data Registry* so that we are in fact using the same
> term as was used in the Verifiable Credentials Data Model 1.0 spec.
>
>
>
> The short answer is that a VDR can be any system for which: a) a developer
> wants to develop and publish a DID method, and b) verifiers will trust as a
> cryptographic root of trust for the DIDs or other verifiable data rooted
> there.
>
>
>
> It's that simple. Literally any system can serve as a VDR, including P2P
> networks that have nothing to do with DLTs or databases at all.
>
>
>
> =Drummond
>
>
>
>
>
> Cheers!
>
>
>
> Michael Shea.
>
>