- From: CVS User npdoty <cvsmail@w3.org>
- Date: Sun, 15 Jun 2014 00:55:45 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv18019
Modified Files:
tracking-compliance.html
Log Message:
add requirement and explanation for using URI to indicate this version of compliance
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/06/15 00:20:45 1.116
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/06/15 00:55:45 1.117
@@ -263,12 +263,24 @@
</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="indicating-compliance">
+ <h3>Indicating Compliance and Non-Compliance</h3>
+ <p>
+ In order to communicate compliance with a user's expressed tracking preference as described in this recommendation, a party MUST indicate compliance using the tracking status resource defined in the [[TRACKING-DNT]] recommendation. A party MUST use the following URI (in the <code>compliance</code> property array) to indicate compliance with this version of the recommendation:
+ <blockquote>
+ <code>http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html</code>
+ </blockquote>
+ </p>
+ <p class="note">
+ The editor's draft URI points to content that will change. Versions of this document that are published as Working Drafts or later maturity levels will use permanent URIs in this section, pointing to content that does not change.
+ </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>
<section id="first-party-compliance">
<h3>First Party Compliance</h3>
<p>
Received on Sunday, 15 June 2014 00:55:46 UTC