W3C home > Mailing lists > Public > public-tracking@w3.org > August 2014

Re: tracking-ISSUE-259: require public-facing statement of server response policy [TPE Last Call]

From: Roy T. Fielding <fielding@gbiv.com>
Date: Tue, 26 Aug 2014 18:58:46 -0700
Message-Id: <839C16E7-F6E4-4AF8-B04D-02A322D341E8@gbiv.com>
To: Tracking Protection Working Group <public-tracking@w3.org>
On Jul 12, 2014, at 6:58 PM, Tracking Protection Working Group Issue Tracker wrote:

> tracking-ISSUE-259: require public-facing statement of server response policy [TPE Last Call]
> 
> http://www.w3.org/2011/tracking-protection/track/issues/259
> 
> Raised by: Lee Tien
> On product: TPE Last Call
> 
> http://lists.w3.org/Archives/Public/public-tracking-comments/2014Jun/0002.html
> 
> To the extent that one objective of the TPE standard is to ensure that a serverís communication of its tracking status value is enforceable under Section 5 of the FTC Act or another similar regulatory regime, the TPE specification should require the server to describe within its privacy policy or other public-facing documents the meaning of its TSV and how the server responds to usersí tracking preferences.

WONTFIX.  The meaning of each TSV is defined by the TPE specification and
nowhere else.  The additional explanation required by "D" is to explain
why it is being communicated, not what is being communicated.

The goal of TPE is to provide machine-readable communication.
A human-readable version of what has been transmitted can be generated
by the user agent based on what has been communicated by TPE and in
accordance with the UA's own UI preferences.

....Roy
Received on Wednesday, 27 August 2014 01:59:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:12 UTC