- From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Date: Thu, 13 Jun 2013 07:09:26 +0000
- To: Ryan Sleevi <sleevi@google.com>
- CC: GALINDO Virginie <Virginie.GALINDO@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <02C5CA75-1800-4C26-AB9A-3B7F04E30DCD@inventivegroup.com>
Ryan, Thank you for updating the spec! The samples look really nice with the Promise syntax. The use of bound functions for logging to the console makes it even nicer ;) . Kind regards, Nick Van den Bleeken R&D Manager Phone: +32 3 425 41 02 Office fax: +32 3 821 01 71 nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com> www.inventivedesigners.com [cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110] On 13 Jun 2013, at 04:39, Ryan Sleevi <sleevi@google.com<mailto:sleevi@google.com>> wrote: 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 ________________________________ Inventive Designers' Email Disclaimer: http://www.inventivedesigners.com/email-disclaimer
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
- image/png attachment: image003.png
Received on Thursday, 13 June 2013 07:09:58 UTC