- From: <frederick.hirsch@nokia.com>
- Date: Mon, 29 Sep 2014 14:06:25 +0000
- To: <public-privacy@w3.org>
- CC: <frederick.hirsch@nokia.com>, <rigo@w3.org>, <matthias.schunter@intel.com>, <frank.wagner@telekom.de>
PING members: The W3C will be holding a two-day workshop, "Workshop on Privacy and User–Centric Controls” 20–21 November 2014, Berlin, Germany. See http://www.w3.org/2014/privacyws/ The focus of the workshop is the user - how to communicate privacy implications and choices effectively to the user, how to implement usable and non-intrusive controls, and how to share information on how data will be used, shared and retained without relying on lengthy privacy documents. Goals of the workshop include relating issues and experience in the area, sharing new ideas, and to offer techniques that application developers and users might expect to be both useful and pragmatic. If you are interested in submitting a position paper, the deadline is 31 October 2014. Early registration is recommended. Please let us know of interest. Thanks regards, Frederick (Matthias, Frank and Rigo) Frederick Hirsch, Nokia @fjhirsch An excerpt from the workshop overview [[ User studies have shown that users are more interested in what sites plan to do with the data they collect rather than with the full space of possibilities arising from the use of APIs. It is unreasonable to expect end users to understand lengthy terms of conditions and privacy policies. While the Paris Workshop explored models how to delegate trust decisions, this Workshop will explore ways to directly help the user understand what is going on. This includes appropriate ways of translating complex issues involving fine grained permissions in APIs into something that users understand. The Workshop on User Centric App Controls intends to further the discussion among stakeholders of the mobile web platform, including researchers, developers and service providers. This workshop serves to investigate strategies toward better privacy protection on the Web that are effective and lead to benefits in the near term. This includes discussing basic privacy UI features that will, on the long run, create a user experience that loops with user expectations. We expect certain controls and dashboards in a car. Perhaps we can create a similar clarity for the privacy dashboard of our devices. The Workshop is user centric as it will also look at user experience, user behavior and how we can offer controls that provide the necessary transparency of privacy-affecting interactions. But it also addresses app developers and the need for usable and implementable APIs to address privacy protection within the Open Web Platform that allow developers to address user's privacy needs. State management • Improving the UI for stateful services, overview of states • Defaults for expiration of stateful situations • How to convey state information to the User • How to deal with logging and how to provide interfaces for logged data? Mobile Interfaces • Requirements for private browsing on mobile • A privacy ontology for mobile apps and their use of personal data • The value of privacy in paradigms for mobile UI • Helpers to understand the privacy impact or a privacy policy • Machine assisted lying to counter unfair data requests Controls • Selective release of personal information to apps • Controlling the geo-location interfaces, including UI challenges • enforcing data expiry • What data should remain on the device, what can be stored into the cloud? ]]
Received on Monday, 29 September 2014 14:06:57 UTC