Merge pull request #251 from selfissued/mbj-sd-jwt-vc-at-risk

Mark uses of SD-JWT-VC as being at risk

index.html

@@ -760,8 +760,8 @@ <h2>Key Discovery</h2>
   as described in [[SD-JWT-VC]].
       </p>
 
-      <p class="issue" title="(AT RISK) Feature depends on demonstration of independent implementations" data-number="160">
-        This normative statement depends on the IETF OAUTH working group adopted draft [[SD-JWT-VC]].
+      <p class="issue" title="(AT RISK) Feature depends on demonstration of independent implementations">
+        This normative statement depends on the IETF OAuth working group draft [[SD-JWT-VC]].
         This feature is at risk and will be removed from the specification if at least
         two independent, interoperable implementations are not demonstrated.
       </p>
@@ -832,7 +832,7 @@ <h2>cnf</h2>
       </section>
 
       <section>
-      <h2>Well Known URIs</h2>
+      <h2>Well-Known URIs</h2>
       <p class="issue" data-number="160">
       The working group is currently exploring how
       <a data-cite="RFC5785#section-3">Defining Well-Known Uniform Resource Identifiers (URIs)</a>
@@ -848,6 +848,12 @@ <h2>JWT Issuer</h2>
               issuer metadata including the issuer's public keys can be retrieved using the mechanism
               defined in [[SD-JWT-VC]].
             </p>
+
+            <p class="issue" title="(AT RISK) Feature depends on demonstration of independent implementations">
+              This normative statement depends on the IETF OAuth working group draft [[SD-JWT-VC]].
+              This feature is at risk and will be removed from the specification if at least
+              two independent, interoperable implementations are not demonstrated.
+            </p>
           </section>
         </section>
         <section>