add issue flag

mprorock · msporny · msporny · commit e5e3681a10d8 · 2023-06-26T14:59:03.000-04:00
Co-authored-by: Manu Sporny &lt;msporny@digitalbazaar.com&gt;
diff --git a/index.html b/index.html
@@ -614,7 +614,10 @@ <h3>StatusList2021Credential</h3>
   "proof": { ... }
 }
         </pre>
-        <pre class="example nohighlight" title="Example StatusList2021Credential">
+                <p class="issue" data-number="73" title="Design of multiple status messages is not finalized.">
+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.
+                </p>
+                <pre class="example nohighlight" title="Example StatusList2021Credential">
           {
             "@context": [
               "https://www.w3.org/2018/credentials/v1",

Original file line number	Diff line number	Diff line change
`@@ -614,7 +614,10 @@ <h3>StatusList2021Credential</h3>`
`614`	`614`	`"proof": { ... }`
`615`	`615`	`}`
`616`	`616`	`</pre>`
`617`		`- <pre class="example nohighlight" title="Example StatusList2021Credential">`
	`617`	`+ <p class="issue" data-number="73" title="Design of multiple status messages is not finalized.">`
	`618`	`+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.`
	`619`	`+ </p>`
	`620`	`+ <pre class="example nohighlight" title="Example StatusList2021Credential">`
`618`	`621`	`{`
`619`	`622`	`"@context": [`
`620`	`623`	`"https://www.w3.org/2018/credentials/v1",`