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

Re: ACTION-122, ISSUE-125: Pro-actively requesting exceptions

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 15 Feb 2012 17:17:07 -0800
Cc: "<public-tracking@w3.org> (public-tracking@w3.org)" <public-tracking@w3.org>
Message-Id: <C7B80DD8-10EA-434B-9364-579548AF2E7C@gbiv.com>
To: Nicholas Doty <npdoty@w3.org>
Added to TPE in r1.70 with only minor wording changes.

I should note that the entire section 6 (Site-specific exceptions)
needs a serious rewrite to be comprehensible to anyone outside the
WG (and probably to most people inside the WG).  That might be a
good way for David Singer to get in the flow. ;-)

On Feb 14, 2012, at 11:00 PM, Nicholas Doty wrote:

> My proposal for potentially using the JavaScript site-specific exception API to pro-actively request exceptions. The overview section documents what I interpreted to be the potential use cases here.
> This would go towards the end of the Site-Specific Exception section of tracking-dnt.html. If we decide on an API for Web-wide exception, we would likely want to update this proposal to apply to that method in the same way.
> Thanks,
> Nick
> # Exceptions when Do Not Track is not enabled
> ## Overview (non-normative)
> Sites may wish to pro-actively request exceptions (site-specific or Web-wide) for tracking elements even when a user arrives without Do Not Track enabled on their user agent. Users may wish to grant affirmative permission to tracking on or by certain sites even without expressing a preference about tracking in general.
> ## Pro-actively requesting exceptions
> User agents MAY instantiate <code>NavigatorDoNotTrack.requestSiteSpecificTrackingException()</code> even when <code>navigator.doNotTrack</code> is null. Sites SHOULD test for the existence of <code>requestSiteSpecificTrackingException</code> before calling the method. Exceptions granted in this context MAY be persisted, for example, when a user later enables Do Not Track in their browser. User agents MAY send a DNT:0 header even when Do Not Track has not been enabled to express the user's affirmative consent for tracking by this entity.
> Note: users may not configure their agents to have simple "default" values for DNT, but use different browsing modes or other contextual information to decide on a DNT value. What algorithm a user agent employs to determine DNT values (or the lack thereof) is out of the scope of this specification.
Received on Thursday, 16 February 2012 01:17:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:38:34 UTC