- From: Richard Barnes <rbarnes@bbn.com>
- Date: Mon, 18 Mar 2013 12:15:13 -0400
- To: Harry Halpin <hhalpin@w3.org>
- Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Fine with me. --Richard On Mar 15, 2013, at 11:05 AM, Harry Halpin <hhalpin@w3.org> wrote: > After discussion with the W3C, chair, and editors, I propose that we extend the current charter for 9 months. > > We also, since it is a deliverable at risk, will clarify the charter by changing this sentence in the charter as well [1]. > > "The mission of the Web Cryptography Working Group, part of the Security Activity, is to define a high-level API providing common cryptographic functionality to Web Applications." > > to > > "The mission of the Web Cryptography Working Group, part of the Security Activity, is to define a API providing common cryptographic functionality to Web Applications." > > Thus deleting the word "high-level". I still hope we can deliver something high-level personally, but that is obviously a lower priority than getting the low-level, and thus that deliverable is risk. > > Note we can go to Last Call *ahead* of schedule if things move quickly. > > Everything else will remain in scope using the techniques given in the charter, but we must be much tighter around use-cases for secondary features. > > If there are any concerns or objections, please put them to the mailing list. We'll try to get consensus on this the next meeting! > > cheers, > harry > > > [1] http://www.w3.org/2011/11/webcryptography-charter.html
Received on Monday, 18 March 2013 16:15:42 UTC