Skip to content

Commit 19ec2c7

Browse files
mspornyTallTeddlongley
committed
Fix grammar in validation expectations section.
Co-authored-by: Ted Thibodeau Jr <[email protected]> Co-authored-by: Dave Longley <[email protected]>
1 parent b00ca37 commit 19ec2c7

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

index.html

+10-9
Original file line numberDiff line numberDiff line change
@@ -6550,27 +6550,28 @@ <h3>Credential Type</h3>
65506550
When a [=verifier=] requests one or more [=verifiable credentials=] from a
65516551
[=holder=], they can specify the <a href="#types">type</a> of credential(s)
65526552
that they would like to receive. Credential types, as well as validation schemas
6553-
for the type and each of its [=claims=], are defined by specification authors
6553+
for each type and each of their [=claims=], are defined by specification authors
65546554
and are published in places like the [[[VC-SPECS]]].
65556555
</p>
65566556

65576557
<p>
65586558
The type of a credential is expressed via the <a href="#types">type</a>
65596559
property. A [=verifiable credential=] of a specific type is expected to contain
6560-
specific [=properties=] that can be used to determine whether or not the
6561-
[=presentation=] meets a set of processing rules that the [=verifier=] is
6562-
executing. By requesting [=verifiable credentials=] of a particular `type`, the
6560+
specific [=properties=] (which might be deeply nested) that can be used to determine whether or not the
6561+
[=presentation=] satisfies a set of processing rules that the [=verifier=]
6562+
executes. By requesting [=verifiable credentials=] of a particular `type`, the
65636563
[=verifier=] is able to gather specific information from the [=holder=], which
6564-
originated with the [=issuer=] of each [=verifiable credential=], that will
6565-
enable it to determine the next stage of an interaction with a [=holder=].
6564+
originated with the [=issuer=] of each [=verifiable credential=], that will
6565+
enable the [=verifier=] to determine the next stage of an interaction with a [=holder=].
65666566
</p>
65676567

65686568
<p>
65696569
When a [=verifier=] requests a [=verifiable credential=] of a specific type,
65706570
there will be a set of mandatory and optional [=claims=] that are associated
6571-
with that type. It is expected that a [=verifier=] will fail to validate
6572-
[=claims=] that are mandatory that are not included and will ignore any
6573-
[=claim=] that is not associated with the specific type. In other words, a
6571+
with that type. It is expected that a [=verifier=]'s validation of a
6572+
[=verifiable credential=] will fail when mandatory [=claims=] are not
6573+
included, and that any [=claim=] that is not associated with the specific
6574+
type will be ignored. In other words, a
65746575
[=verifier=] will perform input validation on the [=verifiable credential=] it
65756576
receives and will reject malformed input based on the credential type
65766577
specification.

0 commit comments

Comments
 (0)