Re: PaceContentNegotiationSection

Eric J. Bowman wrote:
> 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.
> 

Great, we haven't spec'd that all introspection docs you serve from your
server MUST have the same URI.  What URI(s) you choose to server your
introspection docs from is your own concern.

> 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.
> 

No, in our case the each user gets a representation of the resource that
is specific to that individual user.  Just like if we both go to the
personalized version Google's home page -- we'll each see different
representations of the same resource served from the same URI. That's
just the way things work.

- James