W3C home > Mailing lists > Public > public-webappsec@w3.org > December 2014

Re: [webappsec] Dec 1, Thread 1: Rechartering

From: Brad Hill <hillbrad@fb.com>
Date: Tue, 2 Dec 2014 17:41:50 +0000
To: Brad Hill <hillbrad@fb.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>, Mounir Lamouri <mounir@lamouri.fr>
Message-ID: <D0A339A4.1A45%hillbrad@fb.com>
OK, so I missed my own deadline, but did get feedback.

Can folks live with the following charter edits around Permission API to
clarify the scope?

Current:

"Permissions API

Create and advance a recommendation to allow web applications to be aware
of the status of a given permission, to know whether it is granted,
denied, or if the user will be asked whether the permission should be
granted."

Proposed:

"Permissions API

Create and advance a recommendation to allow web applications to be aware
of the status of a given permission, to know whether it is granted,
denied, or if the user will be asked whether the permission should be
granted.  This specification will expose the current state of, and allow
triggering a request for a permissions grant with an API.  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."




On 12/1/14, 10:22 AM, "Brad Hill" <hillbrad@fb.com> wrote:

>This is a time-sensitive thread: please reply before 24:00 GMT (5:00pm
>
>PST) December 1st.
>
>
>
>We have a Call for Consensus set to end today on a proposed rechartering:
>
>
>
>https://urldefense.proofpoint.com/v1/url?u=http://lists.w3.org/Archives/Pu

>blic/public-webappsec/2014Nov/0294.html&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&
>r=HU3cThGizwgsko8%2BWBMXZg%3D%3D%0A&m=IjsKJKSd1hqxj3LrZ4LrmQ1u2s4lNfZklnNM
>IUvymYc%3D%0A&s=2ccde406f235490d2d073c69f0350139fd3baf51cf22d6c98566dbae01
>486a16
>
>
>
>
>
>The draft is at:
>
>
>
>https://urldefense.proofpoint.com/v1/url?u=https://w3c.github.io/webappsec

>/admin/webappsec-charter-2015.html&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=HU3
>cThGizwgsko8%2BWBMXZg%3D%3D%0A&m=IjsKJKSd1hqxj3LrZ4LrmQ1u2s4lNfZklnNMIUvym
>Yc%3D%0A&s=8fca316892b70fd63ee0c4812ff3ae58b8982b447baf3ba96d3a9ac8e21f3ed
>2
>
>
>
>
>
>So far there has been strong assent to the proposal, with one exception:
>
>
>
>Brad Hill is concerned that the Permissions API potentially expands the
>
>scope of patent commitments necessary.
>
>https://urldefense.proofpoint.com/v1/url?u=http://lists.w3.org/Archives/Pu

>blic/public-webappsec/2014Nov/0303.html&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&
>r=HU3cThGizwgsko8%2BWBMXZg%3D%3D%0A&m=IjsKJKSd1hqxj3LrZ4LrmQ1u2s4lNfZklnNM
>IUvymYc%3D%0A&s=64e4e026f074d432aed3d96a3bf0d258f5615968bd3ff24d6ef9d223c3
>7c4b8c
>
>
>
>
>
>Mounir Lamouri responded at:
>
>https://urldefense.proofpoint.com/v1/url?u=http://lists.w3.org/Archives/Pu

>blic/public-webappsec/2014Nov/0362.html&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&
>r=HU3cThGizwgsko8%2BWBMXZg%3D%3D%0A&m=IjsKJKSd1hqxj3LrZ4LrmQ1u2s4lNfZklnNM
>IUvymYc%3D%0A&s=f08c2744173270f677f3cf12746efb3a75b871039c9e840484f8dff3c7
>472ea8
>
>
>
>
>
><hat=individual>I owe Mounir and the group a compromise proposal and am
>
>working with my team on that, expect something soon.</hat>
>
>
>
>And Mark Nottingham and Brian Smith have some concerns about the impact of
>
>suborigins:
>
>https://urldefense.proofpoint.com/v1/url?u=http://lists.w3.org/Archives/Pu

>blic/public-webappsec/2014Nov/0342.html&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&
>r=HU3cThGizwgsko8%2BWBMXZg%3D%3D%0A&m=IjsKJKSd1hqxj3LrZ4LrmQ1u2s4lNfZklnNM
>IUvymYc%3D%0A&s=f6047e46d318912e3d4bdfb4ec778f832511460054e1b8382dae07e544
>ffbd10
>
>
>
>
>
>
>
>If you have further objections, please reply to this email within the time
>
>frame indicated.
>
>
>
>-Brad Hill
>
>
>

Received on Tuesday, 2 December 2014 17:42:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:08 UTC