W3C home > Mailing lists > Public > public-tracking@w3.org > February 2012

(unknown charset) Re: ACTION-86: Write a clarification of dnt:c to apply to never-tracked resources

From: (unknown charset) Matthias Schunter <mts@zurich.ibm.com>
Date: Tue, 07 Feb 2012 14:39:11 +0100
Message-ID: <4F31297F.6080907@zurich.ibm.com>
To: (unknown charset) public-tracking@w3.org
Hi Nick,

thanks for this proposal.

I believe that the current header spec covers this case by means of
the header response that says that a resource does not do any tracking
(beyond what might be permitted for third parties under DNT;1).

This corresponds to your text except that your text "except in
aggregated and anonymous form" is now replaced by a pointer to the
compliance spec.

Sites can then decide whether this resource is cache-able or not. Note
that cacheability and use-for-tracking are orthogonal since cached
resources can also be used for tracking (e.g., URL specific to user).

As a consequence, I suggest to keep these two values separate
  - DNT Response header
  - Cache controls

Other opinions?


On 2/1/2012 4:55 PM, Nicholas Doty wrote:
> This action/change may have been obviated by the revised response
> header
> (http://lists.w3.org/Archives/Public/public-tracking/2012Jan/0279.html) which
> explicitly distinguishes between cached objects and not tracking. In
> case the original
> proposal (http://lists.w3.org/Archives/Public/public-tracking/2011Nov/0067.html) is
> still relevant, I would propose a change as follows:
> Instead of dnt-cached:
>> dnt-no-tracking = n
> *dnt-no-tracking* indicates that this resource is not used for
> tracking. The resource may or may not be cached but any information
> gained by the server about the user's interaction will not be
> retained, except in aggregated and anonymous form.
> This text might instead explicitly refer to the definition of
> "absolutely not tracking" (ISSUE-119) once we have text there.
> Thanks,
> Nick
Received on Tuesday, 7 February 2012 13:45:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:38:33 UTC