- From: Matthias Schunter (Intel Corporation) <mts-std@schunter.org>
- Date: Tue, 24 Jan 2017 09:18:36 +0100
- To: public-tracking@w3.org
Hi Roy, I fully agree with your arguments: Without cooperation of the hoster, any DNT a page-owner does can be rendered meaningless and thus should not be done. > Moving the response from header field to page metadata is only a solution for deployment if neither the accuracy nor the timeliness of that response matters. My perception (as a non-expert) was that it does not make that much difference whether information is transmitted as a header or via http-equiv. Could you explain some more why you prefer not allowing http-equiv for the tk signal? Regards, matthias On 24.01.2017 07:12, Roy T. Fielding wrote: > On Jan 24, 2017, at 11:24 AM, Aleecia M. McDonald <aleecia@aleecia.com> wrote: >> The thing is, Wordpress cannot know what my hosted page is doing with data I collect from my DNT visitors. Only I know that. So Wordpress cannot speak on my behalf because they do not know enough. > Yes, that's true. Just like the page owner cannot know what data Wordpress collects from users that request hosted pages, let alone how carefully they manage log files. > > The solution is that there needs to be a legal agreement between the hosted page owner and the host service provider that specifies how to respond to DNT, in both Tk and TSR, and requires both parties to conform to that response. Lack of such an agreement means no accurate response can be given. > > In practice, this is as simple as a configuration option. The problem is getting hosted services to deploy such an option. I don't think we can take any short cuts here without making the tracking response meaningless. > > Moving the response from header field to page metadata is only a solution for deployment if neither the accuracy nor the timeliness of that response matters. > > ....Roy >
Received on Tuesday, 24 January 2017 08:19:09 UTC