--- a/ED-tracking-tsl.html Fri Jan 20 16:11:11 2012 -0500
+++ b/ED-tracking-tsl.html Fri Jan 20 16:24:38 2012 -0500
@@ -30,7 +30,7 @@
<p class="issue">Should we change the name for something more generic. It could be URL Filtering Lists or something along. The formats allow more applications than just tracking.</p>
-<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>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 Web sites 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
@@ -57,20 +57,24 @@
<p>This section is non-normative</p>
-<p>Today, consumers share information with more websites than the ones they see in the address bar in their browser. This is inherent in the design of the web and simply how the web works, and it has potentially unintended consequences. As consumers visit one site, many other sites receive information about their activities. For example, when a webpage includes a third-party image file—such as a “web beacon”—IP address information, cookies, and referrer data can be sent. A third-party script can have additional impact on user privacy and can collect arbitrary data from the first-party webpage.</p>
-<p>This situation results from how modern websites are built. Typically, a website today might bring together content from many other websites, leaving the impression that the website appears to be its own entity. When the browser calls any other website to request anything (an image, a cookie, HTML, a script that can execute), the browser explicitly provides information in order to get information. By limiting data requests to these sites, it is possible to limit the data available to these sites for collection and tracking.</p>
-<p>A selection list contains parts of third-party URIs that a browser may access automatically when referenced within a web page a user deliberately visits.</p>
+<p>When accessing the Web, users will download Web page which are the agglomeration of multiple resources (visible and not visible). By accessing these resources, the users share information with the owner of these resources. This is inherent in the design of the Web and simply how the Web works, and it has potentially unintended consequences. As users visit one site, many other sites receive information about their activities. For example, when a Web page includes an image file (coming from a different domain), IP address information, cookies, and referrer data can be sent by the user's browser. A script can have additional impact on user privacy and could collect arbitrary data from the initial Web page.</p>
-<p class="issue">Should TSLs also apply to 1<sup>st</sup>-party URIs? If so, there should probably be an option that does this – I think that by default, most of the rules you’d want to write are 3<sup>rd</sup>-party specific. There are valid use cases for 1<sup>st</sup>-party rules, such as CNAME’d DNS entries.</p>
+<p class="issue">We could create a very simple infography showing a simple HTTP request and its consequences to illustrate the paragraph above.</p>
+
+<p>This situation results from how Web sites are built. Typically, a Web site today might bring together content from many other Web sites, leaving the impression that the Web site appears to be its own entity. When the browser calls any other Web site to request anything (an image, a cookie, HTML, a script that can execute), the browser explicitly provides information in order to get information. By limiting requests to these sites, it is possible to limit the data available to these sites, including those used for collection and tracking.</p>
+
+<p>A selection list contains parts of third-party URIs that a browser may access automatically when referenced within a Web page a user deliberately visits.</p>
+
+<p class="issue">Should TSLs also apply to 1<sup>st</sup>-party URIs? If so, there should probably be an option that does this – I think that by default, most of the rules you’d want to write are 3<sup>rd</sup>-party specific. There are valid use cases for 1<sup>st</sup>-party rules, such as CNAME’d DNS entries.</p>
<p class="issue">Karl Dubost: It assumes that tracking is made
only through 3rd party uris.</p>
<p class="issue">[andyzei] There is a difference between “expected” and “unexpected” tracking. 1<sup>st</sup>-party tracking is expected. 3<sup>rd</sup>-party tracking is not. </p>
-<p>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 selection list limits the information other sites can collect about a user.</p>
+<p>Rules in a selection list may change the way the user agent handles third-party content. By limiting the calls to these Web sites and blocking resources from other Web pages, the selection list limits the information other sites can collect about a user.</p>
</section>
<section>
@@ -96,7 +100,7 @@
<h3 id="blocking-downloads">Blocking Downloads</h3>
-<p >When a user agent issues a request for a webpage and receives an HTTP status code that returns a document, and the user or user agent has chosen to apply a selection list, all third-party URIs that can generate a download request must be evaluated against this selection list. </p>
+<p >When a user agent issues a request for a Webpage and receives an HTTP status code that returns a document, and the user or user agent has chosen to apply a selection list, all third-party URIs that can generate a download request must be evaluated against this selection list. </p>
<div class="issue">
<p>incorrect sentence. Maybe something along the following paragraph will be the real implementable requirement. </p>