I guess I'll be able to drop LDAP when LDID will be introduced.
Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
31–40 of 108 posts
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#32The only required property in a DID document is id, so that is the only statement guaranteed to be in a DID document.
DID is little more than list of defined names and their intended usage. It's not automatically bad, but it's just a skeleton without any meat. In some sense, DID is pre-emptive standard template. If new identity protocols write their standard to be convertible to DID, then they end up having systems that can interact (after some testing) if when their methods intersect.
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#33Earlier quoted context omitted.
Here's the link: https://www.microsoft.com/en-us/security/business/solutions/... I haven't used their implementation yet but Microsoft initiated the did:ion method. I guess they'll support it :-D In general, the idea with DID methods is that you can support many methods without too much effort - for example the Universal Resolver implements already a good bunch: https://dev.uniresolver.io/ However, pointing in the di…
Ok, I'll have to look more in-depth into the Microsoft link, they link to many more pages including a whitepaper. Regarding all the blockchain centric DID methods, would someone wanting to validate a DID (eg: did:thecoin:whatever_would_go_here), need to hold a copy of the blockchain? (in a scenario where one doesn't want to be dependent on a third party for blockchain interactions).
Depends on the implementation and the blockchain, but for many cases there are ways to make such resolutions provably correct, such that you don't have to hold the copy of blockchain and you don't have to trust that a third party did the resolution correctly.
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#34I was initially pretty hyped when I read the abstract for DIDs, bookmarked the spec and read it later. The "spec" is a bunch of buzzwords and vague generic "concepts". The DIDs themselves mean basically nothing, it's the "methods" that actually must have their own specification and actually "do something". Another feeling you can quickly get from DIDs is that they're blockchain centric. The entire concept is "jack of…
> The entire concept is "jack of all trades, master of none" is
The quote is “a jack of all trades is a master of none, but oftentimes better than a master of one.”
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#35I was initially pretty hyped when I read the abstract for DIDs, bookmarked the spec and read it later. The "spec" is a bunch of buzzwords and vague generic "concepts". The DIDs themselves mean basically nothing, it's the "methods" that actually must have their own specification and actually "do something". Another feeling you can quickly get from DIDs is that they're blockchain centric. The entire concept is "jack of…
Here is a spec for the `did:key` method: https://w3c-ccg.github.io/did-method-key/
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#36So I've just scanned over this stuff, maybe someone can fill in some gaps for me. There's a list of DID methods "in development" [1]. Is this the list of methods, or is there a centralized registry, or are these just "known" methods? If there's a centralized registry -- then this isn't really "decentralized" is it? On top of that there's a land-grab that's already begun for the method names, and isn't that going to k…
That's the list of methods; and yes, there is very much a land grab going on right now.
No, there's nothing stopping you making your own methods. But will anyone actually use it?
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#37This relies on public-key cryptography? If that is the case, then who is responsible for maintaining the private key? If that responsibility is with the user, then what happens if the user loses the private key? Does the user loses the identity as well? Is there a way to recover that?
web3auth offers such a service.
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#38I guess I'll be able to drop LDAP when LDID will be introduced.
You will even be able to drop "in" did:ldap: if you want.
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#39From the snail DID:
> Write out your DID document according to the data model in [DID-CORE]. Include properties from [DID-CORE], and any other metadata you deem suitable. You MAY type it out and print it onto your paper, you MAY hand write it in pen or pencil or crayon, you MAY use finger painting or cut out and glue small pieces of paper. Express yourself however you like. You SHOULD NOT use glitter or food.
Re: Decentralized Identifiers (DIDs) v1.0 Becomes a W3C Recommendation
#40Why not simply a uri with an uuid in it?
More flexibility.
The did:peer: method, for example, encodes the did document directly in its URI.