ISSUE-113: Should there be a JavaScript API to prompt for a Web-wide exception?

Should there be a JavaScript API to prompt for a Web-wide exception?

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Nick Doty
Opened on:
2012-01-06
Description:
Is a JavaScript prompt for cross-Web tracking useful or necessary?

If so, it might look something like this:
boolean requestTrackingException(string trackingDomain);

This might be convenient. On the other hand, maybe user agents should just handle this on their own. Presumably a user/user-agent wouldn't promise to a tracker that it would grant it a permanent or Web-wide exception.
Related Actions Items:
Related emails:
  1. Re: Agenda for 28 November 2012 call - V01 (from mts-std@schunter.org on 2013-02-13)
  2. Agenda for 09 Jan 2013 TPE call - V01 (from mts-std@schunter.org on 2013-01-08)
  3. Re: Agenda for 06 December 2012 TPE call - V01 (from david@networkadvertising.org on 2012-12-04)
  4. Agenda for 06 December 2012 TPE call - V01 (from mts-std@schunter.org on 2012-12-04)
  5. RE: ISSUE-112 - was Agenda (from michael.oneill@baycloud.com on 2012-11-27)
  6. Re: Agenda for 28 November 2012 call - V02 (from david@networkadvertising.org on 2012-11-27)
  7. ISSUE-112 - was Agenda (from rigo@w3.org on 2012-11-27)
  8. Agenda for 28 November 2012 call - V02 (from mts-std@schunter.org on 2012-11-27)
  9. Re: Agenda for 28 November 2012 call - V01 (from david@networkadvertising.org on 2012-11-25)
  10. Agenda for 28 November 2012 call - V01 (from mts-std@schunter.org on 2012-11-25)
  11. Agenda for August 15, 2012 call (from mts-std@schunter.org on 2012-08-13)
  12. agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
  13. agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
  14. Issue cleanup and sync for TPE document (from mts-std@schunter.org on 2012-08-03)
  15. Re: Agenda for July 18, 2012 DNT WG Call on TPE (from fielding@gbiv.com on 2012-07-18)
  16. agenda: 18 April 2012 call (from aleecia@aleecia.com on 2012-04-18)
  17. Notes from the Exception Working Group [ISSUE-113, ISSUE-128, ISSUE-129, ISSUE-130] (from mts-std@schunter.org on 2012-04-12)
  18. Issues mentioned in the TPE document, or non-closed in the database and applying to TPE (from singer@apple.com on 2012-04-10)
  19. Re: ISSUE-130: Web-wide exceptions - iare there objections to permitting those? (from npdoty@w3.org on 2012-04-05)
  20. TPE: Input for our discussions in DC (from mts-std@schunter.org on 2012-04-04)
  21. Re: Issue Maintenance (from jmayer@stanford.edu on 2012-03-29)
  22. Issue Maintenance (from mts-std@schunter.org on 2012-03-28)
  23. 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)
  24. 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)
  25. 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)
  26. 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)
  27. 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)
  28. 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)
  29. 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)
  30. 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)
  31. 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)
  32. 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)
  33. 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)
  34. 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)
  35. Re: ISSUE-111 - Exceptions are broken (from npdoty@w3.org on 2012-03-08)
  36. RE: set of exceptions (from wileys@yahoo-inc.com on 2012-03-06)
  37. Re: Work ahead; volunteers? (from john@consumerwatchdog.org on 2012-03-06)
  38. How can a server understand the site-specific exceptions that are stored in a user agent (was: Work ahead; volunteers?) (from mts@zurich.ibm.com on 2012-03-06)
  39. TPE: Work ahead; volunteers? (from mts@zurich.ibm.com on 2012-03-06)
  40. JS Exception API (from tom@mozilla.com on 2012-02-29)
  41. Agenda for 2012-Feb-22 call (from mts@zurich.ibm.com on 2012-02-21)
  42. Re: Housekeeping from today's call (from aleecia@aleecia.com on 2012-02-08)
  43. Re: Housekeeping from today's call (from achapell@chapellassociates.com on 2012-02-08)
  44. Housekeeping from today's call (from aleecia@aleecia.com on 2012-02-08)
  45. diff of TPE editing since the FPWD (from fielding@gbiv.com on 2012-01-10)
  46. tracking-ISSUE-113: Should there be a JavaScript API to prompt for a Web-wide exception? [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-01-06)

Related notes:

We agreed that there should be such an API. This issue is now continued as ISSUE-130.

Matthias Schunter, 1 May 2012, 15:28:35

In Bellevue we agreed that a web-wide API should be present. Is included in the spec as part of the exceptions API (currently in Section 6)

Matthias Schunter, 3 Aug 2012, 16:22:40

Display change log ATOM feed


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.325 2014-09-10 21:42:02 ted Exp $