Difference between revisions of "Verifiable Claim"
From MgmtWiki
(→Taxonomy from the spec) |
|||
| Line 8: | Line 8: | ||
==Problem== | ==Problem== | ||
| − | + | Granting a benefit requires proof and verification. Some benefits demand a formal process that includes three parties. In this process, the holder asks for the benefit and the inspector-verifier grants or denies the benefit based on verification of the holder’s qualification from a trusted issuer. | |
==Solution == | ==Solution == | ||
| Line 14: | Line 14: | ||
===Taxonomy from the spec=== | ===Taxonomy from the spec=== | ||
{|border="1" padding="2" width="799px" | {|border="1" padding="2" width="799px" | ||
| − | | Name in spec || Name in | + | | Name in spec || Name in this wiki || Definition |
|- | |- | ||
|entity || in conflict || 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. | ||
Revision as of 09:59, 5 December 2018
Contents
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
Granting a benefit requires proof and verification. Some benefits demand a formal process that includes three parties. In this process, the holder asks for the benefit and the inspector-verifier grants or denies the benefit based on verification of the holder’s qualification from a trusted issuer.
Solution
- A Verifiable Claims Data Model and Representations document is under development by the W3C Verifiable Claims working group on this GitHub site.
Taxonomy from the spec
| Name in spec | Name in this 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 | Statement | claim that is effectively tamper-proof and whose authorship can be cryptographically verified, expressed in a standard, machine-readable data format which can also be extended with minimal coordination. |
| entity credential | in conflict | A set of one or more claims made by the same entity about a subject. (unclear how this is different from a verifiable claim) |
| 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 | An entity that receives one or more verifiable claims for processing. Examples of inspector-verifiers include employers, security personnel, and websites. |
| identifier registry | Identifier Provider | Mediates the creation and verification of subject identifiers. Examples of identifier registries include corporate employee databases, government ID databases, and distributed ledgers. |
| Entity Profile | Trusted Identifier | information that, together with a subject identifier id, constitute an entity profile. The properties are not claims and are not intended to be verifiable. |
| Issued | Date | |
| Type | Software in use | Determine the location's expected behavior |
Note that the term Identifier or Attribute Provider is used in this wiki as the distinction between identifiers and attributes is arbitrary and subject to interpretation.
References
- Synonyms include: Assurance Attested Corroborated.
