Verifiable Claim - Revision history

Tom: /* JWT Rules for Verifiable Claims */

2020-12-18T22:47:57Z

‎JWT Rules for Verifiable Claims

Tom: /* =Other Material */

2019-08-21T20:17:18Z

‎=Other Material

Tom: /* References */

2019-08-21T20:17:02Z

‎References

Tom: /* JWT Rules for Verifiable Claims */

2019-07-06T19:22:35Z

‎JWT Rules for Verifiable Claims

Tom: /* JWT Rules for Verifiable Claims */

2019-07-06T19:15:42Z

‎JWT Rules for Verifiable Claims

Tom: /* EXAMPLE - A simple verifiable claim */

2019-07-06T19:09:46Z

‎EXAMPLE - A simple verifiable claim

Tom: /* EXAMPLE - A simple verifiable claim */

2019-07-06T19:07:16Z

‎EXAMPLE - A simple verifiable claim

Tom: /* False Claims */

2019-01-24T21:56:43Z

‎False Claims

Tom: /* False Claims */

2019-01-24T21:54:53Z

‎False Claims

Tom: /* False Claims */

2019-01-24T18:19:00Z

‎False Claims

@@ Line 90: / Line 90: @@
 JSON Web Token (JWT) [RFC7519] is a widely used means to express claims to be transferred between two parties. Providing a representation of the Verifiable Credentials Data Model for JWT allows existing systems and libraries to participate in the ecosystem described in Section § 1.2 Ecosystem Overview. A JWT encodes a set of claims as a JSON object that is contained in a JSON Web Signature (JWS) [RFC7515] or JWE [RFC7516].
-vc: JSON object, which MUST be present in a JWT verifiable credential. The object contains the verifiable credential according to this specification.
+vc: JSON object, which MUST be present in a JWT verifiable [[Credential]]. The object contains the verifiable credential according to this specification.
-vp: JSON object, which MUST be present in a JWT verifiable presentation. The object contains the verifiable presentation according to this specification.
+vp: JSON object, which MUST be present in a JWT verifiable [[Presentation]]. The object contains the verifiable [[Presentation]] according to this specification.
 JWT Encoding
 To encode a verifiable credential as a JWT, specific properties introduced by this specification MUST be encoded as standard JOSE header parameters, JWT registered claim names, or contained in the JWS signature part. If no explicit rule is specified, properties are encoded in the same way as with a standard verifiable credential, and are added to the vc property of the JWT. The following paragraphs describe these encoding rules.
-If the JWS is present, the digital signature either refers to the issuer of the verifiable credential, or in the case of a verifiable presentation, the holder of the verifiable credential. The JWS proves that the issuer of the JWT signed the contained JWT payload and therefore, the proof property can be omitted.
+If the JWS is present, the digital signature either refers to the issuer of the verifiable credential, or in the case of a verifiable [[Presentation]], the holder of the verifiable credential. The JWS proves that the issuer of the JWT signed the contained JWT payload and therefore, the proof property can be omitted.
 alg MUST be used for RSA and ECDSA-based digital signatures. If only the proof attribute is used, the alg header MUST be set to none.

@@ Line 166: / Line 166: @@
 ==References==
 <references />
-===Other Material==
+===Other Material===
 * Phil Windley has create [http://www.windley.com/archives/2019/08/life-like_identity_why_the_internet_needs_an_identity_metasystem.shtml a model based on DIDs and Verified Credential] that is very ambitious, but without sufficient detail to make a deployment feasible.
 * Synonyms include: [[Assurance]] [[Attested]] [[Corroborated]].

@@ Line 166: / Line 166: @@
 ==References==
 <references />
 * Synonyms include: [[Assurance]] [[Attested]] [[Corroborated]].
 [[Category:Glossary]]
 [[Category:Standard]]

@@ Line 83: / Line 83: @@
 ==JWT Rules for Verifiable Claims==
-This section was abstracted from the work of the Verifiable Claims working group of the W3C on 2019-06-01 and then modified to work for US Health Care needs. At that time this feature was at risk for removal from the spec for lack of implementations.
+This section was abstracted from the work of the Verifiable Claims working group of the W3C on 2019-06-01 and then modified to work for US Health Care needs. At that time this feature was at risk for removal from the spec for lack of implementations. The most noticeable (and least significant) change is to drop the name "credential" as it has a very different meaning in common use for [[Identity Management]].
 <pre>

@@ Line 83: / Line 83: @@
 ==JWT Rules for Verifiable Claims==
-This section was abstracted from the work of the Verifiable Claims working group of the W3C on 2019-05-01 and then modified to work for US Health Care needs.
+This section was abstracted from the work of the Verifiable Claims working group of the W3C on 2019-06-01 and then modified to work for US Health Care needs. At that time this feature was at risk for removal from the spec for lack of implementations.
 <pre>
 .3.1 JSON Web Token
 JSON Web Token (JWT) [RFC7519] is a widely used means to express claims to be transferred between two parties. Providing a representation of the Verifiable Credentials Data Model for JWT allows existing systems and libraries to participate in the ecosystem described in Section § 1.2 Ecosystem Overview. A JWT encodes a set of claims as a JSON object that is contained in a JSON Web Signature (JWS) [RFC7515] or JWE [RFC7516].
 vc: JSON object, which MUST be present in a JWT verifiable credential. The object contains the verifiable credential according to this specification.

@@ Line 77: / Line 77: @@
      "domain": "json-ld.org",
      "nonce": "598c63d6",
-     "signatureValue": "BavEll0/I1zpYw8XNi1bgVg/sCneO4Jugez8RwDg/+
+     "signatureValue": "BavEll0/I1z … T24="
+   }
+}
 </pre>
 ==JWT Rules for Verifiable Claims==

