CVS WWW/2011/tracking-protection/drafts

Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv9843

Modified Files:
	tracking-dnt.html 
Log Message:
(editorial) fix mark-up validation errors

--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2015/03/24 17:35:37	1.284
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2015/03/24 22:05:47	1.285
@@ -488,13 +488,13 @@
         A user agent MUST NOT send a tracking preference expression if
         a tracking preference is <a>not enabled</a>.  This means that no
         expression is sent for each of the following cases:
-        <ul>
-          <li>the user agent does not implement this protocol;</li>
-          <li>the user has not yet made a choice for a specific preference;
-              or,</li>
-          <li>the user has chosen not to transmit a preference.</li>
-        </ul>
       </p>
+      <ul>
+        <li>the user agent does not implement this protocol;</li>
+        <li>the user has not yet made a choice for a specific preference;
+            or,</li>
+        <li>the user has chosen not to transmit a preference.</li>
+      </ul>
       <p>
         In the absence of regulatory, legal, or other requirements, servers
         MAY interpret the lack of an expressed tracking preference as they
@@ -740,28 +740,28 @@
         </p>
         <p>
           If <code>G</code> is present in the site-wide tracking status:
-          <ul>
-            <li>the gateway MUST send a link within its site-wide
-              tracking status representation to a privacy policy that
-              explains what limitations are placed on parties that
-              might receive data via that gateway;</li>
-            <li>the gateway MUST forward any expressed tracking
-              preference in the request to each party that receives data
-              from that request;</li>
-            <li>the gateway MUST have a contract in place with each of the
-              parties to whom it provides request data such that only the
-              selected party is allowed to retain tracking data from a
-              request with an expressed tracking preference of
-              <code><a>DNT:1</a></code>; and,</li>
-            <li>the gateway MUST send a <a>Tk</a> header field in
-              responses to requests on the designated resource and include
-              within that field's value a <code><a>status-id</a></code>
-              specific to the selected party, such that information about
-              the selected party can be obtained via the request-specific
-              tracking status resource (see
-              <a href="#request-specific-status-resource" class="sectionRef"></a>).
-          </ul>
         </p>
+        <ul>
+          <li>the gateway MUST send a link within its site-wide
+            tracking status representation to a privacy policy that
+            explains what limitations are placed on parties that
+            might receive data via that gateway;</li>
+          <li>the gateway MUST forward any expressed tracking
+            preference in the request to each party that receives data
+            from that request;</li>
+          <li>the gateway MUST have a contract in place with each of the
+            parties to whom it provides request data such that only the
+            selected party is allowed to retain tracking data from a
+            request with an expressed tracking preference of
+            <code><a>DNT:1</a></code>; and,</li>
+          <li>the gateway MUST send a <a>Tk</a> header field in
+            responses to requests on the designated resource and include
+            within that field's value a <code><a>status-id</a></code>
+            specific to the selected party, such that information about
+            the selected party can be obtained via the request-specific
+            tracking status resource (see
+            <a href="#request-specific-status-resource" class="sectionRef"></a>).</li>
+        </ul>
         <p>
           With respect to tracking performed by the gateway itself, the
           <code>G</code> response can be considered equivalent
@@ -1362,7 +1362,7 @@
           how one might implement an out-of-band consent mechanism are
           beyond the scope of this protocol.
         </p>
-        </p>
+        <p>
           If no <code>config</code> property is provided, this
           information might be obtained via the links provided in
           <code><a>controller</a></code> or <code><a>policy</a></code>.
@@ -1554,19 +1554,21 @@
         </p>
         <p>
           The user agent MAY provide interfaces to the user:
-          <ul>
-            <li>To indicate that a call to store an exception has just been
-              made;</li>
-            <li>To allow the user to confirm a user-granted exception prior
-              to storage;</li>
-            <li>To indicate that one or more exceptions exist for the
-              current top-level origin;</li>
-            <li>To indicate that one or more exceptions exist for sites
-              incorporated into the current page;</li>
-            <li>To allow the user to see and possibly revoke stored
-              exceptions;
-            <li>Other aspects of the exception mechanism, as desired.</li>
-          </ul>
+        </p>
+        <ul>
+          <li>To indicate that a call to store an exception has just been
+            made;</li>
+          <li>To allow the user to confirm a user-granted exception prior
+            to storage;</li>
+          <li>To indicate that one or more exceptions exist for the
+            current top-level origin;</li>
+          <li>To indicate that one or more exceptions exist for sites
+            incorporated into the current page;</li>
+          <li>To allow the user to see and possibly revoke stored
+            exceptions;</li>
+          <li>Other aspects of the exception mechanism, as desired.</li>
+        </ul>
+        <p>
           There is no required user interface for the user agent; 
           a user agent MAY choose to provide no user interface regarding 
           user-granted exceptions.
@@ -1658,13 +1660,13 @@
           A pair of duplets [A,B] and [X,Y] match if A matches X and B matches Y. 
           A pair of values A and X match if and only if one of the following 
           is true:
-          <ul>
-            <li>either A or X is "*";</li>
-            <li>A and X are the same string;</li>
-            <li>A has the form '*.domain' and X is 'domain' or is of the 
-          form 'string.domain', where 'string' is any sequence of characters.</li>
-          </ul>
         </p>
+        <ul>
+          <li>either A or X is "*";</li>
+          <li>A and X are the same string;</li>
+          <li>A has the form '*.domain' and X is 'domain' or is of the form
+            'string.domain', where 'string' is any sequence of characters.</li>
+        </ul>
         <p>
           In addition, responses to the JavaScript API indicated should be
           consistent with this user preference (see below).
@@ -2010,12 +2012,12 @@
 
         <dl class="idl" title='partial interface Navigator'>
           <dt>boolean confirmWebWideTrackingException( ConfirmExceptionPropertyBag properties )</dt>
+          <dd>
+            Confirms that there exists in the database a web-wide exception
+            for a specific site.
+          </dd>
         </dl>
         <p>
-          This API confirms the existence of a
-          web-wide grant for a specific site, in the database.
-        </p>
-        <p>
           The returned boolean indicates whether the duplet
           <code>[ * , document-origin]</code> or <code>[ * , *.domain]</code>
           (based on if <code>domain</code> is provided and is not null and
@@ -2188,15 +2190,15 @@
       </p>
       <p>
         In this way the site:
-        <ul>
-          <li>does not assume that the storage is instantaneous, and
-            mistakenly grant access when the exception does not (yet) stand;</li>
-          <li>does not call the Confirm API repeatedly without a
-            user-interaction between each call, in a loop;</li>
-          <li>permits the user the opportunity to delete a previously
-          granted exception.</li>
-        </ul>
       </p>
+      <ul>
+        <li>does not assume that the storage is instantaneous and
+          mistakenly grant access when the exception does not (yet) stand;</li>
+        <li>does not call the Confirm API repeatedly, in a loop, without a
+          user-interaction between each call; and,</li>
+        <li>permits the user the opportunity to delete a previously
+        granted exception.</li>
+        </ul>
     </section>
 
     <section id="exceptions-fingerprinting">

Received on Tuesday, 24 March 2015 22:05:50 UTC