- From: CVS User npdoty <cvsmail@w3.org>
- Date: Mon, 27 Jan 2014 01:55:34 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv31516
Modified Files:
tracking-compliance.html
Log Message:
consistent about referring to network interactions rather than transactions
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/01/16 22:10:51 1.108
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-compliance.html 2014/01/27 01:55:34 1.109
@@ -86,8 +86,8 @@
command-line tools, native applications, and mobile apps [[!HTTP11]].
</p></section>
- <section id="network-transaction">
- <h3>Network Transaction</h3>
+ <section id="network-interaction">
+ <h3>Network Interaction</h3>
<p>
A <dfn>network interaction</dfn> is a single HTTP request and its
corresponding response(s): zero or more interim (1xx) responses and
@@ -224,7 +224,7 @@
<section id="graduated-response">
<h3>Graduated Response</h3>
<p>
- A <dfn>graduated response</dfn> a methodology where the action taken is proportional to the size of the problem or risk that is trying to be mitigated. In the context of this document, the term is used to describe an increase in the collection of data about a user or transaction in response to a specific problem that a party has become aware of, such as an increase in fraudulent activity originating from a particular network or IP address range resulting in increased logging of data relating to transactions from that specific range of IP addresses as opposed to increased logging for all users in general.
+ A <dfn>graduated response</dfn> a methodology where the action taken is proportional to the size of the problem or risk that is trying to be mitigated. In the context of this document, the term is used to describe an increase in the collection of data about a user or interaction in response to a specific problem that a party has become aware of, such as an increase in fraudulent activity originating from a particular network or IP address range resulting in increased logging of data relating to interactions from that specific range of IP addresses as opposed to increased logging for all users in general.
</p>
<p class="note">
Only used in security, below, and may overlap with the explanation
@@ -283,7 +283,7 @@
<p>
The first party MUST NOT share data about this network interaction with
third parties who could not collect the data
- themselves under this recommendation. Data about the transaction MAY be shared with service providers acting on behalf of the first party.
+ themselves under this recommendation. Data about the interaction MAY be shared with service providers acting on behalf of the first party.
</p>
<p>
A first party MAY elect to follow the rules defined here for third parties.
@@ -465,7 +465,7 @@
click fraud) from that IP address range. Similarly, if an attack shared
some other identifiable fingerprint, such as a combination of User Agent
and other protocol information, the party could retain logs on all
- transactions matching that fingerprint until it can be determined that
+ interactions matching that fingerprint until it can be determined that
they are not associated with such an attack or such retention is no
longer necessary to support prosecution.</p>
Received on Monday, 27 January 2014 01:55:35 UTC