- From: CVS User npdoty <cvsmail@w3.org>
- Date: Tue, 09 Apr 2013 17:51:24 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts In directory gil:/tmp/cvs-serv10661 Modified Files: tracking-compliance.html Log Message: justin's changes from April 9 --- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2013/03/06 23:31:50 1.87 +++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2013/04/09 17:51:24 1.88 @@ -148,10 +148,16 @@ <section id="scope-and-goals"> <h2>Scope and Goals</h2> - <p class="issue" data-number="6" title="What are the underlying concerns? Why are we doing this?"> - This section will be re-worked after details of substantive text - is closer to being finalized. + This specification is designed to provide users a simple machine-readable + preference expression mechanism to globally or selectively allow or limit + online tracking. + "Tracking" is understood by this standard as the collection and + retention of data across multiple parties' domains or services in a form + such that it can be attributed to a specific user, user agent, or device. </p> + + <p class=note>The scope language is not at consensus, but is an effort by + the editors to offer a provisional definition of tracking.</p> <!-- <p> While there are a variety of business models to monetize content on the web, many rely on advertising. Advertisements can be targeted to a @@ -371,7 +377,7 @@ <p class="note">hwest to propose an alternative definition of first party (based on ownership? alternative to inference?) [recorded in http://www.w3.org/2012/07/11-dnt-minutes.html#action01]</p> ---> +---> </section> @@ -386,7 +392,27 @@ over a branded/labelled embedded widget, search box, or similar service with which a user intentionally interacts is also considered a First Party. If a user merely mouses over, closes, or mutes such content, that is not sufficient - interaction to render the party a first party.</p></section> + interaction to render the party a first party.</p> + + <section id=multiple-first-parties> + <h4>Multiple First Parties> + + <p>In most network interactions, there will be only one first party with which + the user intends to interact. However, in some cases, a network resource will + be jointly operated by two or more parties, and a user would reasonably expect + to communicate with all of them by accessing that resource. User understanding + that multiple parties operate a particular resource could be accomplished + through inclusion of multiple parties' brands in a URI, or prominent branding + on the resource indicating that multiple parties are responsible for content or + functionality on the resource with which a user reasonably would expect to + interact by accessing the resource. Simple branding of a party that merely + serves as a service provider to the single entity providing a resource will not + be sufficient to make that party a first party in any particular network + interaction. + + <p class=note>The language on multiple first parties is not yet at consensus.</p> + </section> + </section> <section id=third-party> <h3>Third Party</h3> @@ -650,7 +676,7 @@ A site that is operated on behalf of multiple legal entities is considered to have a joint first party if a user's expectation would be that each of those entities have control over the data - collected.</p> --> + collected.</p> ---> <!-- <p class="issue" data-number="26" title="Providing data to 3rd-party widgets — does that imply consent?"></p> --> <section id="def-unlinkable"> <h3>Deidentified Data</h3> @@ -692,7 +718,7 @@ limited to a single interaction because a party's status may be affected by time, context, or any other factor that influences user expectations. - </p> --> + </p> ---> </section> <section id="def-collection"> @@ -1349,7 +1375,7 @@ about the domain of the news site in order to render weather information related to the city which ExampleLocalNews reports on.</li> - </ol> --> + </ol> ---> </section> <section id="first-party-data"> @@ -1407,7 +1433,7 @@ profile, and may only retain and use information about that fact for a permitted operational use.</li> </ol> - </section> --> + </section> ---> </section> <section id="frequency-capping"> @@ -1547,6 +1573,17 @@ <p class="note">Add examples once we pick an option.</p> --> + <section id=audience-measurement> + <h5>Audience Measurement</h5> + + <p class=note>The group has recently debated whether to include a + permitted use for the collection of third-party data to calibrate + audience measurement primarily conducted through the use of opt-in + panels. The most recent proposal by ESOMAR is available here: + http://lists.w3.org/Archives/Public/public-tracking/2013Mar/0335.html + but the language is not consensus, and the working group has not + decided whether such a permitted use is even appropriate.</p></section> + <section id="compliance"> <h5>Compliance With Local Laws and Public Purposes</h5>
Received on Tuesday, 9 April 2013 20:36:31 UTC