ACTION-202: Write Email to outline alternative proposal to explicit/explicit exceptions
Write Email to outline alternative proposal to explicit/explicit exceptions
- State:
- closed
- Person:
- Matthias Schunter
- Due on:
- May 23, 2012
- Created on:
- May 16, 2012
- Associated Issue:
- ISSUE-140
- Related emails:
- Re: ACTION-202 Alternative to explicit/explicit API (from jmayer@stanford.edu on 2012-07-09)
- Re: ACTION-202 Alternative to explicit/explicit API (from singer@apple.com on 2012-07-09)
- Re: ACTION-202 Alternative to explicit/explicit API (from singer@apple.com on 2012-07-09)
- AW: Re: ACTION-202 Alternative to explicit/explicit API (from mts-std@schunter.org on 2012-07-09)
- Re: ACTION-202 Alternative to explicit/explicit API (from jmayer@stanford.edu on 2012-07-08)
- Re: ACTION-202 Alternative to explicit/explicit API (from mts-std@schunter.org on 2012-07-07)
- Re: ACTION-202 Alternative to explicit/explicit API (from singer@apple.com on 2012-05-23)
- ACTION-202 Alternative to explicit/explicit API (from mts-std@schunter.org on 2012-05-23)
- Re: ACTION-202 Alternative to explicit/explicit API (from jmayer@stanford.edu on 2012-05-22)
Related notes:
Outline:
JAVASCRIPT: Only site-wide and web-wide
Well-known URL: OPTIONAL List of direct third parties (maybe also any and/or responsibilities) [Empty means that no specifics are promised]
User agent: May snapshot URL at time of site-wide call and use this snapshot for determining whether to send DNT;0 or DNT;1 to third parties.
Sites: if they decided to post a list, then they bind themselves to the list.
SUbsequent enlargements to the list may require calling the javascript API again.
Display change log.