W3C home > Mailing lists > Public > public-tracking@w3.org > October 2011

Re: Propose to drop from the strawman: ISSUE-93

From: Aleecia M. McDonald <aleecia@aleecia.com>
Date: Wed, 26 Oct 2011 01:10:02 -0700
Message-Id: <22C880BD-0193-43B2-A459-A533EFEF146A@aleecia.com>
To: Tracking Protection Working Group WG <public-tracking@w3.org>

On Oct 26, 2011, at 12:40 AM, Nicholas Doty wrote:

> On Oct 26, 2011, at 12:04 AM, Jonathan Mayer wrote:
>> What I'm not comfortable with is the increasing frequency with which stakeholders are claiming issues are "out of scope."  As I read it, and I think in any plain reading, the working group charter is very broad.  A rough parallel for the American law fans at the table: claiming something is "out of scope" is roughly akin to claiming it's unconstitutional.  You should believe, and be prepared to defend, that not only is it a wrong decision, but it's a decision that clearly falls outside the working group's zone of discretion.
> 
> I'd agree that this issue is in scope: how or whether a first-party degrades service speaks to practices for compliance with the user preference and could be part of a code of conduct for services that receive a DNT signal.
> 
> I actually thought that ISSUE-93 was raised in part by Carmen (please correct me if I'm wrong) to question whether the Tracking Preference Expression (DNT) spec should enable first parties to know whether a user is browsing with DNT on for a particular third party, with the concern being that a first party might penalize that user for opting out. (This is connected to ISSUE-59.)
> 
> It sounds like some participants definitely want first parties to know when a third party is receiving a DNT signal precisely for the opportunity to negotiate over it. But it seems to me like this question is in scope both for the compliance document and the preference expression document.

Reminder, text from a prior post I made:

> Note that in many places there are just bare issues listed. It does not mean that we will accept the premise of the issue, it means that it is something we will discuss and resolve (so "should we think about XYZ?" could be resolved as "No, we should not.") 


I think issue-93 is a good example of what I was trying to convey. Our cleanest path forward is likely to note in the spec that some think issue-93 is in scope, some think it is out, and we will discuss it fully in the future. 

	Aleecia
Received on Wednesday, 26 October 2011 08:10:32 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:44:41 UTC