Skip to content

Commit 673641e

Browse files
mspornymsporny
committed
Update spec to use new name "BitstringStatusList".
1 parent 875fece commit 673641e

File tree

1 file changed

+26
-26
lines changed

1 file changed

+26
-26
lines changed

‎index.html‎

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<!DOCTYPE html>
22
<html>
33
<head>
4-
<title>Bit String Status List v1.0</title>
4+
<title>Bitstring Status List v1.0</title>
55
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
66
<!--
77
=== NOTA BENE ===
@@ -271,7 +271,7 @@ <h2>Data Model</h2>
271271
</p>
272272

273273
<section>
274-
<h3>BitStringStatusListEntry</h3>
274+
<h3>BitstringStatusListEntry</h3>
275275

276276
<p>
277277
When an <a>issuer</a> desires to enable status information for a
@@ -297,14 +297,14 @@ <h3>BitStringStatusListEntry</h3>
297297
credential</a>. It MUST NOT be the URL for the status list. The value is
298298
not used during the verification or validation process, and does not need to be
299299
related to the `statusListCredential` value. If necessary, the value can be
300-
used to uniquely identify the `BitStringStatusListEntry` object, such as when it is
300+
used to uniquely identify the `BitstringStatusListEntry` object, such as when it is
301301
stored in a database.
302302
</td>
303303
</tr>
304304
<tr>
305305
<td>type</td>
306306
<td>
307-
The <code>type</code> property MUST be <code>BitStringStatusListEntry</code>.
307+
The <code>type</code> property MUST be <code>BitstringStatusListEntry</code>.
308308
</td>
309309
</tr>
310310
<tr>
@@ -353,7 +353,7 @@ <h3>BitStringStatusListEntry</h3>
353353
The <code>statusListCredential</code> property MUST be a URL to a
354354
<a>verifiable credential</a>. When the URL is dereferenced, the resulting
355355
<a>verifiable credential</a> MUST have <code>type</code> property that
356-
includes the <code>BitStringStatusListCredential</code> value.
356+
includes the <code>BitstringStatusListCredential</code> value.
357357
</td>
358358
</tr>
359359
</tbody>
@@ -371,13 +371,13 @@ <h3>BitStringStatusListEntry</h3>
371371
<span class="highlight">"credentialStatus": [
372372
{
373373
"id": "https://example.com/credentials/status/3#94567"
374-
"type": "BitStringStatusListEntry",
374+
"type": "BitstringStatusListEntry",
375375
"statusPurpose": "revocation",
376376
"statusListIndex": "94567",
377377
"statusListCredential": "https://example.com/credentials/status/3"
378378
}, {
379379
"id": "https://example.com/credentials/status/4#23452"
380-
"type": "BitStringStatusListEntry",
380+
"type": "BitstringStatusListEntry",
381381
"statusPurpose": "suspension",
382382
"statusListIndex": "23452",
383383
"statusListCredential": "https://example.com/credentials/status/4"
@@ -393,7 +393,7 @@ <h3>BitStringStatusListEntry</h3>
393393
</section>
394394

395395
<section>
396-
<h3>BitStringStatusListCredential</h3>
396+
<h3>BitstringStatusListCredential</h3>
397397

398398
<p>
399399
When a status list is published, the result is a <a>verifiable
@@ -416,15 +416,15 @@ <h3>BitStringStatusListCredential</h3>
416416
The <a>verifiable credential</a> that contains the status list MAY
417417
express an <code>id</code> property that matches the value specified in
418418
<code>statusListCredential</code> for the corresponding
419-
<code>BitStringStatusListEntry</code> (see <a href="#bitstringstatuslistentry"></a>).
419+
<code>BitstringStatusListEntry</code> (see <a href="#bitstringstatuslistentry"></a>).
420420
</td>
421421
</tr>
422422
<tr>
423423
<td>type</td>
424424
<td>
425425
The <a>verifiable credential</a> that contains the status list MUST
426426
express a <code>type</code> property that includes the
427-
<code>BitStringStatusListCredential</code> value.
427+
<code>BitstringStatusListCredential</code> value.
428428
</td>
429429
</tr>
430430
<tr>
@@ -449,7 +449,7 @@ <h3>BitStringStatusListCredential</h3>
449449
<td>credentialSubject.type</td>
450450
<td>
451451
The <code>type</code> of the credential <a>subject</a>, which is the
452-
status list, MUST be <code>BitStringStatusList</code>.
452+
status list, MUST be <code>BitstringStatusList</code>.
453453
</td>
454454
</tr>
455455
<tr>
@@ -585,18 +585,18 @@ <h3>BitStringStatusListCredential</h3>
585585
</tbody>
586586
</table>
587587

588-
<pre class="example nohighlight" title="Example BitStringStatusListCredential">
588+
<pre class="example nohighlight" title="Example BitstringStatusListCredential">
589589
{
590590
"@context": [
591591
"https://www.w3.org/ns/credentials/v2"
592592
],
593593
"id": "<span class="highlight">https://example.com/credentials/status/3</span>",
594-
"type": ["VerifiableCredential", "<span class="highlight">BitStringStatusListCredential</span>"],
594+
"type": ["VerifiableCredential", "<span class="highlight">BitstringStatusListCredential</span>"],
595595
"issuer": "did:example:12345",
596596
"validFrom": "2021-04-05T14:27:40Z",
597597
"credentialSubject": {
598598
"id": "https://example.com/status/3#list",
599-
"type": "<span class="highlight">BitStringStatusList</span>",
599+
"type": "<span class="highlight">BitstringStatusList</span>",
600600
"statusPurpose": "<span class="highlight">revocation</span>",
601601
"encodedList": "<span class="highlight">H4sIAAAAAAAAA-3BMQEAAADCoPVPbQwfoAAAAAAAAAAAAAAAAAAAAIC3AYbSVKsAQAAA</span>"
602602
},
@@ -606,18 +606,18 @@ <h3>BitStringStatusListCredential</h3>
606606
<p class="issue" data-number="73" title="Design of multiple status messages is not finalized.">
607607
The Working Group is still discussing the unification of a design between status lists with a single state (such as "revoked" or "suspended") and status lists with multiple states (exposed via a series of status messages). We are seeking implementer feedback on what a unified design should look like from an ease of implementation, privacy, and security standpoint.
608608
</p>
609-
<pre class="example nohighlight" title="Example BitStringStatusListCredential">
609+
<pre class="example nohighlight" title="Example BitstringStatusListCredential">
610610
{
611611
"@context": [
612612
"https://www.w3.org/ns/credentials/v2"
613613
],
614614
"id": "<span class="highlight">https://example.com/credentials/status/3</span>",
615-
"type": ["VerifiableCredential", "<span class="highlight">BitStringStatusListCredential</span>"],
615+
"type": ["VerifiableCredential", "<span class="highlight">BitstringStatusListCredential</span>"],
616616
"issuer": "did:example:12345",
617617
"validFrom": "2021-04-05T14:27:40Z",
618618
"credentialSubject": {
619619
"id": "https://example.com/status/3#list",
620-
"type": "<span class="highlight">BitStringStatusList</span>",
620+
"type": "<span class="highlight">BitstringStatusList</span>",
621621
"ttl": 500,
622622
"statusPurpose": "<span class="highlight">status</span>",
623623
"reference": "https://example.org/status-dictionary/",
@@ -650,7 +650,7 @@ <h3>Generate Algorithm</h3>
650650
<p>
651651
The following process, or one generating the exact output, MUST be followed
652652
when producing a
653-
<a href="#bitstringstatuslistcredential">BitStringStatusListCredential</a>:
653+
<a href="#bitstringstatuslistcredential">BitstringStatusListCredential</a>:
654654
</p>
655655

656656
<ol class="algorithm">
@@ -660,7 +660,7 @@ <h3>Generate Algorithm</h3>
660660
</li>
661661
<li>
662662
Let <strong>RLC</strong> be an unsigned
663-
<a href="#bitstringstatuslistcredential">BitStringStatusListCredential</a>
663+
<a href="#bitstringstatuslistcredential">BitstringStatusListCredential</a>
664664
without the <code>encodedList</code> property set.
665665
</li>
666666
<li>
@@ -684,14 +684,14 @@ <h3>Validate Algorithm</h3>
684684
<p>
685685
The following process, or one generating the exact output, MUST be followed
686686
when validating a <a>verifiable credential</a> that is contained in a
687-
<a href="#bitstringstatuslistcredential">BitStringStatusListCredential</a>:
687+
<a href="#bitstringstatuslistcredential">BitstringStatusListCredential</a>:
688688
</p>
689689

690690
<ol class="algorithm">
691691
<li>
692692
Let <strong>credentialToValidate</strong> be a <a>verifiable credential</a>
693693
containing a <code>credentialStatus</code> entry that is a
694-
<a href="#bitstringstatuslistentry">BitStringStatusListEntry</a>.
694+
<a href="#bitstringstatuslistentry">BitstringStatusListEntry</a>.
695695
</li>
696696
<li>
697697
Let <strong>status purpose</strong> be the value of <code>statusPurpose</code>
@@ -710,12 +710,12 @@ <h3>Validate Algorithm</h3>
710710
<li>
711711
Let <strong>compressed bitstring</strong> be the value of the
712712
<code>encodedList</code> property of the
713-
<a href="#bitstringstatuslistcredential">BitStringStatusListCredential</a>.
713+
<a href="#bitstringstatuslistcredential">BitstringStatusListCredential</a>.
714714
</li>
715715
<li>
716716
Let <strong>credentialIndex</strong> be the value of the
717717
<code>statusListIndex</code> property of the
718-
<a href="#bitstringstatuslistentry">BitStringStatusListEntry</a>.
718+
<a href="#bitstringstatuslistentry">BitstringStatusListEntry</a>.
719719
</li>
720720
<li>
721721
Generate a <strong>revocation bitstring</strong> by passing
@@ -987,7 +987,7 @@ <h2>Revocable Verifiable Credential</h2>
987987
"validFrom": "2021-04-05T14:27:42Z",
988988
<span class="highlight">"credentialStatus": {
989989
"id": "https://example.com/credentials/status/3#94567",
990-
"type": "BitStringStatusListEntry",
990+
"type": "BitstringStatusListEntry",
991991
"statusPurpose": "revocation",
992992
"statusListIndex": "94567",
993993
"statusListCredential": "https://example.com/credentials/status/3"
@@ -1010,12 +1010,12 @@ <h2>Status List Verifiable Credential</h2>
10101010
"https://www.w3.org/ns/credentials/examples/v2"
10111011
],
10121012
"id": "<span class="highlight">https://example.com/credentials/status/3</span>",
1013-
"type": ["VerifiableCredential", "<span class="highlight">BitStringStatusListCredential</span>"],
1013+
"type": ["VerifiableCredential", "<span class="highlight">BitstringStatusListCredential</span>"],
10141014
"issuer": "did:example:12345",
10151015
"validFrom": "2021-04-05T14:27:40Z",
10161016
"credentialSubject": {
10171017
"id": "https://example.com/status/3#list",
1018-
"type": "<span class="highlight">BitStringStatusList</span>",
1018+
"type": "<span class="highlight">BitstringStatusList</span>",
10191019
"statusPurpose": "<span class="highlight">revocation</span>",
10201020
"encodedList": "<span class="highlight">H4sIAAAAAAAAA-3BMQEAAADCoPVPbQwfoAAAAAAAAAAAAAAAAAAAAIC3AYbSVKsAQAAA</span>"
10211021
}

0 commit comments

Comments
 (0)