Skip to content

Commit

Permalink
Fix grammar in verification material language.
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 Feb 4, 2024
1 parent a41d544 commit 21a0755
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
10 changes: 5 additions & 5 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -735,7 +735,7 @@ <h3>Credentials</h3>
[=entity=]. [=Credentials=] might also include an identifier and metadata
to describe properties of the [=credential=], such as the
[=issuer=], the validity date and time period, a representative image,
verification material to use for [=verification=] purposes, the revocation
[=verification material=], the revocation
mechanism, and so on. The metadata might be signed by the [=issuer=]. A
[=verifiable credential=] is a set of tamper-evident [=claims=] and
metadata that cryptographically prove who issued it.
Expand Down Expand Up @@ -5787,7 +5787,7 @@ <h3>Key Management</h3>
provides recommendations for protective measures, harm reduction, and
revocation. Although this section focuses primarily on the security of the
private signing key, [[NIST-SP-800-57-Part-1]] also highly recommends
confirmation of the validity of all verification material before using it.
confirmation of the validity of all [=verification material=] before using it.
</p>
</section>

Expand Down Expand Up @@ -6339,7 +6339,7 @@ <h3>Credential Subject</h3>
`credentialSubject` is expected to identify a [=subject=] to the
[=verifier=]. If the [=holder=] is also the [=subject=], then
the [=verifier=] could authenticate the [=holder=] if they have
verification material metadata related to the [=holder=]. The [=verifier=]
[=verification=] metadata related to the [=holder=]. The [=verifier=]
could then authenticate the [=holder=] using a signature generated by the [=holder=]
contained in the [=verifiable presentation=]. The `id`
[=property=] is optional. [=Verifiers=] could use other [=properties=]
Expand Down Expand Up @@ -6390,7 +6390,7 @@ <h4>Holder</h4>
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
the [=verification material=] used to secure [=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
Expand Down Expand Up @@ -6483,7 +6483,7 @@ <h3>Proofs (Signatures)</h3>

<ul>
<li>
Acceptably recent metadata regarding the verification material associated
Acceptably recent metadata regarding the [=verification material=] associated
with the signature is available. For example, the metadata might include
[=properties=] related to validity periods, key owner, or key purpose.
</li>
Expand Down
2 changes: 1 addition & 1 deletion terms.html
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@
</dd>
<dt><dfn data-lt="verification material">verification material</dfn></dt>
<dd>
Cryptographic information could be a public key or any other cryptographic data
Information that could be a cryptographic public key or any other data
used to verify a proof.
</dd>
<dt><dfn data-lt="URL|URLs">URL</dfn></dt>
Expand Down

0 comments on commit 21a0755

Please sign in to comment.