- From: Ryan Sleevi <sleevi@google.com>
- Date: Wed, 12 Jun 2013 19:39:03 -0700
- To: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Cc: GALINDO Virginie <Virginie.GALINDO@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Thanks for pointing these out Nick. MichaelH also raised them in a private mail to the editors. I've just pushed three new changes to https://dvcs.w3.org/hg/webcrypto-api that attempt to address the issues highlighted so far Update the ECDSA sign/verify algorithm description for the "new" (read: better described) processing model https://dvcs.w3.org/hg/webcrypto-api/rev/6f99a5a25a1d Update the examples: https://dvcs.w3.org/hg/webcrypto-api/rev/a535c724d33e Rename Futures to Promises: https://dvcs.w3.org/hg/webcrypto-api/rev/c32294bc59e2 As always, the latest draft is https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html , and you can always refer to specific versions via https://dvcs.w3.org/hg/webcrypto-api/log On Tue, Jun 11, 2013 at 5:18 AM, Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com> wrote: > Hi Virgin, > > I have two editorial remarks that we probable want to address before > publishing (they are probably being addressed at the moment): > 1) They renamed Future to Promise in the DOM4 specification [1]. > Consequently , our CryptoOperation should inherit from Promise and the > methods of SubtleCrypto should return Promise<any> and the text should speak > of 'promise' instead of 'future' > 2) The examples in section '20. Javascript Example Code' still use the > EventTarget syntax, this should be updated to Promise syntax > > Kind regards, > > Nick > > 1: http://dom.spec.whatwg.org/#promises > > On 11 Jun 2013, at 00:29, GALINDO Virginie <Virginie.GALINDO@gemalto.com> > wrote: > > Dear all, > This is a kind reminder that next Monday we will formally adopt (or not) > the decision to go for next Public Working Draft on the Web Crypto API > https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html > Please review it, and make sure it is acceptable for you as it is. If it is > not, it is the right time to send your comment to the editor. > Regards, > Virginie > > > > > ________________________________ > > Inventive Designers' Email Disclaimer: > http://www.inventivedesigners.com/email-disclaimer
Received on Thursday, 13 June 2013 02:39:31 UTC