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

Re: ACTION-359: Add proposal for ISSUE-161 to allow an indicator of non-compliance within the tracking status value for testing and deployment

From: Jonathan Mayer <jmayer@stanford.edu>
Date: Mon, 11 Feb 2013 09:26:31 -0800
To: "Roy T. Fielding" <fielding@gbiv.com>
Cc: David Wainberg <david@networkadvertising.org>, "public-tracking@w3.org WG" <public-tracking@w3.org>
Message-ID: <9DD40D5688B549C688CF58D3BFAAD36C@gmail.com>
The current text is unclear.  Does "!" mean a website is testing DNT?  Or does it mean general noncompliance?

Here's an alternative: "The origin server is presently testing the tracking protection protocol and tracking compliance policy.  The server is not compliant with either recommendation."


On Monday, February 11, 2013 at 2:15 AM, Roy T. Fielding wrote:

> On Feb 10, 2013, at 2:43 PM, Jonathan Mayer wrote:
> > Some (myself included) object to a general signal for noncompliance.  The shared concern is that websites will claim they "implement Do Not Track" (i.e. the TPE protocol) when they do not implement the TCS compliance policy. 
> > 
> > There seemed to be greater comfort with a noncompliance signal scoped solely to temporary testing.  I would still be uneasy.
> > 
> > Jonathan
> Please direct your comments to the specific proposal that appears
> in the editors' draft:
> http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#tracking-status-value
> I believe that both the first paragraph of 5.2 and the definition
> provided for the ! status are quite clear and cannot be confused
> with implementing the tracking protection protocol.  If you don't
> think so, please provide alternate wording.
> I am less sure about confusion regarding implementing Do Not Track,
> since we haven't defined that, but I seriously doubt that there
> is any incentive whatsoever for sites to say that they implement
> DNT when they don't actually do so.
> ....Roy 
Received on Monday, 11 February 2013 17:26:59 UTC

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