- From: Jonathan Kingston <jonathan@jooped.com>
- Date: Tue, 25 Aug 2015 06:59:06 +0000
- To: Brad Hill <hillbrad@gmail.com>, timeless <timeless@gmail.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
- Message-ID: <CAKrjaaVSqXdRre9egw4THN1U6AeBJQ6-sGTyke7SiQHrjaEw7Q@mail.gmail.com>
+1 welcome to the group! On Tue, 25 Aug 2015 05:44 Brad Hill <hillbrad@gmail.com> wrote: > Welcome, Josh! > > As a document voted on and ratified by the entire W3C membership, I'm not > actually sure we can correct even typographic errors in a charter without a > considerable process overhead. > > I look forward to having even a small fraction of your boundless energy > and attention to detail turned in the direction of our specs! > > -Brad > > > On Mon, Aug 24, 2015 at 9:27 PM timeless <timeless@gmail.com> wrote: > >> Hi, >> I'm officially joining the WebAppSec WG (as an IE). >> >> One of the requirements for joining was that I fill out a survey: >> >> > I ... as W3C Invited Expert, >> > have reviewed the Web Application Security Working Group charter [1] >> >> I do hope to attend regular calls :) >> >> This appears to be a pair of Oxford commas: >> > This recommendation will not address user agent implementations of >> permissions, including their scope, duration, granularity, or user >> interface and experience for indicating, configuring, or asking for >> permissions. >> >> This appears to be a pair of non-Oxford conjunctions: >> > They may transclude, reference or have information flows between >> resources at the same, related or different origins. >> >> >> > Manageability >> > The WG will document and create uniform experiences for several >> undefined areas of major utility, including: >> > ... >> only this bullet ends with a period: >> > * Application awareness of features which may require explicit user >> permission to enable. >> >> >> [1] http://www.w3.org/2015/03/webappsec-charter-2015.html >> >>
Received on Tuesday, 25 August 2015 06:59:44 UTC