- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Wed, 11 Jun 2014 12:35:35 -0700
- To: Justin Brookman <jbrookman@cdt.org>
- Cc: W3C DNT Working Group Mailing List <public-tracking@w3.org>
On Jun 11, 2014, at 10:31 AM, Justin Brookman wrote:
> I'm not sure I understand why this would limit our other issues.
It wouldn't limit the issues (they still exist). What it reduces is
the amount of antiquated text used to address them, and removes the
desire to add reminders/repetition of the definition within every
other requirement.
A normative statement like:
Upon receipt of a request containing DNT:1, an origin server MUST do one
of the following:
a) send in any corresponding tracking status for that target resource
the "N" tracking status value and avoid behavior that fits the
definition of tracking with respect to this network interaction; or,
b) send in any corresponding tracking status for that target resource
an appropriate tracking status value to indicate tracking might
occur (any value other than "N") and conform to the limitations
associated with that value, defined below, with respect to tracking
when DNT:1 is received.
The rest of the spec can then define what the server has agreed to
do (or not do) for each TSV, and also define the qualifiers for use
when the TSV is "T".
....Roy
Received on Wednesday, 11 June 2014 19:35:59 UTC