Skip to content

Commit

Permalink
Fix grammar in verification interface.
Browse files Browse the repository at this point in the history
Co-authored-by: Ted Thibodeau Jr <[email protected]>
  • Loading branch information
msporny and TallTed committed Jul 21, 2024
1 parent 3e59f60 commit 2cf2a94
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -4122,17 +4122,17 @@ <h3>Securing Mechanism Specifications</h3>

<p>
Securing mechanism specifications MUST provide a verification algorithm that
returns the information in the [=conforming document=] that has been
secured in isolation, without any securing mechanism information included, such as `proof` or
returns the information in the [=conforming document=] that has been secured, in
isolation, without including any securing mechanism information, such as `proof` or
JOSE/COSE header parameters and signatures. Verification algorithms MAY return
additional information that might be helpful (for example, during validation or
for debugging purposes), such as securing mechanism details. A verification
for debugging purposes), such as details of the securing mechanism. A verification
algorithm MUST provide an interface that receives a media type ([=string=]
|inputMediaType|) and input data ([=byte sequence=] or [=map=] |inputData|).
If the verification algorithm expects a [=byte sequence=], provide |inputData|
to the algorithm. If the verification algorithm expects a [=map=], provide the
result of [=parsing JSON bytes to an Infra value=] given |inputData|. Securing
mechanism specifications MAY provide additional algorithms and interfaces to the
mechanism specifications MAY provide algorithms and interfaces in addition to the
ones specified in this document. The verification algorithm returns a
verification result with at least the following [=struct/items=]:
</p>
Expand Down

0 comments on commit 2cf2a94

Please sign in to comment.