- From: Justin Brookman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 04 Oct 2012 14:17:10 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv21715
Modified Files:
tracking-compliance.html
Log Message:
Removed logged in ghost section, held place for more options on using first party data in third party context
Index: tracking-compliance.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -d -r1.83 -r1.84
--- tracking-compliance.html 4 Oct 2012 11:39:01 -0000 1.83
+++ tracking-compliance.html 4 Oct 2012 14:17:08 -0000 1.84
@@ -1550,7 +1550,7 @@
including content or advertisements based on the first-party
domain that the user visited.
</p>
-
+
<section class="informative" id="contextual-example">
<h6>Examples</h6>
</section>
@@ -1583,19 +1583,24 @@
<section id="first-party-data">
<h5>Content or Ad Delivery Based on First Party Data</h5>
- <p class="note">
- Note that it is not clear that this is in scope, per Shane;
- others disagree. Revisit whether contextual belongs in some place
- other than permitted uses (potentially the definition of
- collection).
- </p>
- <p class="option">
+
+ <p class="option">
Regardless of DNT signal, information may be collected, retained
and used for the display of content or advertisements based in
part on data that the third party previously collected from the
user when acting as a first party.
</p>
+ <p class=note>This text will be revised to offer two alternatives:
+ first parties can use any data to offer content in the third party
+ context, or first parties can only use declared data to offer
+ content in the third party context. The issue is also contingent
+ upon what identifiers third parties can use in when Do Not Track is
+ turned on. If third parties cannot read cookies, they may be
+ unable to associate first parties in third-party scenarios.<br><br>
+ Others have argued that this language is unnecessary because the
+ standard places no limitations on the use of first party data.</p>
+
<section class="informative" id="first-party-example">
<h6>Examples</h6>
@@ -1942,21 +1947,6 @@
</ol>
</section>
- <section id="logged-in">
- <h3>Logged In Transactions</h3>
-
- <p class="note">
- Add note that we may be able to handle this section entirely within
- the consent definition, rather than calling it out; potentially
- thought an example in the consent section. Concern about UI creep.
- </p>
- <p class="issue" data-number="65" title="How does logged in and logged out state work"></p>
-<!--
-<p class="note">I believe we have consensus that the spec should be silent on
-the relevance of "logged-in" versus "logged-out" state. I am deleting the
-various options on this issue, but we can revisit if people object.</p>
--->
- </section>
</section>
<section id="noncompliant-UA">
Received on Thursday, 4 October 2012 14:17:14 UTC