CVS WWW/2011/tracking-protection/drafts

Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv16341

Modified Files:
	tracking-compliance.html 
Log Message:
update to remove separate UA compliance section, per action-450; add note and issue marker to UA section in definitions

--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html	2014/05/26 03:46:55	1.115
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html	2014/06/15 00:20:45	1.116
@@ -90,7 +90,11 @@
         various client programs capable of initiating HTTP requests,
         including but not limited to browsers, spiders (web-based robots),
         command-line tools, native applications, and mobile apps [[!HTTP11]].
-      </p></section>
+      </p>
+      <p class="issue" data-number="227" title="User Agent requirements in UA Compliance vs. Scope section">
+        There is a proposal to move a sentence about user agents from the Introduction/Scope section to this section. We might also include a reference here to the conformance requirements on user agents in the companion TPE recommendation.
+      </p>
+      </section>
       
       <section id="network-interaction">
       <h3>Network Interaction</h3>
@@ -246,46 +250,6 @@
 
 			</section>
 	</section> <!-- end definitions -->
-	<section id="user-agent-compliance">
-    <h3>User Agent Compliance</h3>
-      <p class="issue" data-number="205" title="user agent compliance requirements; connections to TPE"></p>
-      <p class="note">Much of this is duplicative of requirements in the [[TRACKING-DNT]] specification. Can we harmonize the two? For example: by removing this section and just including a normative reference and a summary of the requirements; or by reducing this section to any requirements beyond those in [[TRACKING-DNT]].</p>
-			<p>
-				A user agent MUST offer users a minimum of two alternative choices for a Do Not Track general preference: unset or DNT: 1. A user agent MAY offer a third alternative choice: DNT: 0.
-			</p>
-			<p>
-				If the user's choice is DNT:1 or DNT:0, the tracking preference is <dfn>enabled</dfn>; otherwise, the tracking preference is <dfn>not enabled</dfn>.
-			</p>
-			<p>
-				A user agent MUST have a default tracking preference of unset (not enabled).
-			</p>
-			<p>
-				User agents and web sites are responsible for determining the user experience by which a tracking preference is controlled. User agents and web sites MUST ensure that tracking preference choices are communicated to users clearly and accurately and shown at the time and place the tracking preference choice is made available to a user.  User agents and web sites MUST ensure that the tracking preference choices describe the parties to whom DNT applies and MUST make available brief and neutral explanatory text to provide more detailed information about DNT functionality.
-			</p>
-			<p>
-				That text MUST indicate that:
-			</p>
-			<ol>
-				<li>
-					if the tracking preference is communicated, it limits collection and use of web viewing data for certain advertising and other purposes;
-				</li>
-				<li>
-					when DNT is enabled, some data may still be collected and used for certain purposes, and a description of such purposes; and
-				</li>
-				<li>
-					if a user affirmatively allows a particular party to collect and use data about web viewing activities, enabling DNT will not limit collection and use from that party.
-				</li>
-			</ol>
-			<p>
-				User agents and web sites MUST obtain an explicit choice made by a user when setting controls that affect the tracking preference expression.
-			</p>
-			<p>
-				A user agent MUST transmit the tracking preference according to the [[!TRACKING-DNT]] specification.
-			</p>
-			<p>
-				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>

Received on Sunday, 15 June 2014 00:20:46 UTC