- From: Roy Fielding via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 14 Aug 2012 00:51:57 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv473
Modified Files:
tracking-dnt.html
Log Message:
change the name of partners array to third-party so that it closely matches its purpose
Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.148
retrieving revision 1.149
diff -u -d -r1.148 -r1.149
--- tracking-dnt.html 14 Aug 2012 00:07:17 -0000 1.148
+++ tracking-dnt.html 14 Aug 2012 00:51:55 -0000 1.149
@@ -580,7 +580,7 @@
</tr>
<tr valign="top"><td align="middle"><dfn>1</dfn></td>
<td><strong>First party</strong>: The designated resource is
- designed for use within a first party context and conforms to
+ designed for use within a first-party context and conforms to
the requirements on a first party. If the designated resource
is operated by an outsourced service provider, the service
provider claims that it conforms to the requirements on a
@@ -588,12 +588,12 @@
</tr>
<tr valign="top"><td align="middle"><dfn>3</dfn></td>
<td><strong>Third party</strong>: The designated resource is
- designed for use within a third party context and conforms to
+ designed for use within a third-party context and conforms to
the requirements on a third party.</td>
</tr>
<tr valign="top"><td align="middle"><dfn>X</dfn></td>
<td><strong>Dynamic</strong>: The designated resource is
- designed for use in both first and third party contexts and
+ designed for use in both first and third-party contexts and
dynamically adjusts tracking status accordingly.
If <code>X</code> is present in the site-wide tracking status,
more information MUST be provided via the <a>Tk</a> response
@@ -634,11 +634,11 @@
designed only for first-party conformance, then either the context
has been misunderstood (both are actually the same party) or the
resource has been referenced incorrectly. For the request-specific
- tracking status resource, an indication of first or third party
- status value describes how the resource conformed to that specific
- request, and thus indicates both the nature of the request (as
- viewed by the origin server) and the applicable set of requirements
- to which the origin server claims to conform for that request.
+ tracking status resource, an indication of first or third party as
+ the status value describes how the resource conformed to that
+ specific request, and thus indicates both the nature of the request
+ (as viewed by the origin server) and the applicable set of
+ requirements to which the origin server claims to conform.
</p>
<p>
The tracking status value is case sensitive, as defined formally
@@ -854,7 +854,7 @@
"example_vids.net",
"example_stats.com"
],
- "partners": [
+ "third-party": [
"api.example.net"
],
"audit": [
@@ -872,12 +872,12 @@
<pre class="abnf">
<dfn>status-object</dfn> = begin-object member-list end-object
-<dfn>member-list</dfn> = tracking ns tracking-v
- [ vs same-party ns same-party-v ]
- [ vs partners ns partners-v ]
- [ vs audit ns audit-v ]
- [ vs policy ns policy-v ]
- [ vs control ns control-v ]
+<dfn>member-list</dfn> = tracking ns tracking-v
+ [ vs same-party ns same-party-v ]
+ [ vs third-party ns third-party-v ]
+ [ vs audit ns audit-v ]
+ [ vs policy ns policy-v ]
+ [ vs control ns control-v ]
*( vs extension )
</pre>
<p>
@@ -909,15 +909,15 @@
<dfn>same-party-v</dfn> = array-of-strings
</pre>
<p>
- An OPTIONAL member named <code><a>partners</a></code> MAY be
+ An OPTIONAL member named <code><a>third-party</a></code> MAY be
provided with an array value containing a list of domain names
for third-party services that might be invoked while using the
designated resource but do not share the same data controller as
the designated resource.
</p>
<pre class="abnf">
-<dfn>partners</dfn> = %x22 "partners" %x22
-<dfn>partners-v</dfn> = array-of-strings
+<dfn>third-party</dfn> = %x22 "third-party" %x22
+<dfn>third-party-v</dfn> = array-of-strings
</pre>
<p>
An OPTIONAL member named <code><a>audit</a></code> MAY be
@@ -1020,8 +1020,9 @@
link to a human-readable policy.
</p>
<p class="issue" data-number="61" title="A site could publish a list of the other domains that are associated with them">
- <b>[PENDING REVIEW]</b> The same-party and partners members provide
- a means to list first-party and third-party domains, respectively.
+ <b>[PENDING REVIEW]</b> The <a>same-party</a> and <a>third-party</a>
+ members provide a means to list first-party and third-party domains,
+ respectively.
</p>
</section>
@@ -1240,7 +1241,7 @@
<li>Tracking providers should not ever have to second-guess a
user's expressed Do Not Track preference.</li>
<li>The solution should not require cross-domain communication
- between a first party publisher and its third parties.</li>
+ between a first-party publisher and its third parties.</li>
</ul>
<p>
When asking for a site-specific exception, the top-level domain
@@ -1307,7 +1308,7 @@
<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
+ 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.
Received on Tuesday, 14 August 2012 00:51:59 UTC