From e905e1344fc2e0e4173f46f56e0b3605df82a727 Mon Sep 17 00:00:00 2001
From: Orie Steele Issuer
+The value associated with the holder
property is expected
+to identify an holder that is known to and trusted by the
+verifier.
+
+Relevant metadata about the holder
property is expected
+to be available to the verifier. For example, an holder can
+publish information containing the verification material used to secure
+verifiable presentations. This metadata is relevant when
+checking the proofs on the verifiable presentations.
+
+See the Subject-Holder Relationships and + for additional examples related to subject and holder. +
+ ++`issuer`, `subject` and `holder` are graph nodes, which support multiple representations, +making validating that these roles are performed by the same entity potentially complex. +
++A verifier might believe that a verifiable presentation holder +is the same entity as a verifiable credential subject, when the following happens: +
++When the identifiers for `holder` and `subject` are the same. +
++When the verification material used to provide a `proof` on a verifiable presentation, +is also present in the claims about the credential subject, either by value or by reference. +
+
The value associated with the holder
property is expected
-to identify an holder that is known to and trusted by the
+to identify a holder that is known and trusted by the
verifier.
From 44428d1487e5dd5da3398aa04ccb7fc377167722 Mon Sep 17 00:00:00 2001
From: Orie Steele Holder
Relevant metadata about the holder
property is expected
-to be available to the verifier. For example, an holder can
+to be available to the verifier. For example, a holder can
publish information containing the verification material used to secure
verifiable presentations. This metadata is relevant when
-checking the proofs on the verifiable presentations.
+checking proofs on verifiable presentations.
See the Subject-Holder Relationships and
From 3b493114f0a6a5e82cacef09e51a3f81d043124a Mon Sep 17 00:00:00 2001
From: Orie Steele
A verifier might believe that a verifiable presentation holder
-is the same entity as a verifiable credential subject, when the following happens:
+is the same entity as a verifiable credential subject, when the following conditions apply:
-When the verification material used to provide a `proof` on a verifiable presentation,
+When the verification material used to provide a
-When the verification material used to provide a
The value associated with the
From 9dbd12e6b405233a941096339d7cea82a539cd2d Mon Sep 17 00:00:00 2001
From: Orie Steele
-See the Subject-Holder Relationships and
+See the and
for additional examples related to subject and holder.
-When the verification material used to secure a verifiable presentation,
+When the verification material used to secure a verifiable presentation
is also present in the claims about the credential subject, either by value or by reference.
-A verifier might believe that a verifiable presentation holder
+A verifier might conjecture that a verifiable presentation holder
is the same entity as a verifiable credential subject, when the following conditions apply:
From 8dcf3a8e3ddeffd192f84496d3fb5a3f69f8af1c Mon Sep 17 00:00:00 2001
From: Orie Steele
-`issuer`, `subject` and `holder` are graph nodes, which support multiple representations,
+`issuer`, `subject`, and `holder` are graph nodes, which support multiple representations,
making validating that these roles are performed by the same entity potentially complex.
The value associated with the
Relevant metadata about the
`issuer`, `subject`, and `holder` are graph nodes, which support multiple representations,
-making validating that these roles are performed by the same entity potentially complex.
+potentially making it complex to evaluate whether these roles are being filled
+by the same entity.
From 5e5bc528321f2e48d9b887b87506a00d1193a871 Mon Sep 17 00:00:00 2001
From: Orie Steele
-`issuer`, `subject`, and `holder` are graph nodes, which support multiple representations,
+`Issuer`, `subject`, and `holder` are graph nodes which support multiple representations,
potentially making it complex to evaluate whether these roles are being filled
by the same entity.
The value associated with the
Relevant metadata about the
`Issuer`, `subject`, and `holder` are graph nodes which support multiple representations,
potentially making it complex to evaluate whether these roles are being filled
-by the same entity.
+by appropriate entities. Validation is the process by which verifiers apply business rules to
+evaluate the appropriateness of a particular use of a Verifiable Credential.
-A verifier might conjecture that a verifiable presentation holder
-is the same entity as a verifiable credential subject, when the following conditions apply:
+A verifier might need to validate a given verifiable presentation
+against complex business rules; for example, the verifier may need confidence
+that the holder is the same entity as a subject of a verifiable
+credential. In that situation, the following factors should provide
+reasonable confidence that the holder presenting a given VC is, in fact, a
+subject of that VC:
A verifier might need to validate a given verifiable presentation
-against complex business rules; for example, the verifier may need confidence
+against complex business rules; for example, the verifier might need confidence
that the holder is the same entity as a subject of a verifiable
credential. In that situation, the following factors should provide
reasonable confidence that the holder presenting a given VC is, in fact, a
From 260568e48084a95f84702cfa5f7f4ae3fa9352d2 Mon Sep 17 00:00:00 2001
From: Orie Steele
From 32c8e847291697f165357d5ea8e409696a0d827a Mon Sep 17 00:00:00 2001
From: Orie Steele
From f91ccbfa665915aaeea6b017bc9ab6b9dcfe063c Mon Sep 17 00:00:00 2001
From: Orie Steele
-Relevant metadata about the
When the identifiers for `holder` and `subject` are the same.
-
When the verification material used to secure a verifiable presentation
is also present in the claims about the credential subject, either by value or by reference.
- Holder
Holder
vp+ld+json
.
Holder
proof
on a verifiable presentation,
is also present in the claims about the credential subject, either by value or by reference.
Holder
proof
on a verifiable presentation,
+When the verification material used to secure a verifiable presentation,
is also present in the claims about the credential subject, either by value or by reference.
Issuer
Holder
holder
property is expected
-to identify a holder that is known and trusted by the
+to identify the holder to the verifier.
verifier.
Holder
checking proofs on verifiable presentations.
Holder
Holder
From 225ead3567cebf0c330353027befe493943659ac Mon Sep 17 00:00:00 2001
From: Orie Steele
Holder
Presentations defines expressions of `holder` in presentations
Holder
From 32b625416218bc557063b36535b951645a669d13 Mon Sep 17 00:00:00 2001
From: Orie Steele
Issuer
Holder
holder
property is expected
-to identify the holder to the verifier.
-verifier.
+to identify the holder to the verifier.
holder
property is expected
From 3d2c7a6251a50248e1d67d501da692a1c1f7d607 Mon Sep 17 00:00:00 2001
From: Orie Steele Holder
Holder
Holder
Issuers define expressions of `issuer` in credentials
Holder
Presentations define expressions of `holder` in presentations
Holder
Issuer
Holder
holder
property is expected
-to identify the holder to the verifier.
+to be usable to identify the holder to the verifier.
holder
property is expected
From 223064c8e512731d4798c7075e0f148cf2ffafff Mon Sep 17 00:00:00 2001
From: Orie Steele Holder
Holder
Holder
Holder
A verifier might need to validate a given verifiable presentation
against complex business rules; for example, the verifier might need confidence
that the holder is the same entity as a subject of a verifiable
-credential. In that situation, the following factors should provide
+credential. In that situation, the following factors can provide
reasonable confidence that the holder presenting a given VC is, in fact, a
subject of that VC:
Holder
against complex business rules; for example, the verifier might need confidence
that the holder is the same entity as a subject of a verifiable
credential. In that situation, the following factors can provide
-reasonable confidence that the holder presenting a given VC is, in fact, a
-subject of that VC:
+reasonable confidence that the holder presenting a given
+verifiable credential is, in fact, a subject of that
+verifiable credential:
Holder
vp+ld+json
.
+using a mechanism the verifier trusts to protect the integrity of the content.
Holder
Holder
Holder
Presentations define expressions of a `holder` in presentations
Holder
to be usable to identify the holder to the verifier.
holder
property is expected
-to be available to the verifier. For example, a holder can
+Relevant metadata about the entity identified by the value of the
+holder
property is expected to be available to or
+retrievable by the verifier. For example, a holder can
publish information containing the verification material used to secure
verifiable presentations. This metadata is relevant when
checking proofs on verifiable presentations.
From 5d44e0e8dd9ac9f3bd7a44e1e500e2d189578fc1 Mon Sep 17 00:00:00 2001
From: Orie Steele Holder
using a mechanism the verifier trusts to protect the integrity of the content.
-Relevant metadata about the entity identified by the value of the
-holder
property is expected to be available to or
-retrievable by the verifier. For example, a holder can
+Often relevant metadata about the holder, as identified by the value of the
+holder
property, is available to, or
+retrievable by, the verifier. For example, a holder can
publish information containing the verification material used to secure
-verifiable presentations. This metadata is relevant when
-checking proofs on verifiable presentations.
+verifiable presentations. This metadata is expected to be used when
+checking proofs on verifiable presentations. Some cryptographic
+identifiers contain all necessary metadata in the identifier itself. In those
+cases, no additional metadata is required. Other identifiers use verifiable
+data registries where such metadata is automatically published for use
+by verifiers, without any additional action by the holder.
See the and
From ff5913dc9ab828ff7e4cdf6e5703a053439cfefb Mon Sep 17 00:00:00 2001
From: Orie Steele Holder
`Issuer`, `subject`, and `holder` are graph nodes which support multiple representations,
potentially making it complex to evaluate whether these roles are being filled
by appropriate entities. Validation is the process by which verifiers apply business rules to
-evaluate the appropriateness of a particular use of a Verifiable Credential.
+evaluate the appropriateness of a particular use of a verifiable credential.
From 9203268ee6dca038e881e6c584ceac617125e7c5 Mon Sep 17 00:00:00 2001
From: Orie Steele Holder
When the identifiers for `holder` and `subject` are the same.
-`Issuer`, `subject`, and `holder` are graph nodes which support multiple representations, -potentially making it complex to evaluate whether these roles are being filled -by appropriate entities. Validation is the process by which verifiers apply business rules to +Validation is the process by which verifiers apply business rules to evaluate the propriety of a particular use of a verifiable credential.