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

Re: DNT:0 and API

From: Nicholas Doty <npdoty@w3.org>
Date: Tue, 18 Sep 2012 16:49:38 -0700
Cc: Rigo Wenning <rigo@w3.org>, public-tracking@w3.org, Mike O'Neill <michael.oneill@baycloud.com>
Message-Id: <086A7721-623E-44F9-8EAD-7698BCFCEAE7@w3.org>
To: David Singer <singer@apple.com>
On Sep 17, 2012, at 2:07 PM, David Singer <singer@apple.com> wrote:
> I think this is possible today, though it's the first I recall thinking about it.  The site would detect a visit with no DNT header, and asks you for an exception (and then the usual exception processing goes on).
> 
> I guess if a site wants to do this, it should work, and we should make sure nothing has been written that implies the converse.  Unless there is a snag I ain't seeing.
> 
>> On Thursday 13 September 2012 12:07:19 Mike O'Neill wrote:
>>> The exception API could be amended slightly to make the UA pop up
>>> a UI if DNT is unset. In jurisdictions needing explicit consent
>>> (like EU), publishers could be required by regulators to use that
>>> form of the API (i.e. if DNT is unset then ask the user how they
>>> want to handle it, e.g. leave it unset or specify 1 or 0).

http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#exceptions-when-not-enabled

Section 6.9, "Exceptions without a DNT header", in the current draft was written in part to enable just this functionality. User agents may expose the JS exception API methods to a site even if DNT is unset, and then use those preferences to subsequently send a DNT:0 header.

(I wrote this section, at the suggestion of Shane, I believe.)

Thanks,
Nick
Received on Tuesday, 18 September 2012 23:49:43 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 June 2013 10:11:34 UTC