RE: [w3c/dnt] Add more meta data in the Tracking Status Resource (#22)

I agree it should be OK for the UA to let the user choose, but the TPE says the set of targets should be “handled as a unit”, so “one out, all out”. 

 

The only way DNT:0 would not be sent would be if the request was blocked, or the UAs implementation of the TPE had a bug. I think requiring the UA to report its own bug is bizarre.

 

 

 

 

 

From: Shane Wiley [mailto:wileys@yahoo-inc.com] 
Sent: 10 May 2017 17:26
To: Mike O'Neill <michael.oneill@baycloud.com>; public-tracking@w3.org
Subject: Re: [w3c/dnt] Add more meta data in the Tracking Status Resource (#22)

 

Or it manages the outcome where a browser provides independent domain control to a user regardless of the "all or nothing" proposition currently stated in the TPE.  

 

I'm personally okay with a user making domain level decisions that go against the Site-Wide Exception that was originally granted as that should be their choice.  But we need balance in transparency to understand the choices the user has made so as a publisher I know how to react from there.

 

- Shane

 

Shane Wiley
VP, Privacy
Yahoo

 

  _____  

From: Mike O'Neill <michael.oneill@baycloud.com <mailto:michael.oneill@baycloud.com> >
To: public-tracking@w3.org <mailto:public-tracking@w3.org>  
Sent: Wednesday, May 10, 2017 3:08 AM
Subject: RE: [w3c/dnt] Add more meta data in the Tracking Status Resource (#22)

 

If site-wide exception exists then it is a bug if a non-empty set of

subresources receives anything other than DNT:0.

 

If the user revokes their consent for any then no subdomains will get DNT:0

(because they MUST be handled as a unit)

 

This is an API for a user agent to report it has a bug, which is pointless.