W3C home > Mailing lists > Public > public-tracking@w3.org > May 2012

ACTION-175: Draft API method for sites to remove, a la removeTrackingException()

From: TOUBIANA, VINCENT (VINCENT) <Vincent.Toubiana@alcatel-lucent.com>
Date: Tue, 15 May 2012 18:15:05 +0200
To: "public-tracking@w3.org" <public-tracking@w3.org>
Message-ID: <4D30AC7C2C82C64580A0E798A171B444488F97D981@FRMRSSXCHMBSD1.dc-m.alcatel-lucent.com>
The action item suggests that this API should be called by websites to remove tracking exceptions but the corresponding issue (83) is about user opt-out.
Therefore, I propose two different APIs:
        - One that should  be called by website to remove exceptions,
        - One that should be called by users to revoke exceptions (opt-out).
Vincent



I Context

Users may grant site-specific and site-wide exceptions when they visit a website requesting them.  They may later decide to revoke any type of granted exceptions that are stored in their browsers.
Site specific exception should be stored in the browser under the format <site,domain,value> where value is true if the exception has been granted and false otherwise. Users should not be able to remove site specific exception from the browser but only can only revoke them. It means that the pair <site,domain> remains stored by the browser but it is associated to the value “false”.

II Remove Exception

The removeException API should be called:
-       By the user at any time to remove site-wide exceptions and web-wide exceptions,
-       By a website if it no longer includes a given third party. The website should not be able to revoke an exception but to REMOVE it.  A website can only call this function for exceptions that have been granted on its website. This situation may happen if a first party no longer uses a third party.  If a first party decides to remove an exception for its site, the user may not be notified.

II.1 Method
removeException
Called by a page or a user to delete a user granted exception
Parameter       Type    Nullable        Optional        Description
siteDomain      DOMString<http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html>  ✘       ✘
DomainString    DOMString       ✘       ✘

Return type: Boolean

Notice that either string could be replaced by a wild card which would be interpreted like “any domain” by the browser. User could thus remove web-wide exceptions, site-specific exception and site-wide exceptions.
If a website calls removeException with a site domain different of its own domain, the exception is not removed and the function return false.
If this function is called by the user, at least one of the parameter should be a wildcard. A user should not delete a site specific exception. A user can remove a web-wide exception by calling removeException(*, domain), such call should not revoke the site-specific exceptions that have been granted to this domain.

III Revoke Exception
The revoke Exception API should be called by a user at any time and to revoke site-specific exception or a site-wide exception.

III.2 Method

revokeException
      Called by a user to delete a site specific exception.
Parameter       Type    Nullable        Optional        Description
siteDomain      DOMString<http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html>  ✘       ✘
DomainString    DOMString       ✘       ✘

Return type: Boolean

If a user revokes a site-specific exception or a site-wide exception, the browser should not send DNT:0 to the associated site during the next visit. To make such thing possible, the browser should store a list of revoked exceptions.



Received on Tuesday, 15 May 2012 16:15:43 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 June 2013 10:11:28 UTC