Skip to content

Commit

Permalink
Fix grammar in validation expectations section.
Browse files Browse the repository at this point in the history
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Dave Longley <[email protected]>
  • Loading branch information
3 people committed Mar 9, 2024
1 parent b00ca37 commit 19ec2c7
Showing 1 changed file with 10 additions and 9 deletions.
19 changes: 10 additions & 9 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -6550,27 +6550,28 @@ <h3>Credential Type</h3>
When a [=verifier=] requests one or more [=verifiable credentials=] from a
[=holder=], they can specify the <a href="#types">type</a> of credential(s)
that they would like to receive. Credential types, as well as validation schemas
for the type and each of its [=claims=], are defined by specification authors
for each type and each of their [=claims=], are defined by specification authors
and are published in places like the [[[VC-SPECS]]].
</p>

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

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

0 comments on commit 19ec2c7

Please sign in to comment.