Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify inputBytes, inputDocument, inputMediaType #1438

Merged
merged 1 commit into from
Feb 27, 2024
Merged

clarify inputBytes, inputDocument, inputMediaType #1438

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 9 additions & 10 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4131,10 +4131,10 @@ <h3>Securing Mechanism Specifications</h3>
JOSE/COSE header parameters and signatures. Specifications MAY provide additional mechanisms to convey
other information that might be helpful (for example, during validation or for
debugging purposes), such as securing mechanism data. A securing mechanism's
verification algorithm MUST provide an interface that receives a sequence of
bytes ([=byte sequence=] |inputBytes|) or a document ([=map=] |inputDocument|)
and a media type ([=string=] |inputMediaType|) as inputs and returns a
verification result with at least the following [=struct/items=]:
verification algorithm MUST provide an interface that receives inputs of a media
type ([=string=] |inputMediaType|) paired with either a sequence of bytes
([=byte sequence=] |inputBytes|) or a document ([=map=] |inputDocument|), and
returns a verification result with at least the following [=struct/items=]:
</p>

<dl>
Expand Down Expand Up @@ -4726,11 +4726,10 @@ <h3>Verification</h3>
<p>
This section contains an algorithm that [=conforming verifier
implementations=] MUST run when verifying a [=verifiable credential=] or a
[=verifiable presentation=]. This algorithm takes a sequence of bytes
([=byte sequence=] |inputBytes|) or a document
([=map=] |inputDocument|) and a media type
([=string=] |inputMediaType|) as inputs, and returns a [=map=]
that contains the following:
[=verifiable presentation=]. This algorithm takes inputs of a media
type ([=string=] |inputMediaType|) paired with either a sequence of bytes
([=byte sequence=] |inputBytes|) or a document ([=map=] |inputDocument|),
and returns a [=map=] that contains the following:
</p>

<ul>
Expand Down Expand Up @@ -4782,7 +4781,7 @@ <h3>Verification</h3>
had an issue determining the proper |verifyProof| algorithm to use, but the
Working Group is attempting to see if saying more here would be worthwhile.
Additional example language could be added that says that an implementation
might have an allow list of acceptable cryptosuites -- and these will be used as
might have an allow list of acceptable cryptosuites — and these will be used as
inputs for finding matching proofs to be verified.
</div>
</li>
Expand Down