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

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

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Matthias Schunter
Opened on:
2012-10-03
Description:
Scenario: A company has many sites and would like to provide exceptions for all its sites. Assuming site1.com, site2.com all belong to brand.com

Scenario:
- A user visits site1.com
- The site redirects to privacy.brand.com
- privacy.brand.com aims at obtaining exceptions for
*.site1.com
*.site2.com
*.brand.com
as user-friendly as possible

Today, the origin-binding means that this would require 3 API calls (one for each site). The goal of this issue is to provide a single interaction to resolve this problem.
Related Actions Items:
No related actions
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)
  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)
  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)
  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)

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

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