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

WWW/2011/tracking-protection/drafts tracking-compliance-20120523.html,NONE,1.1 tracking-compliance.html,1.56,1.57

From: Nick Doty via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 06 Aug 2012 19:27:26 +0000
To: public-tracking-commit@w3.org
Message-Id: <E1SySxa-0008Dt-Nl@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv31496

Modified Files:
Added Files:
Log Message:
moving strawman to editors draft slot; adding old editors draft as a separate file; enabling section hiding toggle

Index: tracking-compliance.html
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- tracking-compliance.html	23 May 2012 20:31:52 -0000	1.56
+++ tracking-compliance.html	6 Aug 2012 19:27:24 -0000	1.57
@@ -1,2008 +1,909 @@
-<!DOCTYPE html>
-	<title>Tracking Compliance and Scope Specification</title>
-	<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
-	<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js"
-	<script class="remove">
-	  var respecConfig = {
-		  specStatus:          "ED",
-		  shortName:           "tracking-compliance",
[...2887 lines suppressed...]
+<p>This specification consists of input from many discussions within and around the W3C Tracking Protection Working Group, along with written contributions from Haakon Flage Bratsberg (Opera Software), Amy Colando (Microsoft Corporation), Roy T. Fielding (Adobe), Tom Lowenthal (Mozilla), Ted Leung (The Walt Disney Company), Jonathan Mayer (Stanford University), Ninja Marnau (Invited Expert), Matthias Schunter (IBM), John M. Simpson (Invited Expert), Kevin G. Smith (Adobe), Rob van Eijk (Invited Expert), Rigo Wenning (W3C), and Shane Wiley (Yahoo!).</p>
+<p>The DNT header field is based on the original Do Not Track submission by Jonathan Mayer (Stanford), Arvind Narayanan (Stanford), and Sid Stamm (Mozilla). The DOM API for NavigatorDoNotTrack is based on the Web Tracking Protection submission by Andy Zeigler, Adrian Bateman, and Eliot Graff (Microsoft). Many thanks to Robin Berjon for ReSpec.js.</p>
+<section id="references">
+<h2>References</h2><h3>B.1 Normative references</h3>
+<p>R. Fielding; et al. <a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext Transfer Protocol - HTTP/1.1.</a> June 1999. Internet RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a></p>
+<p>Roy T. Fielding; David Singer. <a href="http://www.w3.org/TR/tracking-dnt/">Tracking Preference Expression (DNT).</a> 13 March 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/WD-tracking-dnt-20120313/">http://www.w3.org/TR/2011/WD-tracking-dnt-20120313/</a></p>
+<h3>B.2 Informative references</h3>
+<p>Joshua Gomez; Travis Pinnick; Ashkan Soltani. <a href="http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf">KnowPrivacy.</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></p>
+<div id="toggle-widget">
+  <a href="#" id="toggle-button">Hide non-normative sections</a>
\ No newline at end of file

--- NEW FILE: tracking-compliance-20120523.html ---
<!DOCTYPE html>
	<title>Tracking Compliance and Scope Specification</title>
	<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
	<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js"
	<script class="remove">
	  var respecConfig = {
		  specStatus:          "ED",
		  shortName:           "tracking-compliance",
		  // subtitle:  "an excellent document",
		  // publishDate:         "2012-03-13",
		  copyrightStart:      "2011",
		  previousPublishDate: "2012-03-13",
		  previousMaturity:    "WD",
		  // lcEnd: "2009-08-05",
[...1969 lines suppressed...]
			<p class="issue"><a
What types of tracking exist, and what are the use cases for these types of
			<p class="issue">Should we address the association of first party
data with third party data? What does this standard say about a first party
associating offline data from a third party with their own data and then using
that in targeting? How about the first party associating it with third party
data and/or selling it to a third party? </p>
			<p class="issue">For now, we are using "behavioral tracking" as
the term of interest in the scope of this document, though we may want to
refer in all cases to "tracking" instead.</p>
	<p class="issue">We may want to talk about including a data minimization
piece to these exemptions</p> 

Received on Monday, 6 August 2012 19:27:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:48:55 UTC