W3C home > Mailing lists > Public > public-webcrypto@w3.org > September 2012

Re: [W3C Web Crypto WG] FPWD Web Crypto API - available

From: Wendy Seltzer <wseltzer@w3.org>
Date: Thu, 13 Sep 2012 14:56:51 -0400
Message-ID: <50522C73.6040301@w3.org>
To: David Dahl <ddahl@mozilla.com>
CC: Axel Nennker <Axel.Nennker@telekom.de>, hhalpin@w3.org, Ryan Sleevi <sleevi@google.com>, Virginie GALINDO <Virginie.GALINDO@gemalto.com>, public-webcrypto@w3.org
Thanks David and Axel,

Working Drafts are static after publication, so changes will go into the
Editor's Draft (as David has already done) and go out to /TR/ in the
next public Working Draft. We can publish new Working Drafts whenever we
feel there's been significant progress, no less frequently than a
3-month heartbeat.

--Wendy

On 09/13/2012 02:20 PM, David Dahl wrote:
> I fixed this mistake in http://www.w3.org/2012/webcrypto/WebCryptoAPI/ - what is the proper way to migrate it into the WD?
> 
> David
> 
> ----- Original Message -----
> From: "David Dahl" <ddahl@mozilla.com>
> To: "Axel Nennker" <Axel.Nennker@telekom.de>, hhalpin@w3.org
> Cc: wseltzer@w3.org, "Virginie GALINDO" <Virginie.GALINDO@gemalto.com>, public-webcrypto@w3.org, "Ryan Sleevi" <sleevi@google.com>
> Sent: Thursday, September 13, 2012 12:12:55 PM
> Subject: Re: [W3C Web Crypto WG] FPWD Web Crypto API - available
> 
> Axel:
> 
> Yes, you are correct. My mistake. 
> 
> Harry:
> 
> Once I fix that in our repo, what is the process to update the published version?
> 
> David
> 
> 
> ----- Original Message -----
> From: "Axel Nennker" <Axel.Nennker@telekom.de>
> To: "Virginie GALINDO" <Virginie.GALINDO@gemalto.com>, public-webcrypto@w3.org
> Cc: wseltzer@w3.org, hhalpin@w3.org
> Sent: Thursday, September 13, 2012 8:57:33 AM
> Subject: RE: [W3C Web Crypto WG] FPWD Web Crypto API - available
> 
> In 25.2 Key Storage
> 
> var encryptionKey = window.keys.getKeyById("78966b83-b003-46ac-8122-3771e9d7f78");
> 
> 
> 
> // This key is no longer needed, I should remove it:
> 
> window.keys.removeKeyById(encryptionKey.id);
> 
> 
> 
> var otherEncryptionKey = window.keys.getKeyById("5edbeebe-bbbf-4d60-9846-8bbdb81e3215");
> 
> 
> 
> shouldn't that read
> 
> var encryptionKey = window.crypto.keys.getKeyById("78966b83-b003-46ac-8122-3771e9d7f78");
> 
> 
> 
> // This key is no longer needed, I should remove it:
> 
> window.crypto.keys.removeKeyById(encryptionKey.id);
> 
> 
> 
> var otherEncryptionKey = window.crypto.keys.getKeyById("5edbeebe-bbbf-4d60-9846-8bbdb81e3215");
> 
> instead?
> 
> 
> 
> Axel
> 
> 
> 
> -----Original Message-----
> From: GALINDO Virginie [mailto:Virginie.GALINDO@gemalto.com]
> Sent: Thursday, September 13, 2012 3:28 PM
> To: public-webcrypto@w3.org
> Cc: Wendy Seltzer; Harry Halpin
> Subject: [W3C Web Crypto WG] FPWD Web Crypto API - available
> 
> 
> 
> Dear all,
> 
> The Web Crypto API is now available under http://www.w3.org/TR/WebCryptoAPI/.
> 
> Regards,
> 
> Virginie
> 
> 
> 
> -----Original Message-----
> 
> From: GALINDO Virginie
> 
> Sent: jeudi 13 septembre 2012 07:18
> 
> To: public-webcrypto@w3.org
> 
> Cc: Wendy Seltzer; Harry Halpin
> 
> Subject: [W3C Web Crypto WG] Request transition for FPWD on Web Crypto API - approved
> 
> 
> 
> Dear all,
> 
> 
> 
> This is to inform you that the request for transition to FPWD has been approved by the domain team leader (Thomas Roessler). Next step is the migration under http://www.w3.org/TR/WebCryptoAPI/ official link. Will keep you informed.
> 
> 
> 
> 
> 
> Regards,
> 
> Virginie, gemalto
> 
> Happy Chair of Web Crypto WG
> 
> 
> 
> 


-- 
Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
http://wendy.seltzer.org/        +1.617.863.0613 (mobile)
Received on Thursday, 13 September 2012 18:57:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 September 2012 18:57:10 GMT