- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Wed, 9 Oct 2013 12:58:56 -0700
- To: Matthias Schunter (Intel Corporation) <mts-std@schunter.org>
- Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
On Oct 9, 2013, at 10:36 AM, Matthias Schunter (Intel Corporation) wrote: > Hi Team, > > during our call, it seemed that the group was converging on a consensus for this definition of tracking (option 5 by Roy): > > Tracking is the collection of data across multiple parties' domains or services and retention of that data in a > form that remains attributable to a specific user, user agent, or device. > > It is our "old" definition - corrected for grammar. > > Questions: > (a) Are there further required improvements that we need to introduce? Note that this definition is indirectly dependent on the equally old definition of service provider, which states "An outsourced service provider is considered to be the same party as its client if ..." so if we intend to change the SP definition later, we may need to directly address service providers here. > (b) Are there participants that cannot live with this style/type of definition (assuming we can provide the required final fine-tuning)? I still prefer my other proposal (1). There are several problems with the above definition: 1) users aren't aware of parties (ownership) 2) "collection of data across multiple parties' domains" is ambiguous; does it refer to: a) receiving data via multiple domains, or b) receiving data at one domain that includes information about activity at other domains, or c) both? 3) why "domains or services"? domain ownership doesn't limit the number of parties receiving data via that domain. Resources is the HTTP term. These problems are all addressed in proposal (1). ....Roy
Received on Wednesday, 9 October 2013 19:59:19 UTC