- From: Roy Fielding via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 28 Sep 2012 07:55:34 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv30473
Modified Files:
tracking-compliance.html tracking-dnt.html
Log Message:
fix two typos and numerous mark-up errors found via tidy
Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.165
retrieving revision 1.166
diff -u -d -r1.165 -r1.166
--- tracking-dnt.html 28 Sep 2012 07:13:17 -0000 1.165
+++ tracking-dnt.html 28 Sep 2012 07:55:31 -0000 1.166
@@ -27,7 +27,7 @@
noIDLSectionTitle: true,
};
</script>
- <link rel="stylesheet" href="additional.css" type="text/css" media="screen" title="custom formatting for TPWG editors" charset="utf-8">
+ <link rel="stylesheet" href="additional.css" type="text/css" media="screen" title="custom formatting for TPWG editors" charset="utf-8" />
</head>
<body>
<section id='abstract'>
@@ -306,7 +306,7 @@
<td>This user prefers not to be tracked on the target site.</td>
</tr>
<tr><td align="middle">0</td>
- <td>This user prefers to allow tracking on the target site.<td>
+ <td>This user prefers to allow tracking on the target site.</td>
</tr>
</table>
</p>
@@ -361,7 +361,7 @@
there is not a site-specific exception for the origin server
targeted by this request.
</p>
- </p>
+ <p>
The DNT field-value sent by a user agent MUST begin with the
numeric character "0" (%x30) if a tracking preference is
<a>enabled</a>, and the preference is to allow tracking in general
@@ -690,27 +690,27 @@
<tr><td align="middle">a</td>
<td>Audit: Tracking is limited to that necessary for an
external audit of the service context and the data
- collected is minimized accordingly.<td>
+ collected is minimized accordingly.</td>
</tr>
<tr><td align="middle">c</td>
<td>Ad frequency capping: Tracking is limited to frequency
- capping and the data collected is minimized accordingly.<td>
+ capping and the data collected is minimized accordingly.</td>
</tr>
<tr><td align="middle">f</td>
<td>Fraud prevention: Tracking is limited to that necessary
for preventing or investigating fraudulent behavior and
security violations; the data collected is minimized
- accordingly.<td>
+ accordingly.</td>
</tr>
<tr><td align="middle">l</td>
<td>Local constraints: Tracking is limited to what is
required by local law, rule, or regulation and the
- data collected is minimized accordingly.<td>
+ data collected is minimized accordingly.</td>
</tr>
<tr><td align="middle">r</td>
<td>Referrals: Tracking is limited to collecting referral
information and the data collected is minimized
- accordingly.<td>
+ accordingly.</td>
</tr>
</table>
<p>
@@ -1093,6 +1093,7 @@
Note that the tracking status resource space applies equally to
both first-party and third-party services. An example of a
third-party tracking status is
+ </p>
<pre class="example">
{
"tracking": "3",
@@ -1807,6 +1808,7 @@
the user, and guide. The call to the API and the resulting request for
user confirmation should not be a 'surprise' to the user, or require
much explanation on the part of the user-agent.
+ </p>
<p>
A user agent that chooses to implement a prompt to present tracking
exception requests to the user might provide an interface like the
Index: tracking-compliance.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -d -r1.74 -r1.75
--- tracking-compliance.html 28 Sep 2012 07:13:17 -0000 1.74
+++ tracking-compliance.html 28 Sep 2012 07:55:31 -0000 1.75
@@ -117,10 +117,10 @@
<p>This specification uses the term user agent to refer to any of the various client programs capable of initiating HTTP requests, including but not limited to browsers, spiders (web-based robots), command-line tools, native applications, and mobile apps [[!HTTP11]].</p>
-<p class=note>The has been recent discussion about whether the specification should differentiate among different
+<p class=note>There has been recent discussion about whether the specification should differentiate among different
types of users agents (such as general purpose browsers, add-ons, and stand-alone software programs), and
possibly specify different compliance obligations depending on the type of user agent, or priority among different
-categories of user agents in the event of conflicting settings.</br></br>There is currently no open ISSUE associated with
+categories of user agents in the event of conflicting settings. There is currently no open ISSUE associated with
this discussion.</p>
</section>
@@ -386,7 +386,7 @@
<section id="first-third-parties">
<h3>First and Third Parties</h3>
- <section class="option" id="def-first-third-parties-opt-1"><h4>Option 1: First and Third Parties</h5>
+ <section class="option" id="def-first-third-parties-opt-1"><h4>Option 1: First and Third Parties</h4>
<section><h4>Definitions</h4>
<p>A <dfn>first party</dfn> is any <a>party</a>, in a specific <a>network interaction</a>,
@@ -510,7 +510,7 @@
<p class=option>There can be only one first party in any network transaction absent additional meaningful interaction with otherwise third party content on the webpage. The first party is the registrant and operator of the domain that the user intentionally communicated with.</p>
-<p class=option>If a user intends to communicate with a party that utilizes a different party as a platform, then both parties are first parties in the network transaction.<br><br><i>Example:</i> ExampleSports franchise has a dedicated page on a ExampleSocial. When a user visits this dedicated page, both ExampleSports and ExampleSocial are first parties.</p>
+<p class=option>If a user intends to communicate with a party that utilizes a different party as a platform, then both parties are first parties in the network transaction.<br /><br /><i>Example:</i> ExampleSports franchise has a dedicated page on a ExampleSocial. When a user visits this dedicated page, both ExampleSports and ExampleSocial are first parties.</p>
</section>
<section>
@@ -547,14 +547,14 @@
<section class="option" id="def-first-third-parties-opt-2"><h5>Option 2: First and Third Parties</h5>
<p>First Party is the party that owns the Web site or has control over the Web site the consumer visits. A First Party also includes the owner of a widget, search box or similar
service with which a consumer interacts.</p>
-<pclass="note">If a user merely mouses over, closes, or mutes third-party content, that is not
+<p class="note">If a user merely mouses over, closes, or mutes third-party content, that is not
sufficient interaction to constitute a First Party widget interaction.</p><p>
A Third Party is any party other than a First Party, Service Provider, or the user.
It is possible to have multiple first parties on a single page but each party must provide
clear branding and a link to their respective privacy policy (co-branded experience).
</p>
</section>
-<!-- <p class="issue" data-number="26" title="Providing data to 3rd-party widgets -- does that imply consent?"></p> -->
+<!-- <p class="issue" data-number="26" title="Providing data to 3rd-party widgets — does that imply consent?"></p> -->
</section>
@@ -672,7 +672,7 @@
<p class="option">Shane's proposal has suggested the additional compliance requirements of user agents:<br />1. The User Agent must also make available via a link in explanatory text where DNT is enabled to provide more detailed information about DNT functionality<br />2. Any User Agent claiming compliance must have a functional implementation of the browser exceptions in this specification</p>
<p class="issue" data-number="150" title="DNT conflicts from multiple user agents"></p>
-<p class=issue data-number=153 title="What are the implications on software that changes requests but does not necessarily initiate them?"</p>
+<p class="issue" data-number="153" title="What are the implications on software that changes requests but does not necessarily initiate them?"></p>
</section>
@@ -776,10 +776,10 @@
<h5>Security and Fraud Prevention</h5>
<p>Regardless of DNT signal, information may be collected, retained and used for detecting security risks and fraudulent activity, defending from attacks and fraud, and maintaining integrity of the service. This includes data reasonably necessary for enabling authentication/verification, detecting hostile transactions and attacks, providing fraud prevention, and maintaining system integrity. In this example specifically, this information may be used to alter the user's experience in order to reasonably keep a service secure or prevent fraud.</p>
-<p class="note">The more likely options at this point may be represented in Nick Doty's proposed:<br><br>
+<p class="note">The more likely options at this point may be represented in Nick Doty's proposed:<br /><br />
To the extent reasonably necessary for protection of computers and networks and to detect ad or other fraud, third parties may engage in tracking.
-Use of graduated response is preferred.<br><br>
-or David Wainburg's proposed<br><br>
+Use of graduated response is preferred.<br /><br />
+or David Wainberg's proposed<br /><br />
Parties may collect and use data in any way to the extent reasonably necessary for the detection and prevention of malicious or illegitimate activity.</p>
<section class="informative" id="security-example"><h6>Examples</h6>
@@ -856,7 +856,7 @@
information that a user agent necessarily shares with a web server when it communicates
with the web server (e.g. IP address and User-Agent), and the URL of the top-level page,
communicated via a Referer header or other means, unless the URL contains information
-that is not unlinkable (e.g. a username or user ID).</br></br>A third party may not
+that is not unlinkable (e.g. a username or user ID).<br /><br />A third party may not
collect, use, or retain information that a web server could cause to not be sent but
still be able to communicate with the user agent (e.g. a cookie or a Request-URI
parameter generated by the user agent), except the URL of the top-level page, or any data
@@ -874,10 +874,10 @@
<p class="issue" data-number="24" title="Possible permitted use for fraud detection and defense"></p>
<p class="issue" data-number="25" title="Possible permitted use for research purposes"></p>
<p class="issue" data-number="75" title="How do companies claim permitted uses and is that technical or not?"></p>
-<p class="issue" data-number="31" title="Minimization -- to what extent will minimization be required for use of a particular permitted use? (conditional permitted uses)"></p>
+<p class="issue" data-number="31" title="Minimization — to what extent will minimization be required for use of a particular permitted use? (conditional permitted uses)"></p>
<p class="issue" data-number="92" title="If data collection (even very specific with IP address, user agent, referrer) is time-limited, with very limited retention, is that still tracking?"></p>
<p class="issue" data-number="89" title="Does DNT mean at a high level: (a) no customization, users are seen for the first time, every time. (b) DNT is about data moving between sites."></p>
-<p class="issue" data-number="97" title="Re-direction, shortened URLs, click analytics -- what kind of tracking is this?"></p>
+<p class="issue" data-number="97" title="Re-direction, shortened URLs, click analytics — what kind of tracking is this?"></p>
-->
</section></section>
<section id="geolocation">
Received on Friday, 28 September 2012 07:55:40 UTC