- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Tue, 01 Apr 2014 07:00:58 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv11024
Modified Files:
tracking-dnt.html
Log Message:
(editorial) target requirements on what must obey them (user agent. proxy, server, origin server) like new HTTP standard
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/29 05:29:09 1.255
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/04/01 07:00:58 1.256
@@ -864,28 +864,31 @@
<section id='site-wide-status-resource'>
<h4>Site-wide Tracking Status</h4>
<p>
- An origin server MUST provide a <dfn>site-wide tracking status
- resource</dfn> at the well-known identifier [[RFC5785]]
+ A <dfn>site-wide tracking status resource</dfn> provides
+ information about the potential tracking behavior of resources
+ located at that origin server. A site-wide tracking status
+ resource has the well-known identifier
</p>
<pre>/.well-known/dnt/</pre>
<p>
- (relative to the URI of that origin server) for obtaining
- information about the potential tracking behavior of resources
- provided by that origin server. A tracking status resource can be
- used for verification of DNT support, as described in
- <a href="#using-tracking-status" class="sectionRef"></a>.
+ relative to the origin server's URI [[RFC5785]].
</p>
<p>
- A valid retrieval request (e.g., a <code>GET</code> in HTTP)
- on the well-known URI MUST result in either a successful response
- containing a machine-readable representation of the site-wide
- tracking status, as defined below, or a sequence of redirects that
- leads to such a representation.
- A user agent MAY consider failure to provide access to such a
- representation equivalent to the origin server not implementing
- this protocol. The representation can be cached, as described
+ An origin server that receives a valid <code>GET</code> request
+ targeting its site-wide tracking status resource MUST send either
+ a successful response containing a machine-readable representation
+ of the site-wide tracking status, as defined below, or a sequence
+ of redirects that leads to such a representation. Failure to
+ provide access to such a representation implies that the target
+ origin server does not implement this protocol.
+ The representation can be cached, as described
in <a href="#status-caching" class="sectionRef"></a>.
</p>
+ <p>
+ See <a href="#using-tracking-status" class="sectionRef"></a> for
+ examples of how tracking status resources can be used to discover
+ support for this protocol.
+ </p>
</section>
<section id='request-specific-status-resource'>
@@ -902,7 +905,7 @@
status resource applies to the current request.
</p>
<p>
- The <dfn>tracking status resource space</dfn> is defined by the
+ A <dfn>tracking status resource space</dfn> is defined by the
following URI Template [[URI-TEMPLATE]]:
</p>
<pre>/.well-known/dnt/{+status-id}</pre>
@@ -1136,8 +1139,8 @@
is implying that its domain owner is the sole data controller;
information about the data controller ought to be found on the
designated resource's site root page, or by way of a clearly
- indicated link from that page (i.e., no controller property is
- considered equivalent to: <code>"controller":["/"]</code>).
+ indicated link from that page (i.e., an absent controller property
+ is equivalent to: <code>"controller":["/"]</code>).
</p>
<p>
If the <a>designated resource</a> has joint data controllers
Received on Tuesday, 1 April 2014 07:01:00 UTC