Re: PaceContentNegotiationSection

I mean the same thing everyone else does -- serving two or more resources at 
the same URI which are indisputably not the same resource. If both of these:

user1.atomsrv
user2.atomsrv

Are returned from the same URI it is a collision.  There's nothing wrong with 
having multiple introspection documents, but speccing that they must all 
share a common URI still sounds like an RPC endpoint to me.

If you are returning "Joe's collection" and also "Mary's collection", 
depending on which user is requesting /introspection, then you have a URI 
collision at /introspection.  Because you aren't sending Joe XHTML and Mary, 
HTML as with standard conneg where all documents returned are representations 
of the same resource, with a Content-Location specifying exactly which 
representation the user has received, i.e. = /index.xhtml for Joe and 
= /index.html for Mary.  The resource is still /index no matter which 
representation is retrieved.

-EJB

>-----Original Message-----
>From: James M Snell [mailto:jasnell-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx]
>Sent: Friday, August 18, 2006 04:05 PM
>To: eric-MkmoNbc1SAncr/OS1auqaA@xxxxxxxxxxxxxxxx
>Cc: 'Asbjørn Ulsberg', atom-protocol-O6w3ZxSwtmQ@xxxxxxxxxxxxxxxx
>Subject: Re: PaceContentNegotiationSection
>
>As others have asked, please explain the "URI collision". What do you
>mean by "URI collision"?
>
>- James
>
>Eric J. Bowman wrote:
>>> I think that is a bad assumption and is why we are having this discussion.  
>>> Change the assumption and your implementation, put the service document on  
>>> another URI, and the problems you are experiencing and having a hard time  
>>> discussing with us should evaporate in thin air.
>>>
>> 
>> Looking beyond my placement of the service document, there is still a URI 
>> collision inherent in this setup, whether the URI is...
>> 
>> http://example.com/
>> 
>> ...or...
>> 
>> http://example.com/service
>> 
>> Or anything else for that matter, the spec is still describing a URI 
>> collision as I've tried to explain by showing what I return in Content-
>> Location.  I'd still like to know what it is others are returning, /service 
>> for every user?  Going beyond a single-user setup, this will reliably serve 
>> multiple resources at the same URI.
>> 
>> -EJB
>> 
>> 
>> 
>> 
>