Bug 24963 - Add note regarding outstanding JWK issue
authorRyan Sleevi <sleevi@google.com>
Tue, 18 Mar 2014 19:48:17 -0700
changeset 172 0a08958cf50f
parent 171 a70efe4807ee
child 173 be3018091622
Bug 24963 - Add note regarding outstanding JWK issue
spec/Overview-WebCryptoAPI.xml
spec/Overview.html
--- a/spec/Overview-WebCryptoAPI.xml	Wed Mar 12 17:41:46 2014 -0700
+++ b/spec/Overview-WebCryptoAPI.xml	Tue Mar 18 19:48:17 2014 -0700
@@ -1890,6 +1890,15 @@
                 </p>
               </li>
             </ol>
+            <div class="ednote">
+              <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=24963">Bug 24963</a> -
+              There is an open question as to whether/how to support importing
+              keys when format is <code>jwk</code>. As currently specified, it is a
+              JSON-encoded Javascript object, converted to a UTF-8 byte sequence, with the
+              raw bytes provided via <code>CryptoOperationData</code>. A separate
+              proposal exists to handle this via IDL, permitting importing JavaScript
+              objects directly when importing with <code>jwk</code>.
+            </div>
           </div>
 
           <div id="SubtleCrypto-method-exportKey" class="section">
@@ -1971,6 +1980,15 @@
                 </p>
               </li>
             </ol>
+            <div class="ednote">
+              <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=24963">Bug 24963</a> -
+              There is an open question as to whether/how to support exporting
+              keys when format is <code>jwk</code>. As currently specified, the result
+              is a JSON-encoded Javascript object, converted to a UTF-8 byte
+              sequence, with the raw bytes provided via an ArrayBuffer. A separate
+              proposal exists to return an actual Javascript object when exporting
+              with <code>jwk</code>.
+            </div>
           </div>
 
           <div id="SubtleCrypto-method-wrapKey" class="section">
--- a/spec/Overview.html	Wed Mar 12 17:41:46 2014 -0700
+++ b/spec/Overview.html	Tue Mar 18 19:48:17 2014 -0700
@@ -28,7 +28,7 @@
   <link rel="stylesheet" href="//www.w3.org/StyleSheets/TR/W3C-ED" type="text/css" /></head>
 
   <body>
-    <div class="head"><div><a href="http://www.w3.org/"><img src="//www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>Web Cryptography API</h1><h2>W3C Editor’s Draft <em>12 March 2014</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html">http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html</a></dd><dt>Latest Published Version:</dt><dd><a href="http://www.w3.org/TR/WebCryptoAPI/">http://www.w3.org/TR/WebCryptoAPI/</a></dd><dt>Previous Version(s):</dt><dd><a href="https://dvcs.w3.org/hg/webcrypto-api/raw-file/0fe9b34c13fb/spec/Overview.html">https://dvcs.w3.org/hg/webcrypto-api/raw-file/0fe9b34c13fb/spec/Overview.html</a></dd><dt>Editors:</dt><dd><a href="http://www.google.com/">Ryan Sleevi</a>, Google, Inc. &lt;[email protected]&gt;</dd><dd><a href="http://www.netflix.com/">Mark Watson</a>, Netflix &lt;[email protected]&gt;</dd><dt>Participate:</dt><dd><p>Send feedback to <a href="mailto:[email protected]?subject=%5BWebCryptoAPI%5D">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-webcrypto/">archives</a>), or <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=Web%20Cryptography&amp;component=Web%20Cryptography%20API%20Document">file a bug</a> 
+    <div class="head"><div><a href="http://www.w3.org/"><img src="//www.w3.org/Icons/w3c_home" width="72" height="48" alt="W3C" /></a></div><h1>Web Cryptography API</h1><h2>W3C Editor’s Draft <em>18 March 2014</em></h2><dl><dt>Latest Editor’s Draft:</dt><dd><a href="http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html">http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html</a></dd><dt>Latest Published Version:</dt><dd><a href="http://www.w3.org/TR/WebCryptoAPI/">http://www.w3.org/TR/WebCryptoAPI/</a></dd><dt>Previous Version(s):</dt><dd><a href="https://dvcs.w3.org/hg/webcrypto-api/raw-file/0fe9b34c13fb/spec/Overview.html">https://dvcs.w3.org/hg/webcrypto-api/raw-file/0fe9b34c13fb/spec/Overview.html</a></dd><dt>Editors:</dt><dd><a href="http://www.google.com/">Ryan Sleevi</a>, Google, Inc. &lt;[email protected]&gt;</dd><dd><a href="http://www.netflix.com/">Mark Watson</a>, Netflix &lt;[email protected]&gt;</dd><dt>Participate:</dt><dd><p>Send feedback to <a href="mailto:[email protected]?subject=%5BWebCryptoAPI%5D">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-webcrypto/">archives</a>), or <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=Web%20Cryptography&amp;component=Web%20Cryptography%20API%20Document">file a bug</a> 
     (see <a href="https://www.w3.org/Bugs/Public/buglist.cgi?product=Web%20Cryptography&amp;component=Web%20Cryptography%20API%20Document&amp;resolution=---">existing bugs</a>).</p></dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; view <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr />
 
     <div class="section">
@@ -44,7 +44,7 @@
         communications.
       </p>
   
-      <div class="ednote"><div class="ednoteHeader">Editorial note</div><p>There are 17 further editorial notes in the document.</p></div>
+      <div class="ednote"><div class="ednoteHeader">Editorial note</div><p>There are 19 further editorial notes in the document.</p></div>
     </div>
 
     <div class="section">
@@ -56,7 +56,7 @@
         report can be found in the <a href="http://www.w3.org/TR/">W3C technical
           reports index</a> at http://www.w3.org/TR/.
       </em></p><p>
-        This document is the 12 March 2014 <b>Editor’s Draft</b> of the
+        This document is the 18 March 2014 <b>Editor’s Draft</b> of the
         <cite>Web Cryptography API</cite> specification.
       
       Please send comments about this document to
@@ -1898,6 +1898,15 @@
                 </p>
               </li>
             </ol>
+            <div class="ednote"><div class="ednoteHeader">Editorial note</div>
+              <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=24963">Bug 24963</a> -
+              There is an open question as to whether/how to support importing
+              keys when format is <code>jwk</code>. As currently specified, it is a
+              JSON-encoded Javascript object, converted to a UTF-8 byte sequence, with the
+              raw bytes provided via <code>CryptoOperationData</code>. A separate
+              proposal exists to handle this via IDL, permitting importing JavaScript
+              objects directly when importing with <code>jwk</code>.
+            </div>
           </div>
 
           <div id="SubtleCrypto-method-exportKey" class="section">
@@ -1979,6 +1988,15 @@
                 </p>
               </li>
             </ol>
+            <div class="ednote"><div class="ednoteHeader">Editorial note</div>
+              <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=24963">Bug 24963</a> -
+              There is an open question as to whether/how to support exporting
+              keys when format is <code>jwk</code>. As currently specified, the result
+              is a JSON-encoded Javascript object, converted to a UTF-8 byte
+              sequence, with the raw bytes provided via an ArrayBuffer. A separate
+              proposal exists to return an actual Javascript object when exporting
+              with <code>jwk</code>.
+            </div>
           </div>
 
           <div id="SubtleCrypto-method-wrapKey" class="section">