- From: Brad Hill <hillbrad@gmail.com>
- Date: Tue, 01 Dec 2015 00:29:59 +0000
- To: Wendy Seltzer <wseltzer@w3.org>
- Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>
- Message-ID: <CAEeYn8iFVBLmaABfLmi36-NonAHSDMnX9cQeK73qA5Udsn9LPw@mail.gmail.com>
I think this is the same document and we should update pointers. I'm working on yet another API update right now and hope to have it checked in by Wednesday, but I'll issue the CfC formally when I'm ready with that, and can update other pointers as necessary then. thanks! -Brad On Mon, Nov 30, 2015 at 2:57 PM Wendy Seltzer <wseltzer@w3.org> wrote: > Hi Brad, > > Do you think this will be a new WD of http://www.w3.org/TR/UISecurity/ > (re-setting <http://www.w3.org/TR/UISecurity/(re-setting> back to > ordinary working draft), or a separate document > stream? In any event, should we put some sort of note on the previous UI > Security work or an update at its "Latest ED" link [1] to direct people > to the new work? > > Best, > --Wendy > > [1] > http://dvcs.w3.org/hg/user-interface-safety/raw-file/tip/user-interface-safety.html > > On 11/14/2015 07:31 PM, Brad Hill wrote: > > I'll send out a more detailed agenda soon, but I've just pushed a new > > editor's draft of UISecurity and the Visibility API based on the > strategies > > that Dan Kaminsky discussed with us a few meetings ago. > > > > http://w3c.github.io/webappsec/specs/uisecurity/index.html > > > > It's very rough in terms of spec editorial polish, cross-linking, etc., > but > > hopefully gives enough of an idea of the algorithms, changes, and new API > > surface to have a good discussion. > > > > Will send out an agenda for our last noon, PST call tomorrow. > > > > -Brad > > > > > -- > Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office) > Policy Counsel and Domain Lead, World Wide Web Consortium (W3C) > http://wendy.seltzer.org/ +1.617.863.0613 (mobile) > >
Received on Tuesday, 1 December 2015 00:30:43 UTC