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

Tracking Preference Expression Spec Suggestion

From: Andy K <akahl@evidon.com>
Date: Thu, 12 Apr 2012 11:46:24 -0500
Message-ID: <CA+TcBbWzFcmESaXszu6QpAEP=t2T1Nq0YGR8L6riMve5aaxZ5A@mail.gmail.com>
To: public-tracking@w3.org
Cc: "Colin O'Malley" <colin@evidon.com>
Hello all - Andy Kahl, product manager with Evidon here. I've been
following the progress of the Tracking Protection Expression specification
closely, and let me thank the group from the start for the quality work
you've done.

I have a suggestion that relates to section 6 (working from the 2012-03-13
working draft), titled Site-specific Exceptions. This section generally
deals with the notion that the DNT preference has been enabled in a browser
and an exception should be made - that is - DNT is set to 1 by policy but
should be set to 0 in a specific case.

However, there is no opposite exception discussed - that is - if no
previous DNT preference has been expressed, but a user would like to send a
DNT expression to a specific site/domain. I propose that this notion of DNT
inclusion (rather than exception), available whether or not they've made
prior user-agent policy decisions,  be captured in the document. This woud
enable (and encourage) context-based solutions like the platform Evidon
provides to adopt the DNT header along with current cookie-based opt-outs,
without relying on the user to make a top-level browser configuration
decision about DNT.

It appears that many of the lower-level implementation questions around a
concept like this are left to those who would execute (that is, the browser
manufacturers), so I'll refrain from making those kinds of suggestions
here. Please let me know if more detail along those lines is appropriate.

Thanks again for your hard work, and in advance for your consideration.


*Andy Kahl*
Senior Product Manager

c. 408.931.0573



twitter: @evidon

(image/png attachment: image002.png)

Received on Thursday, 12 April 2012 16:49:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:44:47 UTC