- From: Michael[tm] Smith <mike@w3.org>
- Date: Sun, 3 Apr 2016 03:41:36 +0900
- To: GALINDO Virginie <Virginie.Galindo@gemalto.com>
- Cc: "public-web-security@w3.org" <public-web-security@w3.org>, Wendy Seltzer <wseltzer@w3.org>
- Message-ID: <20160402184136.GR21361@sideshowbarker.net>
GALINDO Virginie <Virginie.Galindo@gemalto.com>, 2016-04-02 18:05 +0000: > Archived-At: <http://www.w3.org/mid/540E99C53248CE468F6F7702588ABA2A0146BE84A3@A1GTOEMBXV005.gto.a3c.atos.net> > > Dear all, > > In case the topic of Hardware Security WG was of interest for you... > > Note that, based on the recent W3C members review of the Hardware > Security WG, decision has been made to create a CG, in order to improve > use cases and start drafting APIs. Do not hesitate to support and join > the CG here : > http://www.w3.org/community/groups/proposed#hb-secure-services Before launching that CG I would like to suggest you stop and take some time to consider instead taking the idea to the Web Platform Incubator Community Group (WICG). https://www.w3.org/community/wicg/ The WICG already has 139 participants, including multiple representatives from all the major browser-engine projects. So if the goals of the Hardware Based Secure Services effort include developing an API to be natively implemented in browsers, many of the browser-engine reps and other people who could help you—people experienced with making new Web-technologies ideas into reality—are already gathered together in the WICG exactly for the purpose of incubating ideas like this one. I think you will have difficulty attracting a similar level of participation from browser implementors to an entirely new CG, so I really think you should seriously consider taking it to the WICG first. That would not preclude you from later launching a new specific CG for it after it has matured further. —Mike > -----Original Message----- > > The Hardware Based Secure Services Community Group has been proposed: -- Michael[tm] Smith https://people.w3.org/mike
Received on Saturday, 2 April 2016 18:42:02 UTC