W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2011

Feature Request Access Containers

From: Robin Berjon <robin@berjon.com>
Date: Fri, 27 May 2011 12:25:40 +0200
Message-Id: <C21CDD00-728D-4588-BA21-211C7CA9C08A@berjon.com>
To: public-device-apis@w3.org
Hi all,

as mentioned before and discussed in more detail here and there, I've been mulling over a way of doing bulk feature requests (as in the existing Permissions draft) but coupled with a way to provide XSS mitigation. Some of the feedback so far has been positive, and some negative. This is an attempt to describe it somewhat better to see if it sticks or sinks.

You can read it at:

    http://w3c-test.org/dap/proposals/request-feature/

This is just a personal proposal. It is endorsed by no one at all. It is quite sketchy in several places but hopefully the idea should at least be clear. There are two examples, one using the approach that is currently deployed in browsers, and the other with the proposed system (which naturally won't run anywhere, but you can peruse the very few differences).

I've created a "proposals" directory in our brand new hg repository (thanks Dom!). I'd like to suggest that people here can simply use that to freely store proposals that are not endorsed by the group so that we have a location to access them easily (as Dom explained, anyone in the WG can write there with Mercurial, simply by using their existing W3C credentials  and it should go through corporate firewalls).

If you see bugs in the document's rendering, please report them to me. I've been using ReSpec v2 and there are certainly some kinks to work out.

Feedback much welcome!

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Friday, 27 May 2011 10:26:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:20 GMT