- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Wed, 15 Jan 2014 01:49:23 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv15581
Modified Files:
tracking-dnt.html
Log Message:
(editorial) s/member/property/g for JSON
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/01/15 01:40:47 1.231
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/01/15 01:49:23 1.232
@@ -573,7 +573,7 @@
service providers on any given request. If the designated resource
is operated by a service provider acting as a first party, then
the responsible first party is identified by the
- <code><a>controller</a></code> member or the owner of the origin
+ <code><a>controller</a></code> property or the owner of the origin
server domain. This satisfies the use case of distinguishing
between a service provider acting for some other site and the same
service provider acting on one of its own sites.
@@ -656,7 +656,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> member of
+ controlling consent within the <code><a>edit</a></code> property of
its corresponding tracking status representation
(<a href="#status-representation" class="sectionRef"></a>).
</p>
@@ -680,7 +680,7 @@
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> member in the corresponding tracking
+ <code><a>edit</a></code> property in the corresponding tracking
status representation that links to a resource for obtaining
consent status.
</p>
@@ -828,7 +828,7 @@
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>
- member that can refer to such a mechanism. Although such
+ 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
response value.
@@ -1001,20 +1001,20 @@
An origin server MUST provide a representation of each tracking
status resource in a JSON format [[!RFC4627]] that conforms to
the ABNF for <code><a>status-object</a></code> (except that the
- members within each member-list MAY be provided in any order).
+ properties within a property-list MAY be provided in any order).
</p>
<section id='rep.status-object'>
<h4>Status Object</h4>
<p>
A tracking status representation consists of a single
- <code>status-object</code> containing members that describe
+ <code>status-object</code> containing properties that describe
the tracking status applicable to the <a>designated resource</a>.
</p>
<pre class="abnf">
-<dfn>status-object</dfn> = begin-object member-list end-object
+<dfn>status-object</dfn> = begin-object property-list end-object
-<dfn>member-list</dfn> = tracking-p ns tracking-v
+<dfn>property-list</dfn> = tracking-p ns tracking-v
[ vs compliance ns compliance-v ]
[ vs qualifiers ns qualifiers-v ]
[ vs controller ns controller-v ]
@@ -1052,7 +1052,7 @@
<section id='rep.tracking'>
<h4>Tracking Property</h4>
<p>
- A <code><a>status-object</a></code> always has a member named
+ A <code><a>status-object</a></code> always has a property named
<code>tracking</code> with a string value containing
the tracking status value
(<a href="#tracking-status-value" class="sectionRef"></a>)
@@ -1075,7 +1075,7 @@
<section id='rep.tracking' class="option">
<h4>Compliance Property</h4>
<p>
- An origin server MAY send a member named
+ An origin server MAY send a property named
<code>compliance</code> with an array value containing
a list of URI references that identify specific regimes to which
the origin server claims to comply for the designated resource.
@@ -1097,7 +1097,7 @@
<h4>Qualifiers Property</h4>
<p>
An origin server MAY send a
- member named <code>qualifiers</code> with a string value
+ property named <code>qualifiers</code> with a string value
containing a sequence of case sensitive characters corresponding
to explanations or limitations on the extent of tracking.
Multiple qualifiers indicate that multiple explanations or forms
@@ -1115,12 +1115,12 @@
<section id='rep.controller'>
<h4>Controller Property</h4>
<p>
- An origin server MAY send a member named
+ An origin server MAY send a property named
<code>controller</code> with an array value containing
a list of URI references indirectly identifying the party or
set of parties that claims to be the responsible data controller
for personal data collected via the designated resource. An origin
- server MUST send a <code>controller</code> member if the
+ server MUST send a <code>controller</code> property if the
responsible data controller does not own the designated resource's
domain name.
</p>
@@ -1129,14 +1129,14 @@
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 member is
+ indicated link from that page (i.e., no controller property is
considered equivalent to: <code>"controller":["/"]</code>).
</p>
<p>
If the <a>designated resource</a> has joint data controllers
(i.e., multiple parties have independent control over the
collected data), the origin server MUST send a
- <code>controller</code> member that contains a reference
+ <code>controller</code> property that contains a reference
for each data controller.
</p>
<p>
@@ -1160,7 +1160,7 @@
useful for a site to distinguish those domains that are subject to
their own control (i.e., share the same data controller as the
referring site).
- An origin server MAY send a member named
+ An origin server MAY send a property named
<code>same-party</code> with an array value containing a
list of domain names that the origin server claims are the same
party, to the extent they are referenced by the designated
@@ -1197,7 +1197,7 @@
<section id='rep.audit'>
<h4>Audit Property</h4>
<p>
- An origin server MAY send a member named
+ An origin server MAY send a property named
<code>audit</code> with an array value containing a list of
URI references to external audits of the designated resource's
privacy policy and tracking behavior.
@@ -1215,14 +1215,14 @@
<section id='rep.policy'>
<h4>Policy Property</h4>
<p>
- An origin server MAY send a member named
+ An origin server MAY send a property named
<code>policy</code> with a string value containing a
URI reference to a 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
in the machine-readable tracking status representation.
- If no <code>policy</code> member is provided, this
+ If no <code>policy</code> property is provided, this
information might be obtained via the links provided in
<code><a>controller</a></code>.
</p>
@@ -1235,14 +1235,14 @@
<section id='rep.edit'>
<h4>Edit Property</h4>
<p>
- An origin server MAY send a member named
+ An origin server MAY send a property named
<code>edit</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> member referencing a resource that
+ <code>edit</code> property referencing a resource that
describes how such consent is established and how to revoke that
consent.
</p>
@@ -1257,7 +1257,7 @@
beyond the scope of this protocol.
</p>
</p>
- If no <code>edit</code> member is provided, this
+ If no <code>edit</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>
@@ -1271,9 +1271,9 @@
<h4>Extensions</h4>
<p>
An origin server MAY send additional extension
- members in the <code><a>status-object</a></code> to support future
+ properties in the <code><a>status-object</a></code> to support future
enhancements to this protocol. A recipient MUST ignore
- extension members that it does not recognize.
+ extension properties that it does not recognize.
</p>
<pre class="abnf">
<dfn>extension</dfn> = object
@@ -1362,7 +1362,7 @@
non-conformant with this protocol.
</p>
<p>
- The <code><a>status-object</a></code> is supposed to have a member
+ The <code><a>status-object</a></code> is supposed to have a property
named <code>tracking</code> containing the tracking status
value. The meaning of each tracking status value is defined in
<a href="#tracking-status-value" class="sectionRef"></a>.
@@ -1930,7 +1930,7 @@
<code>[ * , *.domain]</code> (based on if <code>domain</code>
is provided and is not null and not empty)
is added to the database of remembered grants.
- The members of the <code>StoreExceptionPropertyBag</code>
+ The properties of the <code>StoreExceptionPropertyBag</code>
dictionary are as described
<a href="#exceptions-javascript-api">above</a> in the
request for site-specific exceptions.
Received on Wednesday, 15 January 2014 01:49:24 UTC