- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Wed, 7 Mar 2012 06:30:39 -0800
- To: Jonathan Mayer <jmayer@stanford.edu>
- Cc: Tracking Protection Working Group WG <public-tracking@w3.org>
On Mar 7, 2012, at 5:54 AM, Jonathan Mayer wrote: > Roy, > > Clarifying question. Does your proposal prohibit: > 1) *collecting* information that *could be* used for correlation of browsing activity, By *collecting*, I assume you mean "receiving in the request". Not directly. It prevents use of what is collected for tracking, correlation, or combining of data and it prevents assigning an identifier for future tracking, except as stated for the limited exemptions in compliance, first-party service, and stuff that has prior consent. > 2) *collecting* information that *is* used for correlation of browsing activity, or It prohibits use or retention for correlation when DNT is on, yes, except as stated for the limited exemptions in compliance, first-party service, and stuff that has prior consent. > 3) *using* information to correlate browsing activity? Yes, when DNT is on there is no correlation allowed. > My initial read was #1. But on a re-read and in follow-on discussion, there seem to be suggestions of #2 and #3. Note that there is very little that the server can do about receiving data other than not causing it to be set on prior requests. The client can, of course, clear their cookies or enable private browsing after turning on DNT, if that is a concern. ....Roy
Received on Wednesday, 7 March 2012 14:31:09 UTC