- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Mon, 31 Oct 2011 11:17:21 -0700
- To: Tom Lowenthal <tom@mozilla.com>
- Cc: public-tracking@w3.org
On Oct 31, 2011, at 9:43 AM, Tom Lowenthal wrote: > Pursuant to my F2F comment. The current first paragraph of section 2.3 > reads: > >> HTTP [HTTP11] uses the term user agent to refer to any of the various >> client programs capable of initiating HTTP requests, including >> browsers, spiders (web-based robots), command-line tools, native >> applications, and mobile apps. Although the protocol defined by this >> specification is applicable to all forms of user agent, the >> compliance requirements are specifically concerned with the privacy >> expectations of a human user and the tracking of their browsing >> history over time. Hence, user agents that do not have some form of >> "browsing" nature or do not communicate with more than one site are >> not expected to comply with this protocol. > > This leaves the status of mobile apps somewhat unclear. I propose the > following text instead: > > >> HTTP [HTTP11] uses the term user agent to refer to any of the various >> client programs capable of initiating HTTP requests, including >> browsers, spiders (web-based robots), command-line tools, native >> applications, and mobile apps. Although the protocol defined by this >> specification is potentially applicable to all forms of user agent, >> the compliance requirements are specifically concerned with the >> privacy expectations of a human user and the tracking of their >> browsing history over time. >> >> There exist user agents which do not have a "browsing" nature, such >> as mobile apps which communicate with one service exclusively. These >> non-browsing user-agents are not the target for this standard, though >> there is no reason why they could not implement it. +1 (works for me) ....Roy
Received on Monday, 31 October 2011 18:17:46 UTC