- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Wed, 26 Mar 2014 03:34:04 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv4887
Modified Files:
tracking-dnt.html
Log Message:
(editorial) miscellaneous rephrasing
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/26 02:56:30 1.247
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/26 03:34:04 1.248
@@ -503,7 +503,7 @@
when enabled, designers of future extensions ought to use as few
extension characters as possible.
</p>
- <p class="note">At most one DNT header can be present in a valid HTTP
+ <p class="note">At most one DNT header field can be present in a valid
request [[!HTTP]].
</p>
</section>
@@ -535,11 +535,11 @@
<h3>Tracking Preference Expressed in Other Protocols</h3>
<p>
- It is beyond the scope of this specification to define how a user's
- tracking preference might be communicated via protocols other than
- HTTP. However, the semantics of a user's tracking preference is
- intended to apply in general, regardless of the protocols being used
- for Internet communication.
+ A user's tracking preference is intended to apply in general,
+ regardless of the protocols being used for Internet communication.
+ However, it is beyond the scope of this specification to define how
+ a user's tracking preference might be communicated via protocols
+ other than HTTP.
</p>
</section>
</section>
@@ -555,7 +555,7 @@
regarding tracking and providing transparency by communicating
machine-readable claims that a server might wish to make regarding
its own tracking behavior. However, providing a dynamic tracking
- status on every response would effectively disable caching for the
+ status on every response would disable caching for the
entire Web. Instead, this protocol defines a combination of response
mechanisms that allow this information to be communicated without
making every response dynamic.
@@ -583,11 +583,9 @@
<h4>Definition</h4>
<p>
- A <dfn>tracking status value</dfn> (TSV) is a short notation for
- communicating the tracking behavior regarding data collected via a
- <dfn>designated resource</dfn>.
- </p>
- <p>
+ A <dfn>tracking status value</dfn> (TSV) is a single character
+ response to the user's tracking preference with regard to data
+ collected via the <dfn>designated resource</dfn>.
For a site-wide tracking status resource, the designated resource
is any resource on the same origin server.
For a <a>Tk</a> response header field, the target resource of the
@@ -636,8 +634,8 @@
</p>
<p>
If <code>?</code> is present in the site-wide tracking status,
- more information MUST be provided via the <a>Tk</a> response
- header field when accessing a designated resource.
+ the origin server MUST send a <a>Tk</a> header field in all
+ responses to requests on the designated resource.
If <code>?</code> is present in the <a>Tk</a> header field,
more information will be provided in a request-specific
tracking status resource referred to by the <a>status-id</a>.
@@ -832,7 +830,7 @@
<section id='interactive-status-change'>
<h4>Indicating an Interactive Status Change</h4>
<p>
- We anticipate that interactive mechanisms might be used, beyond
+ Interactive mechanisms might be used, beyond
the scope of this specification, that have the effect of asking
for and obtaining prior consent for tracking, or for modifying
prior indications of consent. For example, the tracking status
Received on Wednesday, 26 March 2014 03:34:05 UTC