W3C home > Mailing lists > Public > public-tracking-commit@w3.org > September 2012

WWW/2011/tracking-protection/drafts tracking-compliance-20121002.html,1.3,1.4 tracking-dnt-20121002.html,1.8,1.9

From: Nick Doty via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 30 Sep 2012 22:51:58 +0000
To: public-tracking-commit@w3.org
Message-Id: <E1TISMg-0001gE-9t@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv6400

Modified Files:
	tracking-compliance-20121002.html tracking-dnt-20121002.html 
Log Message:
backporting small fixes from published versions

Index: tracking-compliance-20121002.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance-20121002.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- tracking-compliance-20121002.html	29 Sep 2012 09:01:13 -0000	1.3
+++ tracking-compliance-20121002.html	30 Sep 2012 22:51:56 -0000	1.4
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <html dir="ltr" lang="en"><head>
-  <title>Tracking Compliance and Scope Specification</title>
+  <title>Tracking Compliance and Scope</title>
   <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
   
 <style type="text/css">
@@ -233,7 +233,7 @@
       <a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a>
     
   </p>
-  <h1 class="title" id="title">Tracking Compliance and Scope Specification</h1>
+  <h1 class="title" id="title">Tracking Compliance and Scope</h1>
   
   <h2 id="w3c-working-draft-02-october-2012"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft 02 October 2012</h2>
   <dl>
@@ -306,7 +306,8 @@
         Text in blue boxes presents multiple options the group is considering.
         Options included in this draft should not be read as limitations on
         the potential outcome, but rather simply as possible options that are
-        currently under consideration by the working group.
+        currently under consideration by the working group. This draft is
+        substantially revised from the previous Working Draft.
         An
         <a href="http://www.w3.org/2011/tracking-protection/track/issues/">issue tracking system</a>
         is available for recording
@@ -976,8 +977,7 @@
 <section id="third-party-compliance">
 <!--OddPage--><h2><span class="secno">6. </span>Third Party Compliance</h2>
 <div class="note"><div class="note-title"><span>Note</span></div><p class="">This section addresses the crux of what DNT is intended to accomplish, and as such, all of this section remains
-hotly debated.  The specific language is likely to change.  See also alternative text proposed by Nick Doty:
-http://lists.w3.org/Archives/Public/public-tracking/2012Sep/0141.html</p></div>
+hotly debated.  The specific language is likely to change.  See also <a href="http://lists.w3.org/Archives/Public/public-tracking/2012Sep/0141.html">alternative text proposed by Nick Doty</a>.</p></div>
 
 <p>If a third party receives a communication to which a DNT:1 header is attached:</p>
 <ol start="1"><li>that third party <em title="MUST NOT" class="rfc2119">MUST NOT</em> collect, share, or use information related to that communication outside of the permitted uses
@@ -1073,14 +1073,14 @@
 <h5><span class="secno">6.1.1.6 </span>Security and Fraud Prevention</h5>
 <p>Regardless of DNT signal, information may be collected, retained and used for detecting security risks and fraudulent activity, defending from attacks and fraud, and maintaining integrity of the service.  This includes data reasonably necessary for enabling authentication/verification, detecting hostile transactions and attacks, providing fraud prevention, and maintaining system integrity. In this example specifically, this information may be used to alter the user's experience in order to reasonably keep a service secure or prevent fraud.</p>
 
-<div class="note"><div class="note-title"><span>Note</span></div><p class="">The more likely options at this point may be represented in Nick Doty's proposed:<br><br>
-To the extent reasonably necessary for protection of computers and networks and to detect ad or other fraud, third parties may engage in tracking.
-Use of graduated response is preferred.<br><br>
-or David Wainberg's proposed<br><br>
-Parties may collect and use data in any way to the extent reasonably necessary for the detection and prevention of malicious or illegitimate activity.</p></div>
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">The more likely options at this point may be represented in Nick Doty's proposed:
+<blockquote>To the extent reasonably necessary for protection of computers and networks and to detect ad or other fraud, third parties may engage in tracking.
+Use of graduated response is preferred.</blockquote>
+or David Wainberg's proposed:
+<blockquote>Parties may collect and use data in any way to the extent reasonably necessary for the detection and prevention of malicious or illegitimate activity.</blockquote></p></div>
 
 <section class="informative" id="security-example"><h6><span class="secno">6.1.1.6.1 </span>Examples</h6><p><em>This section is non-normative.</em></p>
