- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Tue, 01 Apr 2014 07:31:19 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv13150
Modified Files:
tracking-dnt.html
Log Message:
(editorial) simplify the response overview
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/04/01 07:00:58 1.256
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/04/01 07:31:19 1.257
@@ -554,28 +554,13 @@
<h3>Overview</h3>
<p>
- This protocol has the dual goals of expressing the user's preference
- 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 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.
- </p>
- <p>
- This section explains how a user agent MAY discover an origin
- server's tracking status for a given resource.
- It defines a REQUIRED <a>site-wide tracking status resource</a> at
- a specific well-known location and an OPTIONAL space of
- <a href="#request-specific-status-resource">request-specific tracking
- status resources</a> for sites where
- the tracking status might vary based on data within the request.
- It also defines a <a>Tk</a> response header field that MAY be sent
- in any response, MUST be sent in responses to requests that
- modify the tracking status, and MAY direct the
- user to a request-specific tracking status resource applicable to
- the current request.
+ In addition to expressing the user's preference regarding tracking,
+ this protocol enables servers to communicate machine-readable claims
+ regarding their own tracking behavior. Since a personalized tracking
+ status on every response would disable caching, a combination of
+ response mechanisms are defined to allow the tracking status to be
+ communicated prior to making a trackable request and without making
+ every response dynamic.
</p>
</section>
Received on Tuesday, 1 April 2014 07:31:20 UTC