Edit ISSUE-217: Terminology for user action, interaction, and network interaction

Nickname:

Title:

State:

Product:

Raised By:

Description:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. ISSUE-217, ISSUE-228: Network Transaction definition --- Decision on Call for Objections (from jbrookman@cdt.org on 2014-02-05) (from jbrookman@cdt.org on 2014-02-05)
  2. Re: Agenda for January 29, 2014, ISSUE-25 (from jbrookman@cdt.org on 2014-01-29) (from jbrookman@cdt.org on 2014-01-29)
  3. Re: Agenda for January 29, 2014, ISSUE-25 (from jbrookman@cdt.org on 2014-01-29) (from jbrookman@cdt.org on 2014-01-29)
  4. Re: Agenda for January 29, 2014 (from rob@blaeu.com on 2014-01-29) (from rob@blaeu.com on 2014-01-29)
  5. Re: Agenda for January 29, 2014 (from kathy@esomar.org on 2014-01-29) (from kathy@esomar.org on 2014-01-29)
  6. Re: Agenda for January 29, 2014 (from rob@blaeu.com on 2014-01-29) (from rob@blaeu.com on 2014-01-29)
  7. Re: Agenda for January 29, 2014 (from sid@mozilla.com on 2014-01-28) (from sid@mozilla.com on 2014-01-28)
  8. Re: Agenda for January 29, 2014 (from ninja@w3.org on 2014-01-28) (from ninja@w3.org on 2014-01-28)
  9. Agenda for January 29, 2014 (from ninja@w3.org on 2014-01-28) (from ninja@w3.org on 2014-01-28)
  10. Re: [Call for objections] Network interaction (from ninja@w3.org on 2013-12-03) (from ninja@w3.org on 2013-12-03)
  11. Re: [Call for objections] Network interaction (from jack@networkadvertising.org on 2013-12-03) (from jack@networkadvertising.org on 2013-12-03)
  12. RE: [Call for objections] Network interaction (from bs3131@att.com on 2013-12-03) (from bs3131@att.com on 2013-12-03)
  13. [Call for objections] Network interaction (from npdoty@w3.org on 2013-12-02) (from npdoty@w3.org on 2013-12-02)
  14. RE: Revise network interaction definition issue-217 issue-228 (from michael.oneill@baycloud.com on 2013-11-25) (from michael.oneill@baycloud.com on 2013-11-25)
  15. Re: Revise network interaction definition issue-217 issue-228 (from rob@blaeu.com on 2013-11-25) (from rob@blaeu.com on 2013-11-25)
  16. Revise network interaction definition issue-217 issue-228 (from npdoty@w3.org on 2013-11-24) (from npdoty@w3.org on 2013-11-24)
  17. tracking-ISSUE-217: Terminology for user action, interaction, and network interaction [Compliance Current] (from sysbot+tracker@w3.org on 2013-10-02) (from sysbot+tracker@w3.org on 2013-10-02)

Related notes:

Existing text:

2.3 Network Transaction

"A network interaction is the set of HTTP requests and responses, or any other sequence of logically related network traffic caused by a user visit to a single web page or similar single action. Page re-loads, navigation, and refreshing of content cause a new network interaction to commence."

1) Section header does not match the defined term. The defined term does not make any sense (a network interaction is any message). The second sentence needs to be prefixed with "For example, ..."; and "Page re-load" is a subset of "refreshing of content".

2) If we want to make requirements on any network interaction, then we should make them on any sent message, or use "network interaction" exclusively for single request/response pairs.

If we want to make requirements on a set of network interactions that result from a single user action, then we should come up with a term for that (i.e., "user action").

If we want to differentiate between a browser's initial resource request (initiated by user action) and the sequence of automated redirects and embedded sub-requests that follow as a direct result of how the browser is instructed or configured to process the results of those interactions, then we should come up with specific terms for each of those things. Note that those interactions are often caused by configuration outside the referring site's control, such as how the browser is implemented, what plug-ins have been installed, what proxies are defined, what accessibility options have been enabled, and so on; so, we might need to differentiate between sub-requests caused by the user (i.e., "configured requests") and sub-requests caused by content received as the result of an interaction that instructs the user agent (i.e., "embedded requests").

Roy Fielding, 2 Oct 2013, 09:29:21

[rigo]: Postponed until 20 Nov while waiting for a definition from Roy

6 Nov 2013, 18:10:47

[rigo]: Use Jacks wiki page for issue-228 to consolidate definitions

6 Nov 2013, 18:19:57

Change Proposal wiki: http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Revise_network_interaction_definition

Justin Brookman, 13 Nov 2013, 23:11:38

This text was determined as the least objectionable definition:
http://lists.w3.org/Archives/Public/public-tracking/2014Jan/att-0117/CfO_Collect_Retain_Use_FINAL.doc
“A party collects data received in a network interaction if that data remains within the party’s control after the network interaction is complete.
A party uses data if the party processes the data for any purpose other than storage or merely forwarding it to another party.
A party shares data if it transfers or provides a copy of data to any other party.
A party facilitates any other party’s collection of data if it enables such party to collect data and engage in tracking.”

Ninja Marnau, 11 Mar 2014, 20:52:13

Text from CfO decision added to TPE in r.1.243

Roy Fielding, 13 Mar 2014, 07:31:31

As we are approaching Last Call with the TPE spec

Ninja Marnau, 9 Apr 2014, 15:22:41


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $