- From: Mark Watson <watsonm@netflix.com>
- Date: Thu, 6 Mar 2014 18:14:19 -0800
- To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <CAEnTvdD9cJUFZNgGu88XcY64jmqUf1wsOUMG9uUV2KSBGn7VJg@mail.gmail.com>
Ryan, I do not believe we should consider replacing the existing JSON import/export format with an object representation as proposed. The serialized JSON format has been stable for some time and aligns with the other formats which are also serialized objects as would be seen in a wire protocol. Introducing a new object representation aligned with JWK is a great idea as an *additional* format, not a replacement - perhaps for a future version of the specification. ...Mark ---------- Forwarded message ---------- From: <bugzilla@jessica.w3.org> Date: Thu, Mar 6, 2014 at 4:22 PM Subject: [Bug 24963] Export Key with "jwk" operations should return a JWK, rather than an ArrayBuffer To: watsonm@netflix.com https://www.w3.org/Bugs/Public/show_bug.cgi?id=24963 --- Comment #1 from Ryan Sleevi <sleevi@google.com> --- Bug filed based on this thread - http://lists.w3.org/Archives/Public/public-webcrypto/2014Mar/0059.html Specifically, http://lists.w3.org/Archives/Public/public-webcrypto/2014Mar/0063.html and http://lists.w3.org/Archives/Public/public-webcrypto/2014Mar/0064.html -- You are receiving this mail because: You are on the CC list for the bug.
Received on Friday, 7 March 2014 02:14:49 UTC