third party is vaguely defined in compliance and not in the way we are using it in this document
authorKarl Dubost <karld@opera.com>
Fri, 20 Jan 2012 16:11:11 -0500
changeset 6 dbb3717b3ad9
parent 5 135307fe3a31
child 7 0f4f2d71a975
third party is vaguely defined in compliance and not in the way we are using it in this document
ED-tracking-tsl.html
--- a/ED-tracking-tsl.html	Fri Jan 20 15:41:59 2012 -0500
+++ b/ED-tracking-tsl.html	Fri Jan 20 16:11:11 2012 -0500
@@ -32,6 +32,12 @@
 
 <p>A <dfn id="selection-list">selection list</dfn> contains parts of <a href="#dfn-third-party-uri">third-party URIs</a> that a browser may access automatically when referenced within a web page that a user deliberately visits. Rules in a selection list may change the way the user agent handles third-party content. By limiting the calls to these websites and blocking resources from other web pages, the <a href="#dfn-filter-list">selection list</a> limits the information other sites can collect about a user.</p>
 
+<p class="issue"><strong>Third-party URIs</strong> might be confusing when reading along the two other Tracking Protection WG documents. The <a href="http://www.w3.org/2003/glossary/keyword/All/third-party.html?keywords=third-party">XLink definition</a> doesn't help either. The third party is vaguely <a href="http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#firstThirdPartiesDefn">defined</a> in the compliance document with <q>
+    A "third party" is any party, in a specific 
+   network interaction, that cannot infer with 
+   high probability that the user knowingly and 
+   intentionally communicated with it.</q></p>
+
 </section>
 
 <section>