- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Thu, 10 Apr 2014 03:53:33 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv1135
Modified Files:
tracking-dnt.html
Log Message:
(editorial) revise the introduction to reduce opinionating and note that compliance is separate
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/04/10 01:16:20 1.265
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/04/10 03:53:33 1.266
@@ -24,6 +24,16 @@
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/49311/status",
issueBase: "http://www.w3.org/2011/tracking-protection/track/issues/",
localBiblio: {
+ "TCS": {
+ "authors": ["Heather West","Justin Brookman","Sean Harvey","Erica Newland"],
+ // "status" : "WD",
+ // "href" : "http://www.w3.org/TR/tracking-compliance/",
+ "status" : "ED",
+ "href" : "http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html",
+ "title" : "Tracking Compliance and Scope",
+ "date" : "08 April 2014",
+ "publisher" : "W3C"
+ },
"HTTP" : {
"title" : "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing",
"authors": ["Roy T. Fielding", "Julian Reschke"],
@@ -103,26 +113,23 @@
<h2>Introduction</h2>
<p>
- The World Wide Web (WWW, or Web) consists of millions of sites
+ The World Wide Web consists of billions of resources
interconnected through the use of hypertext. Hypertext provides a
- simple, page-oriented view of a wide variety of information that
- can be traversed by selecting links, manipulating controls, and
- supplying data via forms and search dialogs. A Web page is usually
- composed of many different information sources beyond the initial
- resource request, including embedded references to stylesheets,
- inline images, javascript, and other elements that might be
- automatically requested as part of the rendering or behavioral
- processing defined for that page.
- </p>
- <p>
- Each of the hypertext actions and each of the embedded resource
- references might refer to any site on the Web, leading to a seamless
- interaction with the user even when a page might be composed of
- information requested from many different and possibly independent
- Web sites. From the user's perspective, they are simply visiting and
- interacting with a single Web property: all of the technical details
- and protocol mechanisms used to compose a page to represent that
- property are hidden behind the scenes.
+ simple, page-oriented view of the information provided by those
+ resources, which can be traversed by selecting links, manipulating
+ controls, and supplying data via forms and search dialogs.
+ </p>
+ <p>
+ A Web page is often composed of many information sources beyond the
+ initial resource request, including embedded references to
+ stylesheets, inline images, javascript, and other elements that might
+ be automatically requested as part of the rendering or behavioral
+ processing defined for that page. The user's experience is seamless,
+ even if the page has been composed from the results of many network
+ interactions with multiple servers. From the user's perspective, they
+ are simply visiting and interacting with a single Web site: all of the
+ technical details and protocol mechanisms used to compose a page to
+ represent that site are hidden behind the scenes.
</p>
<p>
It has become common for Web site owners to collect data regarding
@@ -132,40 +139,44 @@
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 tracking
- elements on each page. A survey of these techniques and their
+ 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]].
</p>
<p>
- People have the right to know how data about them will be collected
- and how it will be used. Empowered with that knowledge, individuals
- can decide whether to allow their online activities to be tracked and
- data about them to be collected. Many Internet companies use data
- gathered about people's online activities to personalize content and
- target advertising based on their perceived interests. While some
- people appreciate this personalization of content and ads,
- others are troubled by what they perceive as an invasion of
- their privacy. For them, the benefit of personalization is not worth
- their concerns about allowing entities with whom they have no direct
- relationship to amass profiles about their activities.
- </p>
- <p>
- Therefore, users need a mechanism to express their own preference
- regarding tracking that is both simple to configure and efficient
- when implemented. In turn, Web sites that are unwilling or unable to
- offer content without such data collection need a mechanism to
- indicate that status to the user and allow them (or their user agent)
- to make an individual choice regarding exceptions.
- </p>
- <p>
- This specification defines protocol elements for use within the
- Hypertext Transfer Protocol [[!HTTP]] which allow a user to express a
- tracking preference, via the <a>DNT</a> request header field, and
- allow a server to describe their tracking behavior via a well-known
- <a href="#status-resource">tracking status resource</a> and the
- <a>Tk</a> response header field. In addition, JavaScript APIs are
- defined for enabling scripts to determine DNT status and to register a
- user-granted exception.
+ Users need a mechanism to express their own preferences regarding
+ tracking 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 to communicate how they behave with regard to
+ tracking and to store user-granted exceptions after the user has
+ made an informed choice.
+ </p>
+ <p>
+ This specification defines Hypertext Transfer Protocol [[!HTTP]]
+ elements for communicating the user's tracking preference (if any)
+ and communicating the server's tracking behavior (if any).
+ 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 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 enabling scripts to determine DNT status and register a
+ <a>user-granted exception</a>.
+ </p>
+ <p>
+ This specification does not define requirements on what a recipient
+ needs to do to comply with a user's expressed tracking preference,
+ except for the means by which such compliance is communicated.
+ Instead, the tracking status provides the ability to identify a set of
+ compliance regimes to which the server claims to comply, with the
+ assumption being that each regime defines its own requirements on
+ compliant behavior. For example, [[TCS]] is a work-in-progress that
+ intends to define such a compliance regime.
</p>
</section>
Received on Thursday, 10 April 2014 03:53:35 UTC