- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Fri, 9 May 2014 10:01:37 -0700
- To: "Jack L. Hobaugh Jr" <jack@networkadvertising.org>
- Cc: W3C DNT Working Group Mailing List <public-tracking@w3.org>
On May 9, 2014, at 7:23 AM, Jack L. Hobaugh Jr wrote: > Hi Roy, > > Thanks for your response. > > Please further explain how the TSR would be used as a dynamic, per user response. > > My understanding of the TSR as specified in Section 6.4 of the TPE is that the TSR is a static JSON representation on the server that contains information about either the potential tracking behavior of resources on that server or can be used to represent multiple, request specific tracking polices (also static JSON format) on the server that can be identified by a status-id value returned in the Tk header. The response is like any other page on the Web. It can be dynamically produced or static. For any tracking site that indicates consent, it will have to be dynamic. This is why the user agent needs to send its normal cookies for the designated site when making the request. > Also, my understanding is that the JSON representation will be updatable but normally static. If that is true then isn’t it also true that the only possibility for a dynamic response would be through the choice (by the server) of appending a particular status-id to the Tk header based on information in the request? Please see the section on caching in TPE. ....Roy
Received on Friday, 9 May 2014 17:01:54 UTC