Add a note to Algorithms clearly specifying that everything should be considered
authorRyan Sleevi <sleevi@google.com>
Sun, 27 Jan 2013 21:01:08 -0800
changeset 33 f332b333d1dd
parent 32 5f50dc350a2c
child 34 bf7653fa8a61
Add a note to Algorithms clearly specifying that everything should be considered
a "feature at risk".

No algorithms are required to be implemented, but any algorithms that are
recgonized by the WG should have interoperability between user agents. As such,
they're all at risk until implementors provide feedback or implement.
spec/Overview-WebCryptoAPI.xml
spec/Overview.html
--- a/spec/Overview-WebCryptoAPI.xml	Sun Jan 27 21:00:57 2013 -0800
+++ b/spec/Overview-WebCryptoAPI.xml	Sun Jan 27 21:01:08 2013 -0800
@@ -2271,6 +2271,19 @@
 
       <div id="algorithms" class="section">
         <h2>Algorithms</h2>
+        <div class="ednote">
+          <p>
+            Note: All algorithms listed should be considered as "features at risk",
+            barring implementors adopting them. Their inclusion in the Editor's Draft
+            reflects requests for their inclusion by members of the community, and are
+            included as an exercise to ensure the robustness of the API defined in this
+            specification.
+          </p>
+          <p>
+            As such, the list of algorithms, and the recommendations, may be significantly
+            altered in future revisions.
+          </p>
+        </div>
         <div id="recommended-algorithms" class="section">
           <h3>Recommended algorithms</h3>
           <p class="norm">This section is non-normative</p>
@@ -2306,7 +2319,8 @@
             </li>
             <li><a href="#aes-cbc">AES-CBC</a></li>
           </ul>
-          <p>To see the results of test-cases between implementations, please see the [@@Upcoming]
+          <p>
+            To see the results of test-cases between implementations, please see the [@@Upcoming]
             Web Cryptography Test Cases Working Group.
           </p>
         </div>
--- a/spec/Overview.html	Sun Jan 27 21:00:57 2013 -0800
+++ b/spec/Overview.html	Sun Jan 27 21:01:08 2013 -0800
@@ -49,7 +49,7 @@
 communications.
       </p>
   
-      <div class="ednote"><div class="ednoteHeader">Editorial note</div><p>There are 24 further editorial notes in the document.</p></div>
+      <div class="ednote"><div class="ednoteHeader">Editorial note</div><p>There are 25 further editorial notes in the document.</p></div>
     </div>
 
     <div class="section">
@@ -2280,6 +2280,19 @@
 
       <div id="algorithms" class="section">
         <h2>20. Algorithms</h2>
+        <div class="ednote"><div class="ednoteHeader">Editorial note</div>
+          <p>
+            Note: All algorithms listed should be considered as "features at risk",
+            barring implementors adopting them. Their inclusion in the Editor's Draft
+            reflects requests for their inclusion by members of the community, and are
+            included as an exercise to ensure the robustness of the API defined in this
+            specification.
+          </p>
+          <p>
+            As such, the list of algorithms, and the recommendations, may be significantly
+            altered in future revisions.
+          </p>
+        </div>
         <div id="recommended-algorithms" class="section">
           <h3>20.1. Recommended algorithms</h3>
           <p class="norm">This section is non-normative</p>
@@ -2315,7 +2328,8 @@
             </li>
             <li><a href="#aes-cbc">AES-CBC</a></li>
           </ul>
-          <p>To see the results of test-cases between implementations, please see the [@@Upcoming]
+          <p>
+            To see the results of test-cases between implementations, please see the [@@Upcoming]
             Web Cryptography Test Cases Working Group.
           </p>
         </div>