ISSUE-185: There should not be an API for web-wide exceptions

WebWide Not

There should not be an API for web-wide exceptions

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Mike O'Neill
Opened on:
2012-10-28
Description:
We should not have a "silent" web-wide exception API, to accompany the suggested site-wide one.
As there is now no safety check UI for the site-wide API ,or potential for one as it is now synchronous, it would be very easy for a 1st party site to maliciously or accidentally set a web-wide API, without the user being informed.
I agree that new site-wide API is a good idea, as it will be simpler to implement and does not have the problem of bombarding users with exception dialogs, but it would be a bad idea to project this onto the web-wide one.
I therefore suggest we either remove the web-wide API or insist that it is implemented as it was before, with a browser UI informing the user and getting agreement.
Related Actions Items:
No related actions
Related emails:
  1. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from mts-std@schunter.org on 2013-04-16)
  2. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from singer@apple.com on 2013-04-16)
  3. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from jmayer@stanford.edu on 2013-04-15)
  4. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from mts-std@schunter.org on 2013-04-15)
  5. RE: Batch closing of TPE-related issues (response by April 16) (from michael.oneill@baycloud.com on 2013-04-15)
  6. Re: Batch closing of TPE-related issues (response by April 16) (from mts-std@schunter.org on 2013-04-15)
  7. ISSUE-161: Discussion of semantics and alternatives to "!" (was: Batch closing) (from mts-std@schunter.org on 2013-04-15)
  8. Re: Batch closing of TPE-related issues (response by April 16) (from john@consumerwatchdog.org on 2013-04-12)
  9. Re: Batch closing of TPE-related issues (response by April 16) (from jmayer@stanford.edu on 2013-04-12)
  10. Re: Batch closing of TPE-related issues (response by April 16) (from david@appnexus.com on 2013-04-12)
  11. RE: Batch closing of TPE-related issues (response by April 16) (from michael.oneill@baycloud.com on 2013-04-12)
  12. Batch closing of TPE-related issues (response by April 16) (from mts-std@schunter.org on 2013-04-12)
  13. Re: TPWG agenda for Wednesday, January 16 (from jmayer@stanford.edu on 2013-01-30)
  14. Re: TPWG agenda for Wednesday, January 16 (from singer@apple.com on 2013-01-29)
  15. Re: ISSUE Cleanup: Please reconfirm your support of Raised ISSUES (by Jan 30) (from jmayer@stanford.edu on 2013-01-24)
  16. Re: ISSUE Cleanup: Please reconfirm your support of Raised ISSUES (by Jan 30) (from david@networkadvertising.org on 2013-01-21)
  17. ISSUE Cleanup: Please reconfirm your support of Raised ISSUES (by Jan 30) (from mts-std@schunter.org on 2013-01-21)
  18. Re: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from rigo@w3.org on 2012-12-06)
  19. Re: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from singer@apple.com on 2012-12-05)
  20. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-05)
  21. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from wileys@yahoo-inc.com on 2012-12-05)
  22. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-05)
  23. Re: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from singer@apple.com on 2012-12-04)
  24. Re: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from singer@apple.com on 2012-12-04)
  25. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-04)
  26. Re: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from david@networkadvertising.org on 2012-12-04)
  27. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-04)
  28. Re: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from singer@apple.com on 2012-12-03)
  29. ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-03)
  30. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from wileys@yahoo-inc.com on 2012-12-03)
  31. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-03)
  32. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from wileys@yahoo-inc.com on 2012-12-03)
  33. RE: ISSUE-187 - What is the right approach to exception handling & ISSUE-185 (from michael.oneill@baycloud.com on 2012-12-02)
  34. RE: tracking-ISSUE-185 (WebWide Not): There should not be an API for web-wide exceptions [Tracking Preference Expression (DNT)] (from wileys@yahoo-inc.com on 2012-10-28)
  35. Re: tracking-ISSUE-185 (WebWide Not): There should not be an API for web-wide exceptions [Tracking Preference Expression (DNT)] (from craigs@otalliance.org on 2012-10-28)
  36. tracking-ISSUE-185 (WebWide Not): There should not be an API for web-wide exceptions [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-10-28)

Related notes:

Thanks for the input. I understand this concern. However, I believe that your concern is addressed: While the API is synchronous, user agents may reconfirm user's agreement with site-wide exceptions before storing them in the database. We may emphasize in the TPE spec that this behavior is permitted and then close iSSUE-185.

Matthias Schunter, 21 Jan 2013, 14:18:34

Closed (unless I receive further feebdack by April 16):

- We reached agreement that there will be an API for web-side exceptions
- The discussion how to ensure that sites obtain proper consent before registering a web-wide exception will continue under ISSUE-193

Matthias Schunter, 15 Apr 2013, 10:39:43

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