- From: Matthias Schunter via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 24 Jun 2012 02:00:39 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv21225
Modified Files:
tracking-dnt.html
Log Message:
editorial changes - no change to substance was intended
Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.121
retrieving revision 1.122
diff -u -d -r1.121 -r1.122
--- tracking-dnt.html 21 Jun 2012 17:41:30 -0000 1.121
+++ tracking-dnt.html 24 Jun 2012 02:00:37 -0000 1.122
@@ -219,7 +219,7 @@
</p>
<p>
Key to that notion of expression is that it MUST reflect the user's
- choice, not the choice of some vendor, institution, or
+ preference, not the choice of some vendor, institution, or
network-imposed mechanism outside the user's control. The basic
principle is that a tracking preference expression is only
transmitted when it reflects a deliberate choice by the user.
@@ -231,9 +231,11 @@
for a <q>Do Not Track</q> preference: <code>unset</code> or
<code>on</code>.
A user agent MAY offer a third alternative choice: <code>off</code>.
+ </p>
+ <p>
If the user's choice is <code>on</code> or <code>off</code>, the
- tracking preference is <dfn>enabled</dfn>; otherwise, the
- tracking preference is <dfn>not enabled</dfn>.
+ tracking preference is called <dfn>enabled</dfn>; otherwise, the
+ tracking preference is called <dfn>not enabled</dfn>.
</p>
<p>
A user agent MUST have a default tracking preference of
@@ -272,7 +274,8 @@
altered by the network environment, aside from blanket limitations
on what resources can or cannot be accessed through that network.
Implementations of HTTP that are not under control of the user
- MUST NOT express a tracking preference on their behalf.
+ MUST NOT express a tracking preference that does not reflect
+ the user's preference.
</p>
</section>
@@ -303,14 +306,13 @@
</table>
</p>
<p>
- If a tracking preference is <a>not enabled</a>, then no
- preference is expressed by this protocol. This means that no
+ If a tracking preference is <a>not enabled</a>, then this protocol MUST NOT express a preference. This means that no
expression is sent for each of the following cases:
<ul>
<li>the user agent does not implement this protocol;</li>
<li>the user has not yet made a choice for a specific preference;
or,</li>
- <li>the user has chosen not to indicate a preference.</li>
+ <li>the user has chosen not to transmit a preference.</li>
</ul>
</p>
<p>
@@ -374,7 +376,7 @@
intermediary has been specifically installed or configured to do so
by the user making the requests. For example, an Internet Service
Provider MUST NOT inject <q>DNT: 1</q> on behalf of all of their
- users who have not selected a choice.
+ users who have not expressed a preference.
</p>
<p>
The remainder of the DNT field-value after the initial character is
@@ -509,15 +511,12 @@
<h3>Overview</h3>
<p>
- The Tracking Protection protocol is designed to be applicable
+ The TPE protocol is designed to be applicable
regardless of the response from servers that receive the tracking
preference expression, allowing conformance to be achieved without
impacting the operational performance of site resources.
- However, there is also a desire to support verification or
- pre-flight testing of a site's conformance with this protocol for
- evaluating conformance before sending data, enabling specialized
- user interfaces, discovering the scope of protocol deployment, and
- testing adherence to potential regulations.
+ </p>
+ <p> To support feedback from a site how the user preferences are honored (either pre-flight or within a HTTP response), this section describes a <a>tracking status resource</a> as well as a <a>Tk</a> response header that specify how a site conforms with DNT.
</p>
<p>
This section explains how a user agent MAY discover an origin
Received on Sunday, 24 June 2012 02:00:41 UTC