-<div class="note"><div class="note-title"><span>Note</span></div><p class="">Add examples with and without outsourced parties (J- not sure what this means)</p></div></section>
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">Add examples with and without outsourced parties</p></div></section>
 </section>
 
 <section id="debugging">
@@ -1283,9 +1283,6 @@
 <h4><span class="secno">6.6.1 </span>Third Party Auditing</h4>
 
 <div class="issue"><div class="issue-title"><a href="http://www.w3.org/2011/tracking-protection/track/issues/21"><span>Issue 21</span></a>: Enable external audit of DNT compliance</div><p class=""></p></div>
-<!--
-<p class="note">We have reviewed one audit proposal that we declined to adopt as mandatory, but there is significant support to include a flexible option to enable auditing. We may include a smaller-scoped proposal in the future, or may drop auditing all together.</p>
--->
 <p><cite><a class="ref" href="http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#status-representation">Tracking Status Qualifiers</a></cite> may include a value to indicate auditing.</p>
 
 </section>
@@ -1298,6 +1295,6 @@
 
 
 <section class="appendix" id="references"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-HTTP11">[HTTP11]</dt><dd>R. Fielding; et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1.</cite></a> June 1999. Internet RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a> 
-</dd><dt id="bib-TRACKING-DNT">[TRACKING-DNT]</dt><dd>Roy T. Fielding; David Singer. <a href="http://www.w3.org/TR/tracking-dnt/"><cite>Tracking Preference Expression (DNT).</cite></a> 13 March 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-tracking-dnt-20120313/">http://www.w3.org/TR/2012/WD-tracking-dnt-20120313/</a> 
+</dd><dt id="bib-TRACKING-DNT">[TRACKING-DNT]</dt><dd>Roy T. Fielding; David Singer. <a href="http://www.w3.org/TR/tracking-dnt/"><cite>Tracking Preference Expression (DNT).</cite></a> 2 October 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-tracking-dnt-20121002/">http://www.w3.org/TR/2012/WD-tracking-dnt-20121002/</a> 
 </dd></dl></section><section id="informative-references"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-KnowPrivacy">[KnowPrivacy]</dt><dd>Joshua Gomez; Travis Pinnick; Ashkan Soltani. <a href="http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf"><cite>KnowPrivacy.</cite></a> 1 June 2009. URL: <a href="http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf">http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf</a> 
 </dd></dl></section></section></body></html>

Index: tracking-dnt-20121002.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt-20121002.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- tracking-dnt-20121002.html	29 Sep 2012 07:05:15 -0000	1.8
+++ tracking-dnt-20121002.html	30 Sep 2012 22:51:56 -0000	1.9
@@ -505,7 +505,8 @@
         Text in blue boxes presents multiple options the group is considering.
         Options included in this draft should not be read as limitations on
         the potential outcome, but rather simply as possible options that are
-        currently under consideration by the working group.
+        currently under consideration by the working group. Readers may review
+        <a href="http://www.w3.org/2007/10/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FTR%2F2012%2FWD-tracking-dnt-20120313%2F&doc2=http%3A%2F%2Fwww.w3.org%2FTR%2F2012%2FWD-tracking-dnt-20121002%2F">changes from the previous Working Draft</a>.
         An
         <a href="http://www.w3.org/2011/tracking-protection/track/issues/">issue tracking system</a>
         is available for recording
