- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Tue, 24 Mar 2015 17:35:37 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv21557
Modified Files:
tracking-dnt.html
Log Message:
(editorial) Just a few minor tweaks to the introduction
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2015/03/23 20:58:25 1.283
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2015/03/24 17:35:37 1.284
@@ -113,35 +113,37 @@
represent that site are hidden behind the scenes.
</p>
<p>
- It has become common for Web site owners to collect data regarding the
- usage of their sites for a variety of purposes, including what led the
- user to visit their site (referrals), how effective the user experience
- is within the site (web analytics), and the nature of who is using their
- site (audience segmentation). In some cases, the data collected is used
- to dynamically adapt the content (personalization) or the advertising
- presented to the user (targeted advertising). Data collection often
- occurs through the insertion of embedded elements on each page, which
- connect the user's activity across multiple pages. A survey of these
- techniques and their privacy implications can be found in [[KnowPrivacy]].
+ Web site owners often collect data regarding usage of their sites, for a
+ variety of purposes, including what led a user to visit the site
+ (<dfn>referrals</dfn>), how effective the user experience is within the
+ site (<dfn>web analytics</dfn>), and the nature of who is using the
+ site (<dfn>audience segmentation</dfn>).
+ In some cases, the data collected is used to dynamically adapt content
+ (<dfn>personalization</dfn>) or advertising presented to the user
+ (<dfn>targeted advertising</dfn>). Data collection often occurs through
+ insertion of embedded elements on each page, resulting in a stream of
+ data that connects a user's activity across multiple pages. A survey of
+ these techniques and their privacy implications can be found in
+ [[KnowPrivacy]].
</p>
<p>
Users need a mechanism to express their own preferences regarding
<a>tracking</a> that is both simple to configure and efficient when
implemented. However, merely expressing a preference does not imply that
- all recipients will be able to comply. In some cases, a server might be
- dependent on some forms of tracking and is unwilling or unable to turn
- that off. In other cases, a server might perform only limited forms of
- tracking that would be acceptable to most users. Servers need mechanisms
- for communicating their tracking behavior and for storing a
- <a>user-granted exception</a> after the user has made an informed
- choice.
+ all recipients will comply. In some cases, a server might be dependent
+ on some forms of tracking and unwilling or unable to turn that off.
+ In other cases, a server might perform only limited forms of tracking
+ that would be acceptable to most users. Therefore, servers need
+ mechanisms for communicating their own tracking behavior, requesting an
+ exception to a user's general preference, and storing such a
+ <a>user-granted exception</a> after the user has made an informed choice.
</p>
<p>
This specification extends Hypertext Transfer Protocol (HTTP) semantics
[[!RFC7231]] to communicate a user's tracking preference, if any, and an
origin server's tracking behavior. The <a>DNT</a> request header field
is defined for communicating the user's tracking preference for the
- request target. A well-known URI for a
+ <a>target resource</a>. A well-known URI for a
<a href="#status-resource">tracking status resource</a> and the
<a>Tk</a> response header field are defined for communicating the
server's tracking behavior. In addition, JavaScript APIs are defined for
@@ -181,6 +183,8 @@
<dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7230#section-2.3">intermediary</a></dfn>,
<dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7230#section-2.3">proxy</a></dfn>,
<dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7230#section-2.3">cache</a></dfn>,
+ <dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7230#section-3.2">header field</a></dfn>,
+ <dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7230#section-5.1">target resource</a></dfn>,
<dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7231#section-2">resource</a></dfn>, and
<dfn><a class="externalDFN" href="https://tools.ietf.org/html/rfc7231#section-3">representation</a></dfn>.
</p>
Received on Tuesday, 24 March 2015 17:35:43 UTC