- From: Roy Fielding via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Oct 2012 08:39:54 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv4952
Modified Files:
tracking-dnt.html
Log Message:
ACTION-322: Clarify "policy" member to refer to "relevant privacy policy",
not necessarily tracking-specific
Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.170
retrieving revision 1.171
diff -u -d -r1.170 -r1.171
--- tracking-dnt.html 29 Sep 2012 08:27:51 -0000 1.170
+++ tracking-dnt.html 17 Oct 2012 08:39:51 -0000 1.171
@@ -943,7 +943,7 @@
"audit": [
"http://auditor.example.org/727073"
],
- "policy": "/tracking.html",
+ "policy": "/privacy.html#tracking",
"control": "http://example.com/your/data"
}
</pre>
@@ -1007,7 +1007,7 @@
<p>
An OPTIONAL member named <code><a>audit</a></code> MAY be
provided with an array value containing a list of URI references
- to external audits of the designated resource's tracking policy
+ to external audits of the designated resource's privacy policy
and tracking behavior in compliance with this protocol.
Preferably, the audit references are to resources that describe
the auditor and the results of that audit; however, if such a
@@ -1021,11 +1021,11 @@
<p>
An OPTIONAL member named <code><a>policy</a></code> MAY be
provided with a string value containing a URI-reference to a
- human-readable document that describes the tracking policy for
- the designated resource.
+ human-readable document that describes the relevant privacy policy
+ for the designated resource.
The content of such a policy document is beyond the
scope of this protocol and only supplemental to what is described
- by this machine-readable tracking status representation.
+ in the machine-readable tracking status representation.
</p>
<pre class="abnf">
<dfn>policy</dfn> = %x22 "policy" %x22
@@ -1139,7 +1139,8 @@
at which the service's tracking behavior might increase. For
example, if the tracking status response is set to expire in seven
days, then the earliest point in time that the service's tracking
- behavior can be increased is seven days after the policy has been
+ behavior can be increased is seven days after the tracking status
+ representation has been
updated to reflect the new behavior, since old copies might
persist in caches until the expiration is triggered. A service's
tracking behavior can be reduced at any time, with or without a
Received on Wednesday, 17 October 2012 08:39:55 UTC