RE: TPE Last Call comments, re: validation of user signals (issue-260)

Nick,

With respect and appreciation for both Roy's time and expertise, I do not believe this addresses my concerns.  

The validity of any signal/preference is premised on their being a mechanism for testing the signal's compliance with the standard it speaks to.  When, as here, there is no way of testing a signal's validity, there are two very different scenarios for taking it at face value.  It is one thing to take a preference at face value when there is not a likelihood of non-compliance and little material effect for accepting the preference at face value.  In the case of DNT, however, we already know that it may be the majority case that preferences are not set to reflect a user expressed choice and there are extremely material economic consequences for taking this un-validated signal at face value.

-Brooks 

-----Original Message-----
From: Nick Doty [mailto:npdoty@w3.org] 
Sent: Tuesday, June 09, 2015 7:04 PM
To: Jack L. Hobaugh Jr; Rachel.Glasser@groupm.com; Alan Chapell; pkosmala@aaaa.org; Dobbs, Brooks; Chris Mejia; David Wainberg; Max.Ochoa@turn.com; tstoute@eyereturn.com; mike@iab.net; alevenfeld@rocketfuel.com; Vivek Narayanadas; nadine.stocklin@pubmatic.com
Cc: public-tracking-comments@w3.org
Subject: TPE Last Call comments, re: validation of user signals (issue-260)

Hi Jack, Rachel, Alan, Peter, Brooks, Chris, David, Max, Tim, Mike, Ari, Vivek and Nadine,

Thank you for your comments (last June) on the TPE Last Call Working Draft. The Tracking Protection Working Group has discussed each of the issues and proposed resolutions. This email in particular describes discussion and proposed resolution regarding validation of DNT signals.

Editor Roy Fielding has provided a detailed response to different comments related to this issue in email; I have provided the link below. I would briefly summarize the resolution as:
* testing and other means can help to validate signals but specification cannot provide additional proof

https://lists.w3.org/Archives/Public/public-tracking/2014Dec/0020.html
https://www.w3.org/2011/tracking-protection/track/issues/260

Please let us know if these changes or explanations resolve your concerns.

Thanks,
Nick Doty, W3C (for the Tracking Protection Working Group)

Re:
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0001.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0003.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0005.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0007.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0009.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0010.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0011.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0012.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0014.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0015.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0016.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0019.html
http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0020.html

Received on Thursday, 11 June 2015 15:59:12 UTC