CVS WWW/2011/tracking-protection/drafts

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

Modified Files:
	tracking-dnt.html 
Log Message:
fix paste-o in TSV abnf and clarify that data collected under P status cannot be used or shared

--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2013/04/23 10:06:45	1.205
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2013/04/24 04:41:23	1.206
@@ -547,7 +547,6 @@
 <dfn>TSV</dfn>    = "1"              ; "1" — first-party
        / "3"              ; "3" — third-party
        / %x43             ; "C" - consent
-       / %x50             ; "P" - potential consent
        / %x44             ; "D" - disregarding
        / %x4E             ; "N" - none
        / %x50             ; "P" - potential consent
@@ -671,10 +670,10 @@
             A tracking status value of <dfn>P</dfn> means that the origin
             server does not know, in real-time, whether it has received prior
             consent for tracking this user, user agent, or device, but
-            promises not to use any <code>DNT:1</code> data until such consent
-            has been determined, and further promises to de-identify within
-            forty-eight hours any <code>DNT:1</code> data received for which
-            such consent has not been received.
+            promises not to use or share any <code>DNT:1</code> data until
+            such consent has been determined, and further promises to delete
+            or de-identify within forty-eight hours any <code>DNT:1</code>
+            data received for which such consent has not been received.
           </p>
           <p>
             Since this status value does not itself indicate whether a
@@ -690,9 +689,9 @@
             the time of a request is either impractical, due to legacy systems
             not being able to keep up with Web traffic, or potentially "gamed"
             by first party sites if they can determine which of their users
-            have consented. It cannot be used for the sake of personalization
-            unless consent is determined at the time of a request, in which
-            case the <code><a>C</a></code> tracking status is preferred.
+            have consented. The data cannot be used for the sake of
+            personalization. If consent can be determined at the time of a
+            request, the <code><a>C</a></code> tracking status is preferred.
           </p>
           <p class="issue" data-number="195" title="Flows and signals for handling out of band consent">
             <b>[OPEN]</b> The <code><a>P</a></code> tracking status

Received on Wednesday, 24 April 2013 04:42:09 UTC