Re: Issue-207

Hi

I think it’s as dynamic as the site wants it to be.  Just as some sites tailor their ‘normal’ content based on various information in the request headers (“if you visit my site from an IP address in the UK, I show you different content than others”, and indeed varying the served content by user-agent used to be quite common to work around which UAs had implemented, or had bugs in, various features), the TSR can appear ‘static’ but actually be subject to ‘internal’ dynamism at the server.  I think.  I may be wrong (it’s friday, that’s my excuse).


On May 9, 2014, at 12:24 , Jack L. Hobaugh Jr <jack@networkadvertising.org> wrote:

> Hi Roy,
> 
> Thanks for your response.
> 
> Perhaps I misunderstood your original statement.  I understood you to state that the TSR itself is dynamic.
> 
> My understanding of Section 6 of the TPE is that the TSR is a static, but modifiable, JSON entity.  
> 
> If you view the TSR as a dynamic entity, an explanation would be helpful.
> 
> Best regards,
> 
> Jack
> 
> Jack L. Hobaugh Jr
> Network Advertising Initiative | Counsel
> 1620 Eye St. NW, Suite 210 Washington, DC 20006
> P: 202-347-5341 | jack@networkadvertising.org
> 
> The information contained in this e-mail is confidential and intended for the named recipient(s) only. However, it is not intended as legal advice nor should you consider it as such. You should contact a lawyer for any legal advice. If you are not an intended recipient of this email you must not copy, distribute or take any further action in reliance on it and you should delete it and notify the sender immediately.
> 
> 
> 
> 
> 
> On May 9, 2014, at 1:01 PM, Roy T. Fielding <fielding@gbiv.com> wrote:
> 
>> 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
>> 
> 

David Singer
Manager, Software Standards, Apple Inc.

Received on Friday, 9 May 2014 20:01:44 UTC