- From: Rigo Wenning <rigo@w3.org>
- Date: Sat, 09 Mar 2013 19:20:58 +0100
- To: Haakon Bratsberg <haakonfb@opera.com>
- Cc: public-tracking-international@w3.org
Haakon, On Monday 25 February 2013 11:06:38 Haakon Bratsberg wrote: > @Rigo: It is not clear to me what "Data classes for DNT :0 - Editor > and next steps" is about. When defining DNT:0 we have to tell people what is potentially collected. At the difference of P3P, DNT is a fixed bucket. So we have to define what DNT:0 data collection may encompass as the consent has to be specific. The idea is to list data classes as defined in the P3P data schema (e.g. clickstream data, uniqueID etc). This should account for 99% of the normal cases (advertisement, market research, OBA, user based analytics, personalization etc) In case somebody goes beyond that, especially for sensitive data (Art. 8), there must be some additional hint. This could be done by some UI requirements for the exception mechanism. (Note that this is not browser UI but service side javascript, so in scope for the charter and of type implementation - help). So it is related to the definition of DNT:0 --Rigo
Received on Saturday, 9 March 2013 18:21:27 UTC