@@ -2415,10 +2416,10 @@
 
 <section class="appendix" id="references"><!--OddPage--><h2><span class="secno">B. </span>References</h2><section id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-ABNF">[ABNF]</dt><dd>D. Crocker and P. Overell. <a href="http://www.ietf.org/rfc/rfc5234.txt"><cite>Augmented BNF for Syntax Specifications: ABNF.</cite></a> January 2008. Internet RFC 5234. URL: <a href="http://www.ietf.org/rfc/rfc5234.txt">http://www.ietf.org/rfc/rfc5234.txt</a>
 </dd><dt id="bib-HTTP11">[HTTP11]</dt><dd>R. Fielding; et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1.</cite></a> June 1999. Internet RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a> 
-</dd><dt id="bib-NAVIGATOR">[NAVIGATOR]</dt><dd>Ian Hickson, David Hyatt. <a href="http://dev.w3.org/html5/spec/timers.html#navigator"><cite>Navigator interface in HTML5.</cite></a> 15 April 2011. Editors' draft. (Work in progress.) URL: <a href="http://dev.w3.org/html5/spec/timers.html#navigator">http://dev.w3.org/html5/spec/timers.html#navigator</a> 
+</dd><dt id="bib-NAVIGATOR">[NAVIGATOR]</dt><dd>Robin Berjon; Travis Leithead; Silvia Pfeiffer; Erika Doyle Navara; Edward O'Connor; Ian Hickson. <a href="http://dev.w3.org/html5/spec/system-state-and-capabilities.html#the-navigator-object"><cite>The Navigator object - System state and capabilities - HTML5.</cite></a> 28 September 2012. Editors' draft. (Work in progress.) URL: <a href="http://dev.w3.org/html5/spec/system-state-and-capabilities.html#the-navigator-object">http://dev.w3.org/html5/spec/system-state-and-capabilities.html#the-navigator-object</a> 
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
 </dd><dt id="bib-RFC4627">[RFC4627]</dt><dd>D. Crockford. <a href="http://www.ietf.org/rfc/rfc4627.txt"><cite>The application/json Media Type for JavaScript Object Notation (JSON)</cite></a> July 2006. Internet RFC 4627. URL: <a href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a>
-</dd><dt id="bib-TRACKING-COMPLIANCE">[TRACKING-COMPLIANCE]</dt><dd>Justin Brookman; Sean Harvey; Erica Newland; Heather West. <a href="http://www.w3.org/TR/tracking-compliance/"><cite>Tracking Compliance and Scope.</cite></a> 13 March 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-tracking-compliance-20120313/">http://www.w3.org/TR/2012/WD-tracking-compliance-20120313/</a> 
+</dd><dt id="bib-TRACKING-COMPLIANCE">[TRACKING-COMPLIANCE]</dt><dd>Justin Brookman; Sean Harvey; Erica Newland; Heather West. <a href="http://www.w3.org/TR/tracking-compliance/"><cite>Tracking Compliance and Scope.</cite></a> 2 October 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-tracking-compliance-20121002/">http://www.w3.org/TR/2012/WD-tracking-compliance-20121002/</a> 
 </dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd>Cameron McCormack. <a href="http://www.w3.org/TR/2011/WD-WebIDL-20110927/"><cite>Web IDL.</cite></a> 27 September 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/WD-WebIDL-20110927/">http://www.w3.org/TR/2011/WD-WebIDL-20110927/</a> 
 </dd></dl></section><section id="informative-references"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-COOKIES">[COOKIES]</dt><dd>Adam Barth. <cite><a href="http://www.rfc-editor.org/rfc/rfc6265.txt">HTTP State Management Mechanism</a>.</cite> April 2011. Internet Proposed Standard RFC 6265. URL: <a href="http://www.rfc-editor.org/rfc/rfc6265.txt">http://www.rfc-editor.org/rfc/rfc6265.txt</a> 
 </dd><dt id="bib-KnowPrivacy">[KnowPrivacy]</dt><dd>Joshua Gomez; Travis Pinnick; Ashkan Soltani. <a href="http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf"><cite>KnowPrivacy.</cite></a> 1 June 2009. URL: <a href="http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf">http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf</a> 
Received on Sunday, 30 September 2012 22:52:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 30 September 2012 22:52:00 GMT