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

RE: tracking-ISSUE-186 (Chapell): Ensure that browsers communicate DNT functionality accurately [Tracking Definitions and Compliance]

From: Shane Wiley <wileys@yahoo-inc.com>
Date: Mon, 5 Nov 2012 10:24:21 -0800
To: Tracking Protection Working Group <public-tracking@w3.org>
Message-ID: <63294A1959410048A33AEE161379C8027484B814CF@SP2-EX07VS02.ds.corp.yahoo.com>
While not resolved, I believe this overlaps with Action-212 (tied directly to the Compliance and Scope document).

-----Original Message-----
From: Tracking Protection Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] 
Sent: Monday, November 05, 2012 10:55 AM
To: public-tracking@w3.org
Subject: tracking-ISSUE-186 (Chapell): Ensure that browsers communicae DNT functionality accurately [Tracking Definitions and Compliance]

tracking-ISSUE-186 (Chapell): Ensure that browsers communicae DNT functionality accurately [Tracking Definitions and Compliance]

http://www.w3.org/2011/tracking-protection/track/issues/186


Raised by: Alan Chapell
On product: Tracking Definitions and Compliance

I'm not attempting to specify User Interface. However, it seems reasonable to ask that browsers communicate DNT functionality clearly to Users. 

Mozilla describes its DNT functionality as follows: “Tell websites that I do not want to be tracked.” I'm not proposing that we specify exactly how browsers communicate to their Users. However, it seems self-evident that some guidance would be helpful. The notion that ‘websites’ are doing the ‘tracking’ that would be ceased as a result of a DNT signal is incorrect – as First Party websites are mostly exempt from the requirements of DNT.

At the very least, this group's output might benefit from some additional thinking in this area.

I was unable to find this issue raised previously. If I'm incorrect, please accept my apologies - and forward the issue and its resolution to me. 





Received on Monday, 5 November 2012 18:25:13 UTC

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