Skip to content

Commit

Permalink
Fix normative requirements for statusPurpose in status list.
Browse files Browse the repository at this point in the history
  • Loading branch information
msporny committed Dec 30, 2023
1 parent 07b37db commit 3a0f98e
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -475,8 +475,8 @@ <h3>BitstringStatusListCredential</h3>
<tr>
<td>credentialSubject.statusPurpose</td>
<td>
The purpose of the status entry MUST be a string. While the value of the
string is arbitrary, the following values MUST be used for their intended
The purpose of the status entry MUST be one or more strings. While the value of
each string is arbitrary, the following values MUST be used for their intended
purpose:
<table class="simple">
<thead>
Expand Down Expand Up @@ -722,8 +722,9 @@ <h3>Validate Algorithm</h3>
verifications fail, return a validation error.
</li>
<li>
Verify that the |status purpose| matches the
`statusPurpose` value in the |statusListCredential|.
Verify that the |status purpose| matches a `statusPurpose` value in the
|statusListCredential|. Note: The |statusListCredential| might contain multiple
status purposes in a single list.
</li>
<li>
Let |compressed bitstring| be the value of the
Expand Down

0 comments on commit 3a0f98e

Please sign in to comment.