ISSUE-149: Compliance section for user agents

Compliance section for user agents

State:
CLOSED
Product:
Compliance Next
Raised by:
Aleecia McDonald
Opened on:
2012-05-30
Description:
We have some related sub-issues we may need to break out, or perhaps we can do this as one. We will talk as a group to see which of the itemized points below are things we wish to take on. I expect we will need to create a new section in the Compliance document specifically about user agents.

First, and a motivating factor underlying other issues, we have the example of the AVG anti-spyware package enabling DNT:1 for new users who purchase their product. As a group, we have discussed the idea that users must be making some choice for privacy -- perhaps via slider, or by downloading MyPrivateWebBrowser, or something -- in order for them to send DNT:1. Reasonable people who were part of those discussions are disagreeing as to whether installing AVG counts as a decision for privacy, or not. This is problematic. Whatever decision we make as a group, we need to (a) be clear about it ourselves so we can (b) write it down clearly for others.

Second, due to multiple addons that support Do Not Track, there could be conflicts. For example, a user could turn off DNT (not unset, actually off, sending DNT:0) in Firefox, yet install Abine's "Do Not Track Plus" addon (which sends DNT:1). More fun, users could have three different addons, each with a different value. Do we have either best practices or requirements for user agents here?

Third, while we have documented DNT as being on / off / unset, do we want to write that as a requirement for user agents? User interface is out of scope by charter, but we could require user agents to offer all three options. Currently we only state all three are possible values (which we do document well.)

Finally, we have issue-143 against the TPE document that is at least somewhat a compliance issue as well, around informed consent and browser choices. This is tied into many of the issues above. We may wish to add a new issue, or move issue-143 to a compliance issue for the time being, or neither.



Partial decision (on tri-part choice):
http://lists.w3.org/Archives/Public/public-tracking/2012Sep/0197.html

Formal objection:
http://lists.w3.org/Archives/Public/public-tracking/2012Oct/0104.html
Related Actions Items:
No related actions
Related emails:
  1. Agenda for May 22 call (from peter@peterswire.net on 2013-05-21)
  2. issue and action cleanup proposals (from npdoty@w3.org on 2013-05-15)
  3. Re: Mapping the "framework" to ISSUEs (from john@consumerwatchdog.org on 2013-05-07)
  4. Mapping the "framework" to ISSUEs (from jmayer@stanford.edu on 2013-05-07)
  5. Re: Batch closing of issues (ISSUE-144, ISSUE-187, ISSUE-190, ISSUE-173, ISSUE-138) [pls Respond by Jan 30] (from jmayer@stanford.edu on 2013-01-24)
  6. ISSUE-163: How in the spec should we ensure user agents don't twist a user preference one way or another? (Text that biases user decisions, 'express' work flows, etc). Related to outcome if ISSUE-149 and http://lists.w3.org/Archives/Public/public-tracking (from sysbot+tracker@w3.org on 2012-09-19)
  7. Working Group Decision on Tri-part choice requirement for user agents (from aleecia@aleecia.com on 2012-09-14)
  8. Call for objections: Tri-part choice requirement for user agents (from aleecia@aleecia.com on 2012-08-15)
  9. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  10. Re: ISSUE-4 and clarity regarding browser defaults (from James.Grimmelmann@nyls.edu on 2012-07-27)
  11. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  12. Re: ISSUE-4 and clarity regarding browser defaults (from david@networkadvertising.org on 2012-07-27)
  13. Re: ISSUE-4 and clarity regarding browser defaults (from david@networkadvertising.org on 2012-07-27)
  14. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  15. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  16. Re: ISSUE-4 and clarity regarding browser defaults (from James.Grimmelmann@nyls.edu on 2012-07-27)
  17. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  18. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  19. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  20. Re: ISSUE-4 and clarity regarding browser defaults (from singer@apple.com on 2012-07-27)
  21. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  22. Re: ISSUE-4 and clarity regarding browser defaults (from Brooks.Dobbs@kbmg.com on 2012-07-27)
  23. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  24. Re: ISSUE-4 and clarity regarding browser defaults (from James.Grimmelmann@nyls.edu on 2012-07-27)
  25. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-26)
  26. Re: ISSUE-4 and clarity regarding browser defaults (from singer@apple.com on 2012-07-26)
  27. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-26)
  28. Re: ISSUE-4 and clarity regarding browser defaults (from john@consumerwatchdog.org on 2012-07-26)
  29. RE: ISSUE-4 and clarity regarding browser defaults (from mike@iab.net on 2012-07-26)
  30. Re: ISSUE-4 and clarity regarding browser defaults (from jeff@democraticmedia.org on 2012-07-26)
  31. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-26)
  32. RE: ISSUE-4 and clarity regarding browser defaults (from mike@iab.net on 2012-07-26)
  33. agenda: 6 June 2012 call (from aleecia@aleecia.com on 2012-06-05)
  34. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-06-03)
  35. Re: ISSUE-4 and clarity regarding browser defaults (from jeff@democraticmedia.org on 2012-06-03)
  36. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-06-03)
  37. Re: ISSUE-4 and clarity regarding browser defaults (from vp@iabeurope.eu on 2012-06-03)
  38. Re: ISSUE-4 and clarity regarding browser defaults (from jeff@democraticmedia.org on 2012-06-03)
  39. Re: ISSUE-4 and clarity regarding browser defaults (from fielding@gbiv.com on 2012-06-02)
  40. Re: tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance] (from rigo@w3.org on 2012-06-01)
  41. Re: tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance] (from fielding@gbiv.com on 2012-05-30)
  42. Re: tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance] (from singer@apple.com on 2012-05-30)
  43. tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance] (from sysbot+tracker@w3.org on 2012-05-30)
  44. agenda: 30 May 2012 call (from aleecia@aleecia.com on 2012-05-29)

Related notes:

Merged during issue cleanup. The parts of this issue not covered by the partial closure noted already are better tracked by:
issue-172 https://www.w3.org/2011/tracking-protection/track/issues/172 How should user agents be required to provide information about DNT?
and
issue-194 https://www.w3.org/2011/tracking-protection/track/issues/194 How should we ensure consent of users for DNT inputs? (user education and user consent)

Nick Doty, 29 May 2013, 01:19:36

Display change log ATOM feed

Chair, 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: 149.html,v 1.1 2019/02/01 09:32:30 vivien Exp $