Re: Action-231, issue-153 requirements on other software that sets DNT headers

Hey Matthias - 

Good point re: compliance with Section 5. I'll revise to say that the
software must otherwise comply with this spec, including but not limited to
section 5.

I'm not sure you what you mean by the "modifies a header" clarification. Can
you explain in more depth? Thanks!


From:  "Matthias Schunter (Intel Corporation)" <mts-std@schunter.org>
Date:  Monday, June 10, 2013 9:49 AM
To:  <public-tracking@w3.org>
Subject:  Re: Action-231, issue-153 requirements on other software that sets
DNT  headers
Resent-From:  <public-tracking@w3.org>
Resent-Date:  Mon, 10 Jun 2013 13:50:01 +0000

>     
>  Hi Alan,
>  
>  thanks a lot for the language! I agree with your general thrust.
>  
>  Quick questions:
>  (a) Is there a reason why these add-ons only need to implement Section 5? Why
> not "ensure that the compliance of the user agent is not negatively affected,
> i.e., 
>       that wit the extension in place, the requirements of the DNT  specs are
> still satisfied."
>  (b) In the second part, "modifies a header" is too narrow (causes
> modification).
>  
>  Other feedback?
>  
>  matthias
>  
>  
>  
>  
> On 10/06/2013 15:22, Alan Chapell wrote:
>  
>  
>>  
>>  
>>  
>> Here is my suggestion for language pursuant to Action 231.
>>  
>>  
>>  
>> 
>>  
>>  
>> A user agent MUST have a default tracking preference of unset (DNT is not
>> enabled; no tracking preference signal is sent). A user agent extension or
>> add-on must not alter the user's tracking preference setting unless it
>> complies with Section 5 of this document (User Preferences). Software outside
>> of the user agent that causes a DNT header to be sent (or modifies existing
>> headers) MUST NOT do so without following the requirements of this section;
>> such software also MUST ensure the expressed preference reflects the
>> individual user's intent.
>>  
>> 
>>  
>>  
>> Alan
>>  
>> 
>>  
>>  
>> 
>>  
>>  
>  
>