Decentralized ID - Revision history

Tom: /* Problems */

2024-10-27T00:48:20Z

‎Problems

Tom: /* Miscellaneous References */

2023-11-21T04:37:26Z

‎Miscellaneous References

Tom: /* Context */

2021-01-25T16:42:51Z

‎Context

Tom: /* Full Title or Meme */

2021-01-22T18:24:33Z

‎Full Title or Meme

Tom: /* Problems */

2021-01-20T00:13:52Z

‎Problems

Tom: /* Solutions */

2021-01-18T20:18:34Z

‎Solutions

Tom: /* Problems */

2021-01-18T20:15:12Z

‎Problems

Tom: /* Solutions */

2020-11-25T04:14:50Z

‎Solutions

Tom: /* Solutions */

2020-08-26T18:58:04Z

‎Solutions

Tom: /* Problems */

2020-08-26T18:56:38Z

‎Problems

@@ Line 28: / Line 28: @@
 * The transaction times for block chain reads is on the order of 10s of seconds, the write time is on the order of 10s of minuets. Neither would be acceptable for a web identity.
 * The power consumption of a full node on a block chain is way in excess of what a portable device could ever afford on battery power.
 ==Solutions==

@@ Line 50: / Line 50: @@
 * The [https://identity.foundation/ DIF web site] has a lot of supporting documentation for the DID.
 [[Category:Glossary]]
 [[Category:Identifier]]
 [[Category:Standard]]

@@ Line 12: / Line 12: @@
 *Every one knows the problem with identities on the internet. They are not under the control of users, who are extremely interested in their own [[Identity]] and want their own [[Privacy]].
-* The BHAG (big hairy audacious goal) is the user in control, when the user really doesn't want to control their identity any more than than they want to program their own computers.
+* The BHAG (big hairy audacious goal) is the user in control, when the user really doesn't want to control their identifiers any more than than they want to program their own computers.
 ==Problems==

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-The DID is a URL that points to a DID document and can server as an [[Identifier]] that is under the control of a [[Subject]].
+The DID is a URL that points to a DID document and can serve as a public key Certificate for an [[Identifier]] that is under the control of a [[Subject]].
 ==Context==

@@ Line 15: / Line 15: @@
 ==Problems==
-* The One big problem with the existing solution of relying on social networks is that they control, and can remove, your identifiers at their sole discretion. Or in their own words:<blockquote>Yahoo may, without telling you
+* The One big problem with the existing solution of relying on social networks is that they control, and can remove, your identifiers at their sole discretion. Or in their own words:
-**immediately cancel or limit your access to your Yahoo accounts, certain Yahoo Services and any associated email addresses...
+**Yahoo may, without telling you, immediately cancel or limit your access to your Yahoo accounts, certain Yahoo Services and any associated email addresses...
 ** If you violate the letter or spirit of this Statement, or otherwise create risk or possible legal exposure for us, we can stop providing all or part of Facebook to you.
-**We reserve the right to modify or terminate the Service or your access to the Service for any reason, without notice, at any time, and without liability to you [Instagram]</blockquote>
+**We reserve the right to modify or terminate the Service or your access to the Service for any reason, without notice, at any time, and without liability to you [Instagram]
 * Another big problem is [[Trust]] where there are no standards or examples of any trust without a history of trusted behavior.
 * Beware of time-stamping services posing as trust anchors. Bellcore created such a service in the early 1990 and spun it off into a separate company in 1994.<ref>BELLCORE SPINS OFF NEW COMPANY TO OFFER DIGITAL NOTARY (TM)(SM) SERVICE  http://seclists.org/interesting-people/1994/Mar/100</ref> None of these services provide any trust in the contents of the documents.

@@ Line 38: / Line 38: @@
 *The '''[[Ion ID]]''' is a variant of the DID that is based on the side tree protocol.
 *'''[[Trusted Identifier]]s''' are a variant of the [[Decentralized ID]] that enables [[Identifier]] [[Recovery]] as would be required for many real-world scenarios like Health Care.
 ==References==

@@ Line 35: / Line 35: @@
 *In this wiki the IAP ([[Identifier or Attribute Provider]]) supply a [[Data Category]] only when that category has [[User Consent]]. To get all of those categories that the [[Relying Party]] requires, the request needs to go to a [[User Agent]] that is able to release the data held across many providers, some of the [[Hundred Points of Light]] that apply to the real-world [[User]], but only those appropriate for the [[Relying Party]] request are enabled by the user.
 *'''[https://w3c-ccg.github.io/did-method-registry/ The DID Method Registry]''' has been created to track the methods that implement the DID spec. There seem to be no particular criteria for a method to be accepted other than a willingness of the method's authors to submit the method as compliant.
-*'''Self-sovereign identities''' seem to be the answer to all parties' concerns. <ref>Ian Glazer, ''Why self-sovereign identity will get adopted (and it’s not the reason you probably want)'' 2018-06-15 https://www.tuesdaynight.org/2018/06/15/why-self-sovereign-identity-will-get-adopted-and-its-not-the-reason-you-probably-want/</ref> The only problem with it that I can see is that no one seems to know exactly what it is or how it might work. MIT has started an open source effort to build something<ref>Github, ''Developing General Principles for Sovereign Identity.'' https://github.com/mitmedialab/SovereignIdentityPrinciples</ref> but no one seems to know what.
+*[[Self-sovereign identities]] seem to be the answer to all parties' concerns. <ref>Ian Glazer, ''Why self-sovereign identity will get adopted (and it’s not the reason you probably want)'' 2018-06-15 https://www.tuesdaynight.org/2018/06/15/why-self-sovereign-identity-will-get-adopted-and-its-not-the-reason-you-probably-want/</ref> The only problem with it that I can see is that no one seems to know exactly what it is or how it might work. MIT has started an open source effort to build something<ref>Github, ''Developing General Principles for Sovereign Identity.'' https://github.com/mitmedialab/SovereignIdentityPrinciples</ref> but no one seems to know what.
 *'''[https://github.com/decentralized-identity/sidetree-core/blob/master/docs/protocol.md Side tree protocol]''' provides a high transaction through-put capability for DIDs.
 *The '''[[Ion ID]]''' is a variant of the DID that is based on the side tree protocol.

@@ Line 31: / Line 31: @@
 ==Solutions==
-* The W3C has established a credential community group (CCG) to establish the consensus needed to crate a working group that would then propose a [https://w3c-ccg.github.io/did-spec/ draft standard for the DID - Decentralized ID], and also a [[Verifiable Claim]]s WG.
+* The W3C has established a credential group (CG) to establish the consensus needed to propose a [https://w3c-ccg.github.io/did-spec/ draft standard for the DID - Decentralized ID], and also a [[Verifiable Claim]]s WG.
-* [[Verified Claim]] is one of the work efforts of the CCG.
+* [[Verified Claim]] is one of the work efforts of the CG.
 *In this wiki the IAP ([[Identifier or Attribute Provider]]) supply a [[Data Category]] only when that category has [[User Consent]]. To get all of those categories that the [[Relying Party]] requires, the request needs to go to a [[User Agent]] that is able to release the data held across many providers, some of the [[Hundred Points of Light]] that apply to the real-world [[User]], but only those appropriate for the [[Relying Party]] request are enabled by the user.
 *'''[https://w3c-ccg.github.io/did-method-registry/ The DID Method Registry]''' has been created to track the methods that implement the DID spec. There seem to be no particular criteria for a method to be accepted other than a willingness of the method's authors to submit the method as compliant.

@@ Line 19: / Line 19: @@
 ::: If you violate the letter or spirit of this Statement, or otherwise create risk or possible legal exposure for us, we can stop providing all or part of Facebook to you.
-:: We reserve the right to modify or terminate the Service or your access to the Service for any reason, without notice, at any time, and without liability to you [Instagram]</blockquote>
+::: We reserve the right to modify or terminate the Service or your access to the Service for any reason, without notice, at any time, and without liability to you [Instagram]</blockquote>
 * Another big problem is [[Trust]] where there are no standards or examples of any trust without a history of trusted behavior.
 * Beware of time-stamping services posing as trust anchors. Bellcore created such a service in the early 1990 and spun it off into a separate company in 1994.<ref>BELLCORE SPINS OFF NEW COMPANY TO OFFER DIGITAL NOTARY (TM)(SM) SERVICE  http://seclists.org/interesting-people/1994/Mar/100</ref> None of these services provide any trust in the contents of the documents.