Difference between revisions of "Verifiable Claim"

From MgmtWiki
Jump to: navigation, search
(Taxonomy of the spec)
(Taxonomy of the spec)
Line 16: Line 16:
 
|  Name in spec || Name in Wiki ||  Definition  
 
|  Name in spec || Name in Wiki ||  Definition  
 
|-
 
|-
|entity || n/a || A thing with distinct and independent existence such as a person, organization, concept, or device.
+
|entity || in conflict || A thing with distinct and independent existence such as a person, organization, concept, or device.
 
|-
 
|-
 
|subject || subject ||An entity about which claims may be made.
 
|subject || subject ||An entity about which claims may be made.
Line 24: Line 24:
 
| verifiable claim || || claim that is effectively tamper-proof and whose authorship can be cryptographically verified. Multiple claims may be bundled together into a set of claims.
 
| verifiable claim || || claim that is effectively tamper-proof and whose authorship can be cryptographically verified. Multiple claims may be bundled together into a set of claims.
 
|-
 
|-
| List of required user attributes || always needed || proof of presence (for example)
+
|issuer || issuer ||An entity that creates a verifiable claim, associates it with a particular subject, and transmits it to a holder. Examples of issuers include corporations, governments, and individuals.
 +
 
 
|-
 
|-
| List of requested user attributes || above and beyond the above || passport, drivers license
+
| inspector-verifier || Attribute Provider (on-line) ||An entity that receives one or more verifiable claims for processing. Examples of inspector-verifiers include employers, security personnel, and websites.
 +
 
 
|-
 
|-
| Privacy policy || URL || DOI or URN
+
| identifier registry ||Attribute Provider (off-line) ||Mediates the creation and verification of subject identifiers. Examples of identifier registries include corporate employee databases, government ID databases, and distributed ledgers.
 
|-
 
|-
 
|  Terms of use  || URL || DOI or URN
 
|  Terms of use  || URL || DOI or URN
Line 35: Line 37:
 
|-
 
|-
 
|  Software in use ||  || Determine the location's expected behavior  
 
|  Software in use ||  || Determine the location's expected behavior  
|-
+
 
| 8 || Contact information ||structure(locale)||  mailto: phone fax, etc.
 
|-
 
| 9 || Signature Type|| fixed list||  bgcolor="SkyBlue"|RSA2048 (for example)
 
|-
 
| 10 ||Signature ||hex value||  bgcolor="SkyBlue"|134bbead23d908e0a3221bc
 
 
|}
 
|}
  

Revision as of 09:33, 5 December 2018

Full Title or Meme

A Verifiable Claim is one that can be Validated by a signed statement from some recognized authority as to the nature of a linkage between Attributes and a Subject.

Context

  • The Context in which a validation applies should be made clear by a policy statement from the validating authorities.
  • The mission of the Verifiable Claims Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.

Problem

Solution

Taxonomy of the spec

Name in spec Name in Wiki Definition
entity in conflict A thing with distinct and independent existence such as a person, organization, concept, or device.
subject subject An entity about which claims may be made.
claim attribute A statement made by an entity about a subject.
verifiable claim claim that is effectively tamper-proof and whose authorship can be cryptographically verified. Multiple claims may be bundled together into a set of claims.
issuer issuer An entity that creates a verifiable claim, associates it with a particular subject, and transmits it to a holder. Examples of issuers include corporations, governments, and individuals.
inspector-verifier Attribute Provider (on-line) An entity that receives one or more verifiable claims for processing. Examples of inspector-verifiers include employers, security personnel, and websites.
identifier registry Attribute Provider (off-line) Mediates the creation and verification of subject identifiers. Examples of identifier registries include corporate employee databases, government ID databases, and distributed ledgers.
Terms of use URL DOI or URN
Trusted Identifier URN TID:framework:LUID
Software in use Determine the location's expected behavior

References

  1. Synonyms include: Assurance Attested Corroborated.