Re: PaceContentNegotiationSection

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