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.

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

Better requirement for proofPurpose's presence and validity. #249

Merged
merged 2 commits into from
Oct 16, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 5 additions & 2 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2248,8 +2248,11 @@ <h3>Proofs (e.g., Signatures)</h3>
or key purpose.</li>
<li>The key MUST NOT be revoked or expired.</li>
<li>The cryptographic signature MUST be valid.</li>
<li>If a <code>proofPurpose</code> exists, it MUST be a valid value
per the cryptographic suite.</li>
<li>
If the cryptographic suite expects a <code>proofPurpose</code>,
it MUST exist and be a valid value (such as
<code>credentialIssuance</code>) per the cryptographic suite.
</li>
</ul>

<p class="note">
Expand Down