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

RE: ACTION-84: Wiley to describe the reason for setting DNT=null

From: Kevin Smith <kevsmith@adobe.com>
Date: Wed, 1 Feb 2012 10:53:50 -0800
To: Shane Wiley <wileys@yahoo-inc.com>, Tracking Protection Working Group WG <public-tracking@w3.org>
Message-ID: <6E120BECD1FFF142BC26B61F4D994CF3064CA07310@nambx07.corp.adobe.com>
Shane,
Can you provide examples of how a publisher might act differently if they get a null vs no header at all?

From: Shane Wiley [mailto:wileys@yahoo-inc.com]
Sent: Monday, January 30, 2012 10:09 PM
To: Tracking Protection Working Group WG
Subject: ACTION-84: Wiley to describe the reason for setting DNT=null

Description:
Wiley to describe the reason for setting DNT=null

Draft:
<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.
Received on Wednesday, 1 February 2012 18:54:27 UTC

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