Re: URLs and access issues

For those interested, some of these issues and a proposed solution were 
addressed in a paper
I published a few years ago (in a different lifetime). 
The paper's solution is probably naive, but I think some of the points
made are still relevant.

Kaplan, A. and Lunn, J., /FlexXML: Engineering a more flexible and 
adaptable Web/, *IEEE International Conference on Information 
Technology: Coding and Computing*, Las Vegas, NV, April 2001. 
http://www.cs.clemson.edu/~kaplan/research/flexxml.pdf

Alan

-- 
Alan Kaplan, Ph.D.                      
Lead Scientist                          Voice:  +1-609-734-7339 
Panasonic Digital Networking Laboratory Fax:    +1-609-987-8827 
Panasonic R&D Company of America        Mobile: +1-609-865-6061 
2 Research Way, 3rd Floor               Skype/AIM: commishkap
Princeton, NJ 08540 USA


>It's possible to identify the device and then render the content with
>the use of an adaptation solution - this does not require the use of
>more then one URI. Go to www.aol.com using a PC and then use a mobile
>device. 1 URI different content.
>
>Paul
>
>  
>
>>-----Original Message-----
>>From: public-bpwg-request@w3.org [mailto:public-bpwg-request@w3.org]
>>    
>>
>On Behalf
>  
>
>>Of Michael Kaye
>>Sent: 19 August 2005 19:57
>>To: public-bpwg@w3.org
>>Subject: Re: URLs and access issues
>>
>>
>>Paul Walsh wrote:
>>
>>    
>>
>>>You don't need different URIs to represent
>>>different content - this is why we have adaptation.
>>>
>>>
>>>      
>>>
>>(further to my email)
>>
>>Yes, you do.
>>
>>If you start requiring that all caches across the internet MUST NOT
>>cache any content (as it could change at any time, depending on the
>>    
>>
>time
>  
>
>>of day, the device, anything) then the gain in bandwidth use is going
>>    
>>
>to
>  
>
>>be staggeringly huge.
>>
>>Requiring that all mobileOK content is not cached is not a step
>>    
>>
>forward
>  
>
>>that I'd like to see occur.
>>
>>Michael.
>>    
>>
>
>
>  
>