Edit ISSUE-171: How can the exception API be used to grant site-wide exceptions to multiple sites?

Nickname:

Title:

State:

Product:

Raised By:

Description:

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

Related emails:

  1. Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160 (from david@networkadvertising.org on 2012-11-05) (from david@networkadvertising.org on 2012-11-05)
  2. Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160 (from singer@apple.com on 2012-11-05) (from singer@apple.com on 2012-11-05)
  3. Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160 (from mts-std@schunter.org on 2012-11-05) (from mts-std@schunter.org on 2012-11-05)
  4. tracking-ISSUE-171: How can the exception API be used to grant site-wide exceptions to multiple sites? [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-10-03) (from sysbot+tracker@w3.org on 2012-10-03)

Related notes:

Proposed solution:
a) A site (e.g., privacy.brand.com) declares its affiliated sites in the "same-party" attribute within the tracking status resource
b) The site calls for a site-wide exceptions using the API
c) We update the spec in a way that this exception is valid for all
third parties ON ALL SITES declared to belong to the same party as indicated
by the same-party attribute.

Matthias Schunter, 3 Oct 2012, 11:16:35

The consensus was to keep the origin policy, i.e., to require each domain to ask for a site-wide exception for itself. This may require iframes to obtain exceptions for multiple sites.

Matthias Schunter, 25 Nov 2012, 16:29:26


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 $