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 10:56:51 +0200
Cc: Dave Raggett <dsr@w3.org>, W3C SysApps <public-sysapps@w3.org>
Message-Id: <15402763-135F-4202-AF5B-3F3BD41D8537@berjon.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>
Hi Bryan,

On Jun 6, 2012, at 05:24 , SULLIVAN, BRYAN L wrote:
> On the privacy aspects, I think it would be a good time to take a system-level approach to that across these APIs. Thus I propose that we add a Privacy API to the phase 1, with the objective of providing to the user whatever information is relevant to the privacy related characteristics of all apps on the device, and related system-wide controls for the same. For example, in the DNT discussion it's been noted that diverse implementations in web user agents (of which there can be multiple) and web-enabled apps can lead to fragmented and inconsistent representations of user privacy preferences. Thus it would be good to enable management of preferences system-wide, and ensure that the applicable signals are always used (e.g. DNT header). The objective of the API would not be to mandate any UI aspects, but to provide the ability of apps to disclose privacy related characteristics, and the ability of suitably authorized apps to read those characteristics and manage system-wide privacy settings.

I heartily agree that the entire platform should be under a consistent privacy policy  the current approach of some regulatory bodies in which Web sites have to comply to strict privacy laws (e.g. on cookies) but apps just get a free pass is nothing short of moronic.

But I didn't see this as requiring a separate API  I thought it would be part of the system settings.

Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 6 June 2012 08:57:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:09 UTC