- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Wed, 02 Oct 2013 08:37:48 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv9860/drafts
Modified Files:
tracking-dnt.html
Log Message:
user agent, not user-agent, unless we are talking about the User-Agent header field
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2013/10/02 05:38:49 1.223
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2013/10/02 08:37:47 1.224
@@ -280,7 +280,7 @@
designed to add a tracking preference expression,
or make a choice for privacy that then implicitly includes a
tracking preference (e.g., <q>Privacy settings: high</q>).
- The user-agent might ask the user for their preference during startup,
+ The user agent might ask the user for their preference during startup,
perhaps on first use or after an update adds the tracking protection
feature. Likewise, a user might install or configure a proxy to add
the expression to their own outgoing requests.
@@ -432,7 +432,7 @@
extension characters as possible.
</p>
<p class="note">This document does not have any implied or specified
- behavior for the user-agent treatment of cookies when DNT is enabled.
+ behavior for the user agent treatment of cookies when DNT is enabled.
</p>
<p class="note">The HTTP specification [[!HTTP11]] permits multiple headers
with the same field-name only under restricted circumstances which do
@@ -1555,7 +1555,7 @@
assumed – see <a href="#exceptions-no-js" class="sectionRef"></a>.)
</p>
<p>
- The user-agent MAY provide interfaces to the user:
+ The user agent MAY provide interfaces to the user:
<ul>
<li>To indicate that a call to store an exception has just been made;
<li>To allow the user to confirm a user-granted exception prior to
@@ -1656,7 +1656,7 @@
</p>
<p>
The calls cause the following steps to occur (subject to user
- confirmation of the exception, if the user-agent asks for it):
+ confirmation of the exception, if the user agent asks for it):
</p>
<ul>
<li>The UA adds to its local database one or
@@ -1697,7 +1697,7 @@
<p>
User-agents MUST handle each API request as a 'unit', granting
and maintaining it in its entirety, or not at all. That means
- that a user-agent MUST NOT indicate to a site that a request for
+ that a user agent MUST NOT indicate to a site that a request for
targets {a, b, c} exists in the database, and later remove only one or
two of {a, b, c} from its logical database of remembered grants.
This assures sites that the set of sites they need for
@@ -1706,7 +1706,7 @@
</p>
<div class="note">
<p>
- It is left up to individual user-agent implementations how to
+ It is left up to individual user agent implementations how to
determine and how and whether to store users' tracking
preferences.
</p>
@@ -1715,7 +1715,7 @@
their names might mean little to the user. The user might, for
example, be told that there is a stored exception for a specific set
of sites on such-and-such top-level origin, rather than listing them
- by name; or the user-agent may decide to store, and show to the user,
+ by name; or the user agent may decide to store, and show to the user,
a site-wide exception, effectively ignoring the list of
domain names, if supplied.
</p>
@@ -1792,7 +1792,7 @@
</p>
<p>
If the list <code>arrayOfDomainStrings</code> is supplied, the
- user-agent MAY choose to store a site-wide
+ user agent MAY choose to store a site-wide
exception. If it does so it MUST indicate
this in the return value.
</p>
@@ -1865,7 +1865,7 @@
<p class="note">
The prior version of this call was asynchronous with a call-back; the change
to require the site to determine the user's wishes, rather than the UA,
- enabled this to become synchronous. This is simpler; the user-agent may
+ enabled this to become synchronous. This is simpler; the user agent may
still ask for the user's approval. Sites wishing to know whether an
exception stands, or the DNT header that they would receive,
should call the appropriate enquiry API.
@@ -1945,7 +1945,7 @@
</p>
<p>
If the list <code>arrayOfDomainStrings</code> is supplied, and the
- user-agent stores only site-wide exceptions, then the user-agent
+ user agent stores only site-wide exceptions, then the user agent
MUST match by confirming a site-wide exception.
</p>
<p>
@@ -1956,26 +1956,26 @@
the duplet in the logical model.
</p>
<p>
- If the user-agent stores explicit lists, and the call includes one, the
+ If the user agent stores explicit lists, and the call includes one, the
database is checked for the existence of all the duplets (one per target):
</p>
<pre>[document-origin, target]</pre>
<p>
- If the user-agent stores only site-wide exceptions or the call did
+ If the user agent stores only site-wide exceptions or the call did
not include an explicit list, the database is checked for the
single duplet:
</p>
<pre>[document-origin, * ]</pre>
<p>
- If the user-agent stores explicit lists, and the call includes one,
+ If the user agent stores explicit lists, and the call includes one,
and the <code>domain</code> argument is provided and is not empty then the
database is checked for the existence of all the duplets (one per target):
</p>
<pre>[*.domain, target]</pre>
<p>
- If the user-agent stores only site-wide exceptions or the call did
+ If the user agent stores only site-wide exceptions or the call did
not include an explicit list, and the <code>domain</code> argument is
provided and is not empty then the database is checked for the single
duplet:
@@ -2080,7 +2080,7 @@
first party will not necessarily know in advance whether a known third party
will use some other third parties.</p>
- <p>If a user-agent sends a tracking exception to a given combination of origin
+ <p>If a user agent sends a tracking exception to a given combination of origin
server and a named third party, the user agent will send DNT:0 to that named
third party. By receiving the DNT:0 header, the named third party acquires
the permission to track the user agent and collect the data and process it
@@ -2097,7 +2097,7 @@
The tracking permission request triggered
by the origin server is thus granted to the named third party and its
sub-services. This is even true for sub-services that would normally receive a
- DNT:1 web-wide preference from the user-agent if the user agent
+ DNT:1 web-wide preference from the user agent if the user agent
interacted with this service directly.</p>
<p>For advertisement networks this typically would mean that the collection and
@@ -2150,7 +2150,7 @@
the exception until the user approves. Some agents might provide a
user-interface to see and edit the database of recorded exception grants.
The API parameters siteName, explanationString, and detailURI are
- provided so that the user-agent may use them in their user interface.
+ provided so that the user agent may use them in their user interface.
</p>
<p>
A user agent that chooses to highlight when tracking exceptions have been
@@ -2168,7 +2168,7 @@
</p>
<p>
- In some user-agent implementations, decisions to grant exceptions
+ In some user agent implementations, decisions to grant exceptions
may have been made in the past (and since forgotten) or may have
been made by other users of the device. Thus, exceptions may not
always represent the current preferences of the user. Some user
@@ -2227,7 +2227,7 @@
test for the existence of
<code>storeSiteSpecificTrackingException</code> before calling
the method. If an exception is granted in this context and the
- user-agent stores that preference, a user agent may send a DNT:0
+ user agent stores that preference, a user agent may send a DNT:0
header even if a tracking preference isn't expressed for other
requests. Persisted preferences MAY also affect which header is
transmitted if a user later chooses to express a tracking
@@ -2254,7 +2254,7 @@
<p>The 'Store' calls do not have a return value, and return immediately.
If there is a problem with the calling parameters, then a Javascript
exception will be raised.
- In addition, it may be that the user-agent does not immediately store
+ In addition, it may be that the user agent does not immediately store
the exception, possibly because it is allowing the user to confirm.
Even though the site has acquired the user's informed consent before
calling the 'Store' API, it is possible that the user will change
@@ -2267,7 +2267,7 @@
</p>
<p>Sites can call the 'Confirm' APIs to enquire whether a specific
- exception has been granted and stands in the user-agent. This is the call
+ exception has been granted and stands in the user agent. This is the call
to make to determine whether the exception exists, and hence to control
access to the function or operation; if it fails (the exception has been
deleted, or not yet granted), then the user is ideally again offered
Received on Wednesday, 2 October 2013 08:37:49 UTC