Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20]

On Aug 18, 2012, at 6:43 PM, Nicholas Doty wrote:

> (There's also the question of whether permitted use qualifiers would be possible in the format of the response header. I believe the consensus in Bellevue which we're currently reviewing is that we would make permitted use qualifiers optional for the tracking status resource and so we wouldn't necessarily need to change the format of the response header.)

If someone wants that, they will have to open a new issue with
the exact text to be placed in the document.  Most of the text
can be found below.

....Roy
 
% cvs diff -r1.138 -r1.139 tracking-dnt.html
Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.138
retrieving revision 1.139
diff -u -r1.138 -r1.139
--- tracking-dnt.html	7 Aug 2012 01:11:24 -0000	1.138
+++ tracking-dnt.html	7 Aug 2012 01:27:25 -0000	1.139
@@ -990,73 +990,6 @@
           </p>
         </section>
 
-        <section id='status-response-value'>
-          <h3>Qualifier Value</h3>
-
-          <p>
-            When present, the tracking status qualifier member's value
-            consists of a string of characters indicating what permitted
-            uses for tracking are being used.
-            Multiple qualifiers can be provided.
-          </p>
-          <table class="simple" width="80%" align="center">
-            <tr><th>qualifier</th>
-                <th>meaning</th>
-            </tr>
-            <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>
-            </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>
-            </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>
-            </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>
-            </tr>
-            <tr><td align="middle">r</td>
-                <td>Referrals: Tracking is limited to collecting referral
-                  information and the data collected is minimized
-                  accordingly.<td>
-            </tr>
-          </table>
-          <p>
-            Qualifiers that indicate limitations on tracking correspond to
-            the specific permitted uses in [[!TRACKING-COMPLIANCE]]. An
-            origin server indicating one or more of those permitted uses
-            also indicates that it conforms to the requirements associated
-            with those permitted uses. Multiple limitation qualifiers mean
-            that multiple permitted uses of tracking might be present and
-            that each such use conforms to the associated requirements.
-            All limitation qualifiers imply some form of tracking might
-            be used and thus MUST NOT be provided with a tracking status
-            value of <code>N</code> (not tracking).
-          </p>
-          <p>
-            Future extensions to this protocol might define additional
-            characters as qualifiers from the
-            <code><a>ext-qualifier</a></code> set (consisting of the
-            remaining unused lowercase letters, dot, dash, and underscore).
-            Recipients SHOULD ignore extension qualifiers that they do not
-            understand.
-          </p>
-    	    <p class="issue"><a href="http://www.w3.org/2011/tracking-protection/track/issues/136">ISSUE-136</a>: Resolve dependencies of the TPE on the compliance specification.<br />
-            The list of qualifiers is intended to correspond to constraints
-            and permitted uses identified by [[!TRACKING-COMPLIANCE]], and at some point 
-            might perhaps even move to that document in the sections defining the 
-            permitted uses. The above list will be updated accordingly.
-          </p> 
-        </section>
-
         <section id='status-caching'>
           <h3>Caching</h3>
 
@@ -1121,7 +1054,6 @@
           <pre class="abnf">
 <dfn>status-object</dfn> = begin-object member-list end-object
 <dfn>member-list</dfn>   = tracking        ns tracking-v
-                [ vs uses       ns uses-v       ]
                 [ vs same-party ns same-party-v ]
                 [ vs partners   ns partners-v   ]
                 [ vs audit      ns audit-v      ]
@@ -1130,18 +1062,6 @@
                 *( vs extension )
 
 <dfn>tracking</dfn>      = %x22 "tracking" %x22
-<dfn>uses</dfn>          = %x22 "uses" %x22
-<dfn>uses-v</dfn>        = %x22 *<a>qualifier</a> %x22
-
-<dfn>qualifier</dfn>     = %x61  ; "a" — audit
-              / %x63  ; "c" — ad frequency capping
-              / %x66  ; "f" — fraud prevention
-              / %x6C  ; "l" — local law, rule, or regulation
-              / %x72  ; "r" — referrals
-              / ext-qualifier
-
-<dfn>ext-qualifier</dfn> = %x2D-2E / %x30-39 / %x5F / %x62 
-              / %x64-65 / %x67-6B / %x6D-71 / %x73-7A
 
 <dfn>same-party</dfn>    = %x22 "same-party" %x22
 <dfn>same-party-v</dfn>  = array-of-strings

Received on Sunday, 19 August 2012 03:43:35 UTC