W3C home > Mailing lists > Public > public-tracking@w3.org > October 2013

Re: ISSUE-5: Consensus definition of "tracking" for the intro?

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Tue, 15 Oct 2013 13:08:10 +0100
To: "'Roy T. Fielding'" <fielding@gbiv.com>, "David Singer" <singer@apple.com>, "John Simpson" <john@consumerwatchdog.org>
Cc: <public-tracking@w3.org>
Message-ID: <084101cec99f$384852d0$a8d8f870$@baycloud.com>
In an off-list discussion about the compromise proposal David flagged that
it could be read to allow third-party retention of data derived from the act
of visiting a first-party site, e.g. what category of site, time of visit
etc. So a server receiving a third-party request could retain data about the
first-party resource, say a Guns & Ammo site and when it was visited, and
associate that with a unique user identifier to build up an activity


I have tried to come up with a definition that encompasses the first-party
alleviation which does not end of over-complicating what should be a simple


I now have this, though I still don't think it is as clear as the current
draft or option 4 (which I prefer) with the party qualification laid out in
the compliance section.


A transport request is any request for content delivery over the public

Transport data is data in, or derived from, a given transport request.

Tracking data is a subset of transport data which can be used to recognise
subsequent transport requests to be from the same user,  user agent, or

Tracking is the sharing of tracking data with a third-party, or its
retention by a party other than the first-party.




Received on Tuesday, 15 October 2013 12:08:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:00 UTC