@@ Line 14: / Line 14: @@
 A [[Verifiable Claim]] can be perfectly constructed, totally verifiable, and still be completely false if it is not about a real attribute of the [[Subject]] that created the digital [[Identifier]] that is bound to the claim. This is a particularly knotty problem for a [[Decentralized ID]] that is not known to be bound to any particular human user by its very design. It may be that the [[Decentralized ID]] has protected the user against release of [[User Private Information]], but it does not meet the primary meaning of [[Privacy]], namely the right to be let alone. Now any can make a claim about any [[Identifier]] and if the [[Subject]] does not want to expose more of their [[User Private Information]] they cannot avail themselves of the right of [[Redress]] to false claims.
-There are lots of statistics about (mostly unstructured) claims  made on the web today, but the best estimate seems to be that over 50% are false. For example the claim that Hillary Clinton was running a pedophile ring out of the basement of a pizzeria that had no basement. Based on that it would be prudent to assume that 50% of the [[Verifiable Claim]]s would also be false.
+There are lots of statistics about (mostly unstructured) claims  made on the web today, but the best estimate seems to be that over 50% are false. For example the claim that Hillary Clinton was running a pedophile ring out of the basement of a pizzeria that had no basement. Based on that finding it would be prudent to assume that 50% of the [[Verifiable Claim]]s would also be false.
 The science fiction writers Vernor Vinge<ref>Vernor Vinge, ''True Names and the Opening of the Cyberspace Frontier.'' (2001-12-14 original 1981) ISBN 978-0312862077</ref> and Stanislaw Lem<ref>Paul Grimstad, ''The Beautiful Mind Bending of Stanislaw Lem.'' New Yorker https://www.newyorker.com/culture/culture-desk/the-beautiful-mind-bending-of-stanislaw-lem</ref> have explored the hazards of navigating in the digital and the real worlds with false identities. In Vinge's book the protagonist is exposed and suffers from the hands of the corrupt government. In Lem's actual life he learns to create false papers and escapes from a corrupt government with the help of a false identity. It should be clear that as [[Identity]] papers become easier to create, the incidence of false papers will proliferate.

@@ Line 16: / Line 16: @@
 There are lots of statistics about (mostly unstructured) claims  made on the web today, but the best estimate seems to be that over 50% are false. For example the claim that Hillary Clinton was running a pedophile ring out of the basement of a pizzeria that had no basement. Based on that it would be prudent to assume that 50% of the [[Verifiable Claim]]s would also be false.
-The science fiction writers Vernor Vinge<ref>Vernor Vinge, ''True Names and the Opening of the Cyberspace Frontier.'' (2001-12-14 original 1981) ISBN 978-0312862077</ref> and Stanislaw Lem<ref>By Paul Grimstad, ''The Beautiful Mind Bending of Stanislaw Lem.'' New Yorker https://www.newyorker.com/culture/culture-desk/the-beautiful-mind-bending-of-stanislaw-lem</ref> have explored the hazards of navigating in the digital and the real worlds with false identities. In Vinge's book the protagonist is exposed and suffers from the hands of the corrupt government. In Lem's actual life he learns to create false papers and escapes from a corrupt government with the help of a false identity. It should be clear that as [[Identity]] papers become easier to create, the incidence of false papers will proliferate.
+The science fiction writers Vernor Vinge<ref>Vernor Vinge, ''True Names and the Opening of the Cyberspace Frontier.'' (2001-12-14 original 1981) ISBN 978-0312862077</ref> and Stanislaw Lem<ref>Paul Grimstad, ''The Beautiful Mind Bending of Stanislaw Lem.'' New Yorker https://www.newyorker.com/culture/culture-desk/the-beautiful-mind-bending-of-stanislaw-lem</ref> have explored the hazards of navigating in the digital and the real worlds with false identities. In Vinge's book the protagonist is exposed and suffers from the hands of the corrupt government. In Lem's actual life he learns to create false papers and escapes from a corrupt government with the help of a false identity. It should be clear that as [[Identity]] papers become easier to create, the incidence of false papers will proliferate.
 ==Solution ==