CVS WWW/2011/tracking-protection/drafts

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

Modified Files:
	tracking-dnt.html 
Log Message:
updating notes per teleconference

--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2013/04/24 04:41:23	1.206
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2013/04/25 23:52:46	1.207
@@ -278,6 +278,7 @@
         Implementations of HTTP that are not under control of the user
         MUST NOT generate or modify a tracking preference.
       </p>
+      <p class="issue" data-number="136" title=" Resolve dependencies of the TPE on the compliance specification">Some participants have noted that enabled/not-enabled status may depend on the Compliance document or may have varying implications in different jurisdictions.</p>
     </section>
 
     <section id='expressing'>
@@ -1551,14 +1552,11 @@
              <code>widgets.exsocial.org</code> are both
              <strong>targets</strong>.
           </p>
-          <p class="issue" data-number="112" title="How are sub-domains handled for site-specific exceptions?">
-            <b>[PENDING REVIEW]</b> Should a request for a tracking exception
-            apply to all subdomains of the first party making the request? Or
-            should a first party explicitly list the subdomains that it's
-            asking for? Similarly, should third-party subdomains be allowed
-            (e.g. *.tracker.com)? <br />
-            <b>Proposal</b>: Exceptions are requested for fully-qualified
-            domain names.
+          <p class="issue" data-number="112" title="How are sub-domains
+          handled for site-specific exceptions?"> 
+            <b>[PENDING REVIEW]</b> In the current proposal a
+            <code>domain</code> parameter allows exceptions to apply to
+            sub-domains in the same way as cookies.
           </p>
           <p>
             The domains that enter into the behavior of the APIs include:
@@ -2176,8 +2174,8 @@
         </p>
       </section>
       
-      <section id="exceptions-by-sites">
-       <h3>Exception use by sites (informative)</h3>
+      <section id="exceptions-by-sites" class="informative">
+       <h3>Exception use by sites</h3>
 
 		<p>This section is to inform the authors of sites on some considerations 
 		 in using the exceptions APIs to best effect; sites of particular interest 

Received on Thursday, 25 April 2013 23:52:47 UTC