- From: Nick Doty via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 07 May 2012 08:07:26 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts In directory hutz:/tmp/cvs-serv32285 Modified Files: tracking-compliance.html Log Message: marking sections as non-normative with class attributes Index: tracking-compliance.html =================================================================== RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html,v retrieving revision 1.54 retrieving revision 1.55 diff -u -d -r1.54 -r1.55 --- tracking-compliance.html 2 May 2012 15:46:10 -0000 1.54 +++ tracking-compliance.html 7 May 2012 08:07:24 -0000 1.55 @@ -481,8 +481,8 @@ necessarily determinative of, user perceptions of whether two parties are distinct. </p> </section> - <section id="partyDiscussion"> -<h2>Non-Normative Discussion</h2> + <section id="partyDiscussion" class="informative"> +<h2>Discussion</h2> <p>Our definition of what constitutes a "party" is guided by ordinary user expectations. We decline to adopt a conflicting approach that @@ -563,7 +563,7 @@ <h1>Option 2: Discoverable Affiliates</h1> <section id="party2norm"> -<h2>Normative Discussion</h2> +<h2>Definition</h2> <p> A party is any commercial, nonprofit, or governmental organization, a subsidiary or unit of such an organization, or a person. For unique corporate entities to qualify as a common party @@ -571,8 +571,8 @@ and commonly controlled, and MUST make their parent affiliation (if any) easy discoverable to users. </p> </section> - <section id="party2nonnorm"> -<h2>Non-Normative Discussion</h2> <p>This may be accomplished in many ways, + <section id="party2nonnorm" class="informative"> +<h2>Discussion</h2> <p>This may be accomplished in many ways, including but not limited to, prominent and common branding on site pages, "one click away" within Privacy Policies, and, if available, a programmatic list of domains that share common ownership (affiliation).</p> @@ -603,8 +603,8 @@ implementable as-is.</p> </section> - <section id="firstThirdPartiesDiscussion"> -<h2>Non-Normative Discussion</h2> + <section id="firstThirdPartiesDiscussion" class="informative"> +<h2>Discussion</h2> <section id="firstThirdPartiesOverview"> <h2>Overview</h2> @@ -751,7 +751,7 @@ <section id="op2aff" class="option"> <h3>Option 2: Discoverable Ownership and Affiliates</h3> -<p class="note">This language merely rehashes the discoverable affiliate definition of "party" and does not provide guidance as to when a party is operating on a first-party or third-party basis. This language would be better incorporated as non-normative discussion under the Option 2: Discoverable Affiliates definition of party above.</p> +<p class="note">This language merely rehashes the discoverable affiliate definition of "party" and does not provide guidance as to when a party is operating on a first-party or third-party basis. This language would be better incorporated as non-normative discussion under the Option 2: Discoverable Affiliates definition of party above.</p> <section id="firstThirdPartiesDefn2"> <h3>Definitions</h3> @@ -858,8 +858,8 @@ other sequence of logically related network traffic. </p> </section> -<section id="networkInteractionDiscussion"> -<h2>Non-Normative Discussion</h2> +<section id="networkInteractionDiscussion" class="informative"> +<h2>Discussion</h2> <p>Determination of a party's status is limited to a single interaction because a party's status may be affected by time, @@ -899,8 +899,8 @@ <p>The definitions of collection, retention, use, and sharing are drafted expansively so as to comprehensively cover a party's user-information -practices. These definitions do not require a party's intent; a party may -inadvertently collect, retain, use, or share data. The definition of +practices. These definitions do not require a party's intent; a party may +inadvertently collect, retain, use, or share data. The definition of collection includes information that a party did not cause to be transmitted, such as protocol headers. </p> @@ -1211,7 +1211,8 @@ notice to user(s).</li></ol> -<p>Examples and use cases</p> + <section id="compl2-examples" class="informative"> + <h3>Examples and use cases</h3> <ol><li>User visits Site A, to which Ad Network B delivers advertisements. Ad Network B has accumulated transactional information about User from User’s visits to Site A and other @@ -1234,6 +1235,7 @@ transmitted with HTTP.</li> </ol> </section> + </section> </section> @@ -1254,8 +1256,8 @@ location data, than that consent prevails. </li> </ol> -<section> -<h3>Non-Normative Discussion</h3> +<section class="informative"> +<h3>Discussion</h3> <p>It is acceptable to use data sent as part of this particular network interaction when composing a response to a [DNT-ON] request, but it is @@ -1268,8 +1270,6 @@ levels of detail may feel invasive to users, and may violate their expectations about Do Not Track. These sorts of detailed assessments should be avoided.</p> -</section> - <section> <h3>Examples</h3> <dl> @@ -1293,6 +1293,7 @@ made on the fly, and the information was only held ephemerally.</p> </section> </section> +</section> @@ -1397,7 +1398,7 @@ : Still have "operational use" of data (auditing of where ads are shown, impression tracking, etc.)</p> - <section id = "TypesofTrackingOperationalNorm"> + <section id = "TypesofTrackingOperationalNorm" class="informative"> <h2>Discussion</h2> <p>In order to preserve certain common and important data usages, while @@ -1470,8 +1471,8 @@ <section id = "TypesofTrackingOutsourcingNorm"> -<h2>Normative Discussion</h2> -A third-party site may operate as a first-party site if all the +<h2>Requirements</h2> +A third-party site MAY operate as a first-party site if all the following conditions hold:</p> <ol> <li>the third party's data collection, retention, and use practices @@ -1490,8 +1491,7 @@ </ol> </section> -<section id="TypesofTrackingOutsourcingDiscussion"> <h2>Non-Normative -Discussion</h2> +<section id="TypesofTrackingOutsourcingDiscussion" class="informative"> <h2>Discussion</h2> <section id="TypesofTrackingOutsourcingOverview"><h2>Overview</h2> @@ -1537,9 +1537,8 @@ href="http://www.w3.org/2011/tracking-protection/track/issues/34">ISSUE-34</a> : Possible permitted use for aggregate analytics</p> - <section id = "TypesofTrackingUnidentNorm"> <h2>Normative -Discussion</h2> - <p>A third party may collect, retain, and use any information from a + <section id = "TypesofTrackingUnidentNorm"> <h2>Requirements</h2> + <p>A third party MAY collect, retain, and use any information from a user or user agent that, with high probability, could not be used to:</p> <ol> <li>identify or nearly identify a user or user agent; or</li> @@ -1548,8 +1547,8 @@ </ol> </section> -<section id="TypesofTrackingUnidentDiscussion"> <h2>Non-Normative - Discussion</h2> +<section id="TypesofTrackingUnidentDiscussion" class="informative"> + <h2>Discussion</h2> <section id="TypesofTrackingUnidentOverview"><h2>Overview</h2> <p class="note"> Clarification is needed with regard to what is @@ -1834,7 +1833,7 @@ <h3>Enforcement/Compliance</h3> <section id="complinormative"> - <h2>Normative discussion</h2> + <h2>Requirement</h2> <p class="note">Final wording awaits how the response is designed in the [[!TRACKING-DNT]] recommendation, but we agree upon the general direction below.</p> @@ -1842,8 +1841,8 @@ public commitment that it complies with this standard.</p> </section> -<section id="complinonnormative"> - <h2>Non-normative discussion</h2> +<section id="complinonnormative" class="informative"> + <h2>Discussion</h2> <p>A "public commitment" may consist of a statement in a privacy policy, a response header, a machine-readable tracking status resource at a well-known location, or any other reasonable means. This standard does not require a
Received on Monday, 7 May 2012 08:07:30 UTC