ISSUE-140: Do we need site-specific exceptions, i.e., concrete list of permitted thirdparties for a site?
Do we need site-specific exceptions, i.e., concrete list of permitted thirdparties for a site?
- State:
- CLOSED
- Product:
- Tracking Preference Expression (DNT)
- Raised by:
- Matthias Schunter
- Opened on:
- 2012-04-13
- Description:
- The current draft + emails contain three cases of user-granted exceptions:
a) Site-wide (anythirdparty, thissite)
b) Web-wide (thisthirdparty, anywhere)
c) Site-specific List of (thirdparties) on thissite
This ISSUE examines whether case (c) should be dropped or not. - Related Actions Items:
ACTION-173 on Ian Fette to Provide writeup on why managing explicit-explicit pairings is problematic from UI perspective - due 2012-04-19, closedACTION-172 on Nick Doty to Write up more detailed list of use cases for origin/origin exceptions - due 2012-04-30, closedACTION-202 on Matthias Schunter to Write Email to outline alternative proposal to explicit/explicit exceptions - due 2012-05-23, closed- Related emails:
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from michael.oneill@baycloud.com on 2012-10-09)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from fredandw@live.com on 2012-10-09)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from michael.oneill@baycloud.com on 2012-10-09)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from fredandw@live.com on 2012-10-08)
- Re: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from joe@cdt.org on 2012-10-08)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from bs3131@att.com on 2012-10-08)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from michael.oneill@baycloud.com on 2012-10-08)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from fredandw@live.com on 2012-10-08)
- RE: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from adrianba@microsoft.com on 2012-10-08)
- Re: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from mts-std@schunter.org on 2012-10-08)
- Re: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from jmayer@stanford.edu on 2012-10-07)
- Re: Housekeeping: Closing ISSUE-140 (concrete/explicit list of exceptions) (from mts-std@schunter.org on 2012-10-03)
- Re: Housekeeping: Closing ISSUE 140 (concrete/explicit list of exceptions) (from jmayer@stanford.edu on 2012-10-02)
- Housekeeping: Closing ISSUE 140 (concrete/explicit list of exceptions) (from mts-std@schunter.org on 2012-10-01)
- Closing ISSUE-140 (site-specific explicit/explicit exceptions) [Respond by September 05]? (from mts-std@schunter.org on 2012-08-27)
- Re: agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
- agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
- agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
- Re: Agenda for July 18, 2012 DNT WG Call on TPE (from fielding@gbiv.com on 2012-07-18)
- ACTION-203 : Text for transitive model (from rigo@w3.org on 2012-05-25)
- Re: Agenda for May 23, 2012 DNT WG Call V01 (from singer@apple.com on 2012-05-23)
- Agenda for May 23, 2012 DNT WG Call V01 (from mts-std@schunter.org on 2012-05-23)
- Re: explicit-explicit exception pairs [a proposed resolution to ISSUE-140] (from singer@apple.com on 2012-05-15)
- RE: Agenda for May 16, 2012 DNT WG Call (from wileys@yahoo-inc.com on 2012-05-14)
- Agenda for May 16, 2012 DNT WG Call (from mts-std@schunter.org on 2012-05-14)
- Re: explicit-explicit exception pairs [a proposed resolution to ISSUE-140] (from mts-std@schunter.org on 2012-05-14)
- Agenda for 02 May, 2012 call (from mts-std@schunter.org on 2012-05-01)
- tracking-ISSUE-140: Do we need site-specific exceptions? [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-04-13)
Related notes:
Concerns raise were:
- The thirdparties actually used are known by the browser anyway
- How do we populate and manage the list for the site?
- What useful actions can user agents do with this data? (If we do not see how it can be used, may may choose not to transmit it).
- Transmitting this information is important for compliance
Display change log