- From: CVS User npdoty <cvsmail@w3.org>
- Date: Mon, 26 May 2014 03:18:47 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv27233
Modified Files:
tracking-compliance.html tracking-dnt-last-call.html
Log Message:
updating Disregard text per WG discussion; reorg to apply disregard requirements for server compliance generally (first- and third-party); addresses action-448 and issue-207
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/05/26 02:53:42 1.112
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/05/26 03:18:47 1.113
@@ -276,6 +276,25 @@
Implementations of HTTP that are not under control of the user MUST NOT generate or modify a tracking preference.
</p>
</section>
+ <section id="server-compliance">
+ <h3>Server Compliance</h3>
+ <p>
+ It is outside the scope of this specification to control short-term,
+ transient collection and use of data, so long as the data is not
+ shared with a third party and is not used to build a profile about a
+ user or otherwise alter an individual user’s user experience outside the
+ current network interaction. For example, the contextual customization
+ of ads shown as part of the same network interaction is not restricted
+ by a <code>DNT:1</code> signal.
+ </p>
+ <p class="issue" data-number="134" title="Would we additionally permit logs that are retained for a short enough period?"></p>
+ <p class="issue" data-number="204" title="Definitions of collection / retention and transience / network interaction"></p>
+ <p>
+ A party to a given user action that disregards a DNT signal MUST indicate so to the user agent, using the response mechanism defined in the [[TRACKING-DNT]] recommendation. The party MUST provide information in its privacy policy listing the specific reasons for not honoring the user's expressed preference. The party's representation MUST be clear and easily discoverable.
+ </p>
+ <p>
+ In the interest of transparency, especially where multiple reasons are listed, a server might use the [[TRACKING-DNT]] <a class="externalDFN" href="http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#rep.qualifiers">qualifiers</a> or <a class="externalDFN" href="http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#rep.config">config</a> properties to indicate a particular reason for disregarding or steps to address the issue. A user agent can parse this response to communicate the reason to the user or direct the user to the relevant section of a privacy policy. This document does not define specific qualifiers for different reasons servers might have for disregarding signals.
+ </p>
<section id="first-party-compliance">
<h3>First Party Compliance</h3>
<p>
@@ -319,22 +338,6 @@
one of the permitted uses MUST NOT place a unique identifier in cookies
or other browser-based local storage mechanisms.
</p>
- <p>
- A third party to a given user action that disregards a DNT signal MUST indicate so to the user
- agent, using the response mechanism defined in the [[!TRACKING-DNT]] recommendation.
- </p>
- <p>
- It is outside the scope of this specification to control short-term,
- transient collection and use of data, so long as the data is not
- shared with a third party and is not used to build a profile about a
- user or otherwise alter an individual user’s user experience outside the
- current network interaction. For example, the contextual customization
- of ads shown as part of the same network interaction is not restricted
- by a <code>DNT:1</code> signal.
- </p>
- <p class="issue" data-number="134" title="Would we additionally permit logs that are retained for a short enough period?"></p>
- <p class="issue" data-number="204" title="Definitions of collection / retention and transience / network interaction"></p>
-
<section id="geolocation">
<h3>Third Party Geolocation Compliance</h3>
<p>
@@ -479,6 +482,7 @@
</section>
</section>
</section>
+ </section>
<section id="user-granted-exceptions">
<h2>User-Granted Exceptions</h2>
<p>
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt-last-call.html 2014/04/14 12:34:04 1.3
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt-last-call.html 2014/05/26 03:18:47 1.4
@@ -8,8 +8,9 @@
var respecConfig = {
specStatus: "LC",
shortName: "tracking-dnt",
- // publishDate: "2014-03-13",
+ publishDate: "2014-04-24",
previousPublishDate: "2014-01-28",
+ lcEnd: "2014-06-19",
previousMaturity: "WD",
edDraftURI: "http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html",
editors: [
@@ -20,7 +21,7 @@
],
wg: "Tracking Protection Working Group",
wgURI: "http://www.w3.org/2011/tracking-protection/",
- wgPublicList: "public-tracking",
+ wgPublicList: "public-tracking-comments",
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/49311/status",
issueBase: "http://www.w3.org/2011/tracking-protection/track/issues/",
localBiblio: {
@@ -70,7 +71,6 @@
noIDLSectionTitle: true
};
</script>
- <link rel="stylesheet" href="additional.css" type="text/css" media="screen" title="custom formatting for TPWG editors">
</head>
<body>
<section id='abstract'>
@@ -85,7 +85,21 @@
machine-readable tracking status.
</p>
</section>
-
+ <section id="sotd">
+ <p>
+ Readers may review <a href="http://services.w3.org/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FTR%2F2013%2FWD-tracking-dnt-20130912%2F&doc2=http%3A%2F%2Fwww.w3.org%2FTR%2F2014%2FWD-tracking-dnt-20140128%2F">changes
+ from the previous Working Draft</a>; in particular, recent changes
+ have updated definitions, requirements on determining a user preference and introduced a media type. An
+ <a href="http://www.w3.org/2011/tracking-protection/track/products/2/all">issue
+ tracking system</a> is available for recording issues regarding this document and their resolutions.
+ </p>
+ <p>
+ This document is published as a Last Call Working Draft, which invites broad community review of technical requirements and dependencies. The Tracking Protection Working Group encourages people to comment on the extent to which technical requirements of the group's <a href="http://www.w3.org/2011/tracking-protection/charter.html">charter</a>have been met and how significant dependencies with groups inside and outside W3C have been satisfied. The Working Group will evaluate all comments received and determine whether or how the specification needs to be modified in light of the comments. Comments will be evaluated on whether they identify technical problems with the TPE, whether the TPE fulfills its requirements, and whether the TPE creates or does not otherwise resolve dependencies with other technical standards, practices or processes. The Chairs of the Working Group will issue written responses to all comments received.
+ </p>
+ <p>
+ Of note, this document does not define site behavior for complying with a user's expressed tracking preference, but does provide sites with a mechanism for indicating compliance. The Tracking Compliance and Scope [[TCS]] specification which standardizes how sites should respond to Do Not Track requests, including what information may be collected for limited permitted uses despite a Do Not Track signal, is under discussion. The Tracking Protection Working Group expects that specification to proceed to Last Call in the summer of 2014. Both specifications are currently scheduled to go to Candidate Recommendation in December 2014.
+ </p>
+ </section>
<section>
<h2>Introduction</h2>
Received on Monday, 26 May 2014 03:18:48 UTC