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

RE: tracking-ISSUE-121: Should a user agent advertise its DNT ability by, e.g., sending DNT;NULL [Tracking Preference Expression (DNT)]

From: Shane Wiley <wileys@yahoo-inc.com>
Date: Wed, 1 Feb 2012 18:30:28 -0800
To: Nicholas Doty <npdoty@w3.org>
CC: Tracking Protection Working Group WG <public-tracking@w3.org>
Message-ID: <63294A1959410048A33AEE161379C8023D0C8AC1C5@SP2-EX07VS02.ds.corp.yahoo.com>
Nick,

Web-wide exception use case:

Site XYZ is launching a new service that allows a personalized social tag to be placed on the blogs of their friends.  In order to avoid Out of Band exceptions, they poll the user agent to see if DNT is supported.  If supported, Site XYZ requests a web-wide exception for the new service and records this with the User Agent.  This way the user can selectively turn DNT on or off and not affect the web-wide exception granted to Site XYZ's feature they signed-up for.

Generally, to assist the marketplace to transition to DNT, it will be helpful to have the option to proactively use site-specific and web-wide exceptions to minimize the number of Out of Band exceptions that are necessary to continue to innovate and launch new products.

- Shane

-----Original Message-----
From: Nicholas Doty [mailto:npdoty@w3.org] 
Sent: Wednesday, February 01, 2012 9:18 PM
To: Shane Wiley
Cc: Tracking Protection Working Group WG
Subject: Re: tracking-ISSUE-121: Should a user agent advertise its DNT ability by, e.g., sending DNT;NULL [Tracking Preference Expression (DNT)]

On Feb 1, 2012, at 6:03 PM, Shane Wiley wrote:
> If you feel this can be managed via the site-specific exceptions call, then I believe we're covered.

It would still be useful for us to understand your use case. Depending on the design of the JavaScript API, it should be easy to check for the capability to request a site-specific exception. But I currently wouldn't expect user agents to expose that if the Do Not Track itself weren't turned on.

> This was assigned to me at Brussels as I saw the site-specific exception value but there were many on the email list that were arguing for having DNT:<null> too.  Hopefully someone else will speak up if they want to keep this option (but I hear you loud and clear on traffic bloat).

Yes, if there are many (or any) others on the email list who have a use case here, please speak up!

Thanks,
Nick
Received on Thursday, 2 February 2012 02:31:30 UTC

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