W3C home > Mailing lists > Public > public-sysapps@w3.org > June 2012

Re: updated draft charter

From: Robin Berjon <robin@berjon.com>
Date: Wed, 6 Jun 2012 22:05:32 +0200
Cc: Dave Raggett <dsr@w3.org>, W3C SysApps <public-sysapps@w3.org>
Message-Id: <8AC06A96-36AE-47C1-8054-8EBE37A03811@berjon.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>
On Jun 6, 2012, at 19:30 , SULLIVAN, BRYAN L wrote:
> [bryan] Does "system settings" mean this is unspecified, or would we define requirements at least? The point of the API I recommended is that we need a semantic, normative way for apps to make privacy assertions and for the user to accept them in informed consent. The management of privacy preferences on a system wide basis I agree is a detail of system settings, but will there be an API for that? If there isn't I think it will be difficult to promote a consistent privacy experience for users, i.e. the experience on different devices may vary widely. We would like to avoid that by providing this as an appropriately permitted app that can be deployed across different Web-based devices.

I don't want to presume of the shape that it will take at this point. I think that the important thing to note is that this falls under the scope of system settings. Beyond that, whether system settings look like a regular preferences API with some preferences being specified with defined, required behaviour, or if it's a bunch of different small APIs, is really up to the group to decide. I suspect it will be the former, and I would very much support it including mandatory privacy settings, but I don't believe that that ought be solved now (the sooner we charter, the sooner the group can address that :)

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 6 June 2012 20:06:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 June 2012 20:06:02 GMT