Re: Proposed text for privacy requirements

I would recommend starting with the declarative aspects (how does a webapp/widget declare its intent) of this, since that's something more concrete and testable. The UI aspects will be more difficult and depend upon the type of user-agent (e.g. Browser or widget engine), their UI elements ("chrome") and the current view mode of the webapp/widget (icon, chromeless, etc).
 
Bryan Sullivan | AT&T 

----- Original Message -----
From: Alissa Cooper <acooper@cdt.org>
To: Paddy Byers <paddy.byers@gmail.com>
Cc: SULLIVAN, BRYAN L (ATTCINW); Thomas Roessler <tlr@w3.org>; Dominique Hazael-Massieux <dom@w3.org>; Frederick Hirsch <frederick.hirsch@nokia.com>; W3C Device APIs and Policy WG <public-device-apis@w3.org>
Sent: Sun Mar 07 11:56:58 2010
Subject: Re: Proposed text for privacy requirements


On Mar 4, 2010, at 1:10 PM, Paddy Byers wrote:

> You're thinking of something like the Creative Commons "license  
> deed" (for example [0]) ?
>
> Thanks - Paddy
>
> [0]: http://creativecommons.org/licenses/by/3.0/



The design space is pretty vast, and the question of what gets  
represented is obviously separate from the question of how it gets  
represented. The notion of compact privacy policies has been around at  
least since P3P if not before. There have also been a number of  
efforts to develop a set of privacy icons [0][1][2]. These can get  
quite prescriptive in what they can express, but that could be a  
benefit. On the far less complex end of the spectrum, apps could just  
be given a text field in which to declare a small snippet of their  
policies in human-readable form. If this kind of policy communication  
is something we decide to pursue, it's probably worth exploring the  
whole range of options.

[0] http://identityproject.lse.ac.uk/mary.pdf

[1] https://wiki.mozilla.org/Drumbeat/Challenges/Privacy_Icons

[2] http://asset.netzpolitik.org/wp-upload/data-privacy-icons-v01.pdf

Received on Sunday, 7 March 2010 20:17:52 UTC