W3C home > Mailing lists > Public > public-webcrypto@w3.org > February 2016

[W3C Web Crypto WG] Take away from our call on 22nd of February

From: GALINDO Virginie <Virginie.Galindo@gemalto.com>
Date: Tue, 23 Feb 2016 11:36:18 +0000
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <540E99C53248CE468F6F7702588ABA2A0144F792B7@A1GTOEMBXV005.gto.a3c.atos.net>
Dear all,

For the ones who were not able to attend the call yesterday, here is a take away :

-          The WG needs to progress on the Web Crypto API and align with the current implementations,

-          A possible plan is to develop the test cases and make sure implementations are testes extensively, so that we can identify the gap between implementations and specification,

-          In any case, an exact status of the implementations is required - but none of the traditional implementers showed up for the call,

-          It has been suggested that we ask the director a 6 months extension in order to finalize the work,

-          The specification will now be worked under github repository.

Next calls :

-          29 of February for an informal session in collecting/improving tests and migrating into the W3C test framework

-          7th of March : regular WG call

-          14th of March : informal test session

-          21st of March : regular WG call (to be confirmed, as overlapping with W3C AC meeting in Boston)

Again, this API is the result of long sustainable effort from all of you, we are closed to finalize it, involvement of everyone would be highly appreciated.

Chair of the Web Crypto WG

This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Received on Tuesday, 23 February 2016 11:36:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 23 February 2016 11:36:51 UTC