DID Documents as self-signed Verifiable Claims about vc-data-model HOT 6 CLOSED

From @msporny on July 17, 2017 1:10

It's exactly as @ChristopherA says, but keep in mind that our DDO implementation is going on 2+ years old at this point. Here's an example of a DDO for our current system:

https://demo.authorization.io/dids/did:2ba2d687-2f92-4c4a-aa45-e3e8a6ae38a1

We'll be revamping it over the next couple of months to align w/ the new DID spec. We expect to suggest changes to DDO objects.

To be clear, a DDO can be thought of as an Entity Profile (from Verifiable Claims). That is, it's a signed document that can contain a set of Credentials (which contain Verifiable Claims).

from vc-data-model.

@ChristopherA which repo should we move this to?

from vc-data-model.

From @ChristopherA on July 18, 2017 1:18

I our prototype, ddo fragment /0 is signed by the blockchain itself (in our case, bitcoin) which points to the next fragment (in our case, through the op_return), and the /1 is a self-signed claim that adds claims about the entity that issued the did. Fragment /1+ could contain more claims, either issued by the did issuer, or accepted from others about the did issuer that the issue accepts.

from vc-data-model.

Link to some of my other comments on this issue: #59 (comment)

from vc-data-model.

I think this issue is out of date (and should be closed). It's not clear it introduces any new/unknown requirements for Entity Profiles, which is the concept we were looking for when we opened the issue.

from vc-data-model.

I'm going to close this one out -- @kimdhamilton, if you prefer it reopened please do so.

from vc-data-model.