CREDENTIAL: Downgrade the Credentials CG interop from an 'issue' to a 'note'.

Author: mikewest

specs/credentialmanagement/index.html

@@ -3283,7 +3283,7 @@ <h2 class="heading settled" data-level="9" id="future-work"><span class="secno">
     <p>Baby steps.</p>
 
 
-    <div class="issue" id="issue-9c0b1540"><a class="self-link" href="#issue-9c0b1540"></a>
+    <div class="note" role="note">
     Groups like the
     <a href="http://www.w3.org/Payments/IG/">Web Payments IG</a>
     and the
@@ -3295,21 +3295,7 @@ <h2 class="heading settled" data-level="9" id="future-work"><span class="secno">
     and
     <a href="http://opencreds.org/specs/source/use-cases/">Credentials CG Use Cases</a>,
     and anticipate extending the API in a separate document to solve a different
-    set of problems than WebAppSec is currently chartered to deal with.  We
-    should keep track of this work as it progresses and make appropriate
-    references to any technical reports which may assist in understanding and
-    implementing this report, as appropriate, when this document is ready to
-    transition to Recommendation status.
-
-
-     <p>It’s not yet clear whether the API proposed in this document allows these
-    and other groups to elegantly address the problems they’re interested in
-    solving. We may wish to adjust portions of the API before advancing this
-    document to REC in order to ensure clean extensibility into these other
-    areas.</p>
-     
-  
-    </div>
+    set of problems than WebAppSec is currently chartered to deal with.  </div>
 </section>
 
 </main>
@@ -3689,32 +3675,5 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
    <div class="issue"> Currently, we’re not protecting requests with opaque bodies from
   Service Worker interception. Should we?<a href="#issue-be0db764"> ↵ </a></div>
    <div class="issue"> Add some thoughts here about when and how the API
-  should be used, especially with regard to <code class="idl"><a data-link-type="idl" href="#dom-credentialrequestoptions-suppressui">suppressUI</a></code>. <a href="https://github.com/w3c/webappsec/issues/290">&lt;https://github.com/w3c/webappsec/issues/290></a><a href="#issue-e1d9f1af"> ↵ </a></div>
-   <div class="issue">
-    Groups like the
-    <a href="http://www.w3.org/Payments/IG/">Web Payments IG</a>
-    and the
-    <a href="https://www.w3.org/community/credentials/">Credentials CG</a>
-    have expressed interest in extending the API defined in this document in
-    order to address use cases beyond those outlined in <a href="#use-cases">§1.1 Use Cases</a>. They’ve
-    documented these use cases in detail in
-    <a href="http://www.w3.org/TR/web-payments-use-cases/">Web Payments Use Cases 1.0</a>
-    and
-    <a href="http://opencreds.org/specs/source/use-cases/">Credentials CG Use Cases</a>,
-    and anticipate extending the API in a separate document to solve a different
-    set of problems than WebAppSec is currently chartered to deal with.  We
-    should keep track of this work as it progresses and make appropriate
-    references to any technical reports which may assist in understanding and
-    implementing this report, as appropriate, when this document is ready to
-    transition to Recommendation status.
-
-
-    <p>It’s not yet clear whether the API proposed in this document allows these
-    and other groups to elegantly address the problems they’re interested in
-    solving. We may wish to adjust portions of the API before advancing this
-    document to REC in order to ensure clean extensibility into these other
-    areas.</p>
-    
-  <a href="#issue-9c0b1540"> ↵ </a>
-   </div></div></body>
+  should be used, especially with regard to <code class="idl"><a data-link-type="idl" href="#dom-credentialrequestoptions-suppressui">suppressUI</a></code>. <a href="https://github.com/w3c/webappsec/issues/290">&lt;https://github.com/w3c/webappsec/issues/290></a><a href="#issue-e1d9f1af"> ↵ </a></div></div></body>
 </html>

specs/credentialmanagement/index.src.html

@@ -2203,7 +2203,7 @@ <h2 id="future-work">Future Work</h2>
 
   Baby steps.
 
-  <div class="issue">
+  <div class="note">
     Groups like the
     <a href="http://www.w3.org/Payments/IG/">Web Payments IG</a>
     and the
@@ -2215,16 +2215,5 @@ <h2 id="future-work">Future Work</h2>
     and
     <a href="http://opencreds.org/specs/source/use-cases/">Credentials CG Use Cases</a>,
     and anticipate extending the API in a separate document to solve a different
-    set of problems than WebAppSec is currently chartered to deal with.  We
-    should keep track of this work as it progresses and make appropriate
-    references to any technical reports which may assist in understanding and
-    implementing this report, as appropriate, when this document is ready to
-    transition to Recommendation status.
-
-    It's not yet clear whether the API proposed in this document allows these
-    and other groups to elegantly address the problems they're interested in
-    solving. We may wish to adjust portions of the API before advancing this
-    document to REC in order to ensure clean extensibility into these other
-    areas.
-  </div>
+    set of problems than WebAppSec is currently chartered to deal with.  </div>
 </section>