From 2cf2a94ce96a1cdb1b1b56d4804854670defc3f4 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 6 Jul 2024 18:28:43 -0400 Subject: [PATCH] Fix grammar in verification interface. Co-authored-by: Ted Thibodeau Jr --- index.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/index.html b/index.html index dace1d1f7..19192441d 100644 --- a/index.html +++ b/index.html @@ -4122,17 +4122,17 @@

Securing Mechanism Specifications

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=]: