Edit ISSUE-59: Should the first party be informed about whether the user has sent a DNT header to third parties on their site?

Nickname:

Title:

State:

Product:

Raised By:

Description:

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

Related emails:

  1. Re: Agenda for July 18, 2012 DNT WG Call on TPE (from fielding@gbiv.com on 2012-07-18) (from fielding@gbiv.com on 2012-07-18)
  2. RE: ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from wileys@yahoo-inc.com on 2012-06-24) (from wileys@yahoo-inc.com on 2012-06-24)
  3. Re: ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from derhoermi@gmx.net on 2012-06-24) (from derhoermi@gmx.net on 2012-06-24)
  4. Re: ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from derhoermi@gmx.net on 2012-06-24) (from derhoermi@gmx.net on 2012-06-24)
  5. ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from mts-std@schunter.org on 2012-06-24) (from mts-std@schunter.org on 2012-06-24)
  6. Re: ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from peter.cranstone@gmail.com on 2012-06-23) (from peter.cranstone@gmail.com on 2012-06-23)
  7. Re: ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from peter.cranstone@gmail.com on 2012-06-23) (from peter.cranstone@gmail.com on 2012-06-23)
  8. Re: ISSUE-59: Should the first party be informed about the DNT values sent to third parties (from peter.cranstone@gmail.com on 2012-06-23) (from peter.cranstone@gmail.com on 2012-06-23)
  9. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from npdoty@w3.org on 2012-03-23) (from npdoty@w3.org on 2012-03-23)
  10. RE: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from kevsmith@adobe.com on 2012-03-23) (from kevsmith@adobe.com on 2012-03-23)
  11. RE: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from kevsmith@adobe.com on 2012-03-23) (from kevsmith@adobe.com on 2012-03-23)
  12. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from jmayer@stanford.edu on 2012-03-17) (from jmayer@stanford.edu on 2012-03-17)
  13. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from jmayer@stanford.edu on 2012-03-17) (from jmayer@stanford.edu on 2012-03-17)
  14. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from npdoty@w3.org on 2012-03-17) (from npdoty@w3.org on 2012-03-17)
  15. RE: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from kevsmith@adobe.com on 2012-03-15) (from kevsmith@adobe.com on 2012-03-15)
  16. Re: ISSUE-111, ad exchanges, web wide exception (from rigo@w3.org on 2012-03-15) (from rigo@w3.org on 2012-03-15)
  17. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from sid@mozilla.com on 2012-03-14) (from sid@mozilla.com on 2012-03-14)
  18. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from jmayer@stanford.edu on 2012-03-14) (from jmayer@stanford.edu on 2012-03-14)
  19. Re: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from sid@mozilla.com on 2012-03-14) (from sid@mozilla.com on 2012-03-14)
  20. RE: A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from kevsmith@adobe.com on 2012-03-14) (from kevsmith@adobe.com on 2012-03-14)
  21. A First-Party List API for Site-Specific Exceptions (ISSUE-59, ISSUE-109, ISSUE-111, ISSUE-113, ISSUE-114) (from jmayer@stanford.edu on 2012-03-14) (from jmayer@stanford.edu on 2012-03-14)
  22. Re: [ISSUE-5] What is the definition of tracking? (from jeff@democraticmedia.org on 2011-12-10) (from jeff@democraticmedia.org on 2011-12-10)
  23. Re: Summary of Options for 1P Learning of 3P DNT Status (from ifette@google.com on 2011-10-30) (from ifette@google.com on 2011-10-30)
  24. Re: Summary of compliance issues raised (from tom@mozilla.com on 2011-10-27) (from tom@mozilla.com on 2011-10-27)
  25. Summary of compliance issues raised (from aleecia@aleecia.com on 2011-10-26) (from aleecia@aleecia.com on 2011-10-26)
  26. Re: Propose to drop from the strawman: ISSUE-93 (from aleecia@aleecia.com on 2011-10-26) (from aleecia@aleecia.com on 2011-10-26)
  27. Re: Propose to drop from the strawman: ISSUE-93 (from npdoty@w3.org on 2011-10-26) (from npdoty@w3.org on 2011-10-26)
  28. Summary of Options for 1P Learning of 3P DNT Status (from jmayer@stanford.edu on 2011-10-26) (from jmayer@stanford.edu on 2011-10-26)
  29. Summary of progress on Issue 59 (from aleecia@aleecia.com on 2011-10-19) (from aleecia@aleecia.com on 2011-10-19)
  30. agenda for wednesday call (from aleecia@aleecia.com on 2011-10-18) (from aleecia@aleecia.com on 2011-10-18)
  31. ISSUE-59: Should the first party be informed about whether the user has sent a DNT header to third parties on their site? (from sysbot+tracker@w3.org on 2011-09-22) (from sysbot+tracker@w3.org on 2011-09-22)

Related notes:

Call 2012-04-18: We agreed that we no longer need to consider the actual headers but instead will focus on user-granted exceptions.
I.e., ISSUE-59 will be superseded by ISSUE-111 from now on.

Matthias Schunter, 18 Apr 2012, 17:23:43


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 $