- From: Nicholas Doty <npdoty@w3.org>
- Date: Wed, 1 Feb 2012 06:40:39 -0800
- To: Tracking Protection Working Group WG <public-tracking@w3.org>, Shane Wiley <wileys@yahoo-inc.com>
Apologies if I'm repeating questions from the f2f but I'm still uncertain about the use cases for this proposal. What would a server/publisher do differently if it received DNT:null than if it didn't receive a DNT header at all? Why would a user wish to broadcast their user agent's ability when they hadn't yet expressed a preference? —Nick On Jan 31, 2012, at 1:33 AM, Tracking Protection Working Group Issue Tracker wrote: > tracking-ISSUE-121: Should a user agent advertise its DNT ability by, e.g., sending DNT;NULL [Tracking Preference Expression (DNT)] > > http://www.w3.org/2011/tracking-protection/track/issues/121 > > Raised by: Shane Wiley > On product: Tracking Preference Expression (DNT) > > 2012-01-30 Shane said: > > <non-normative> > As many User Agents may fall outside of the large web browser vendors, such as Apps, Toolbars, Custom Web Kits, etc., it will be helpful for publishers to receive a signal that a User Agent supports DNT even when a user has not yet provided a preference. > > <normative> > User Agents SHOULD provide a null DNT signal if the user has not yet provided a preference and the User Agent supports DNT. > As many User Agents may fall outside of the large web browser vendors, such as Apps, Toolbars, Custom Web Kits, etc., it will be helpful for publishers to receive a signal that a User Agent supports DNT even when a user has not yet provided a preference. > > <normative> > User Agents SHOULD provide a null DNT signal if the user has not yet provided a preference and the User Agent supports DNT.
Received on Wednesday, 1 February 2012 14:40:44 UTC