- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Wed, 26 Mar 2014 03:47:50 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv6154
Modified Files:
tracking-dnt.html
Log Message:
change the name of the edit property to config
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/26 03:34:04 1.248
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/26 03:47:50 1.249
@@ -677,7 +677,7 @@
the tracking preference expressed by this protocol.
An origin server that sends this tracking status value for a
<a>designated resource</a> MUST provide a reference for
- controlling consent within the <code><a>edit</a></code> property of
+ controlling consent within the <code><a>config</a></code> property of
its corresponding tracking status representation
(<a href="#status-representation" class="sectionRef"></a>).
</p>
@@ -697,8 +697,8 @@
<p>
Since this status value does not itself indicate whether a
specific request is tracked, an origin server that sends a
- <code>P</code> tracking status value MUST provide an
- <code><a>edit</a></code> property in the corresponding tracking
+ <code>P</code> tracking status value MUST provide a
+ <code><a>config</a></code> property in the corresponding tracking
status representation that links to a resource for obtaining
consent status.
</p>
@@ -834,7 +834,7 @@
the scope of this specification, that have the effect of asking
for and obtaining prior consent for tracking, or for modifying
prior indications of consent. For example, the tracking status
- resource's status-object defines an <code><a>edit</a></code>
+ resource's status-object defines a <code><a>config</a></code>
property that can refer to such a mechanism. Although such
out-of-band mechanisms are not defined by this specification,
their presence might influence the tracking status object's
@@ -1028,7 +1028,7 @@
[ vs same-party ns same-party-v ]
[ vs audit ns audit-v ]
[ vs policy ns policy-v ]
- [ vs edit ns edit-v ]
+ [ vs config ns config-v ]
*( vs extension )
</pre>
<p>
@@ -1051,7 +1051,7 @@
"http://auditor.example.org/727073"
],
"policy": "/privacy.html#tracking",
- "edit": "http://example.com/your/data"
+ "config": "http://example.com/your/data"
}
</pre>
</section>
@@ -1224,22 +1224,22 @@
</pre>
</section>
- <section id='rep.edit'>
- <h4>Edit Property</h4>
+ <section id='rep.config'>
+ <h4>Config Property</h4>
<p>
An origin server MAY send a property named
- <code>edit</code> with a string value containing a
+ <code>config</code> with a string value containing a
URI reference to a resource for giving the user control over
personal data collected via the designated resource (and possibly
other resources).
If the tracking status value indicates prior consent
- (<code><a>C</a></code>), the origin server MUST send an
- <code>edit</code> property referencing a resource that
+ (<code><a>C</a></code>), the origin server MUST send a
+ <code>config</code> property referencing a resource that
describes how such consent is established and how to revoke that
consent.
</p>
<p>
- An edit resource might include the ability to review
+ A config resource might include the ability to review
past data collected, delete some or all of the data, provide
additional data (if desired), or <q>opt-in</q>, <q>opt-out</q>,
or otherwise modify an out-of-band consent status regarding
@@ -1249,13 +1249,13 @@
beyond the scope of this protocol.
</p>
</p>
- If no <code>edit</code> property is provided, this
+ If no <code>config</code> property is provided, this
information might be obtained via the links provided in
<code><a>controller</a></code> or <code><a>policy</a></code>.
</p>
<pre class="abnf">
-<dfn>edit</dfn> = %x22 "edit" %x22
-<dfn>edit-v</dfn> = string ; URI-reference
+<dfn>config</dfn> = %x22 "config" %x22
+<dfn>config-v</dfn> = string ; URI-reference
</pre>
</section>
Received on Wednesday, 26 March 2014 03:47:52 UTC