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

WWW/2011/tracking-protection/drafts tracking-compliance.html,1.77,1.78

From: Nick Doty via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 30 Sep 2012 22:57:04 +0000
To: public-tracking-commit@w3.org
Message-Id: <E1TISRc-0002An-QQ@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv8260

Modified Files:
	tracking-compliance.html 
Log Message:
backporting formatting changes from published drafts

Index: tracking-compliance.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -d -r1.77 -r1.78
--- tracking-compliance.html	29 Sep 2012 09:14:51 -0000	1.77
+++ tracking-compliance.html	30 Sep 2012 22:57:02 -0000	1.78
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en" dir="ltr">
 <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">
   <script src='http://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
   <script class="remove">
@@ -677,9 +677,7 @@
 <section id="third-party-compliance">
 <h3>Third Party Compliance</h3>
 <p class="note">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>
-
+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>
 <p>If a third party receives a communication to which a DNT:1 header is attached:</p>
 <ol start="1"><li>that third party MUST NOT collect, share, or use information related to that communication outside of the permitted uses
 as defined within this standard and any explicitly-granted exceptions, provided in accordance with the requirements of this standard;</li>
@@ -829,11 +827,11 @@
 <h5>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>
 
-<p class="note">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 class="note"><p>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>Examples</h6>
 <p class="note">Add examples with and without outsourced parties (J- not sure what this means)</p></section>
Received on Sunday, 30 September 2012 22:57:06 GMT

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