CVS WWW/2011/tracking-protection/drafts

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

Modified Files:
	tracking-dnt.html 
Log Message:
(editorial) reduce usage of the word context to either the defined term or the browser context

--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2014/01/15 20:55:36	1.235
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2014/02/22 04:56:33	1.236
@@ -136,8 +136,8 @@
         data about them to be collected. Many Internet companies use data
         gathered about people's online activities to personalize content and
         target advertising based on their perceived interests. While some
-        people appreciate this personalization of content and ads in certain
-        contexts, others are troubled by what they perceive as an invasion of
+        people appreciate this personalization of content and ads,
+        others are troubled by what they perceive as an invasion of
         their privacy. For them, the benefit of personalization is not worth
         their concerns about allowing entities with whom they have no direct
         relationship to amass profiles about their activities.
@@ -235,7 +235,7 @@
           examples of ways to provide this discoverability.
         </p>
         <p>
-          Within the context of a given user action, a <dfn>first party</dfn>
+          With respect to a given user action, a <dfn>first party</dfn>
           is a party with which the user intends to interact, via one or more
           network interactions, as a result of making that action. Merely
           hovering over, muting, pausing, or closing a given piece of content
@@ -513,17 +513,19 @@
       <section id='js-dom'>
         <h3>JavaScript Property to Detect Preference</h3>
           <p>
-              This property enables a site executing code in its own origin
-              to determine what DNT header would be sent to it in the current
-              context, taking into account the user's general preference (if
-              any) and any user-granted exceptions.</p>
+              This property enables a client-side script with read access to
+              the Window object to determine what DNT header field value would
+              be sent to the same origin server, taking into account the
+              user's general preference (if any) and any user-granted
+              exceptions applicable to that origin.
+          </p>
           <dl class="idl" title='partial interface Window'>
             <dt>readonly attribute DOMString doNotTrack</dt>
             <dd>Returns the same string value that would be sent in a
               <a>DNT-field-value</a>
               (<a href="#dnt-header-field" class="sectionRef"></a>) to a
               <strong>target</strong> that is the document-origin of the
-              <code>window</code>, in the context of the current
+              <code>window</code>, in the browser context of the current
               <strong>top-level origin</strong>.
               The value is <code>null</code> if no DNT header field would be
               sent (e.g., because a tracking preference is <a>not enabled</a>).
@@ -1583,7 +1585,8 @@
             sent in a given request include:
           </p>
           <ul>
-            <li>The <strong>top-level origin</strong> of the current context;</li>
+            <li>The <strong>top-level origin</strong> of the current browser
+                context;</li>
             <li>The <strong>target</strong> of the request.</li>
           </ul>
           <p class="note">
@@ -1625,11 +1628,11 @@
 
 
           <p class="issue" data-number="159" title="How do we allow sites that mash-in ad-supported content to maintain their own trusted third parties?">
-            [POSTPONED] This model does not support mashed-up content which is in turn
-            supported by ads; it's not clear how to distinguish between
-            embedded content which is embedding ads (and hence the top-level
-            origin stays the same) and embedded content that should start a
-            new context.<br />
+            [POSTPONED] This model does not support mashed-up content which is
+            in turn supported by ads; it's not clear how to distinguish
+            between embedded advertising for the current page (intended for
+            this top-level origin) and embedded content and advertising that
+            is transcluded from some other document origin.<br />
             <b>Proposal</b>: For this version of the specification, we don't
             address this corner case.
           </p>
@@ -2156,9 +2159,9 @@
           even when <code>navigator.doNotTrack</code> is null. Scripts SHOULD
           test for the existence of
           <code>storeSiteSpecificTrackingException</code> before calling
-          the method. If an exception is granted in this context and the
+          the method. If an exception is granted and the
           user agent stores that preference, a user agent may send a DNT:0
-          header even if a tracking preference isn't expressed for other
+          header field even if a tracking preference isn't expressed for other
           requests. Persisted preferences MAY also affect which header is
           transmitted if a user later chooses to express a tracking
           preference.

Received on Saturday, 22 February 2014 04:56:35 UTC