Re: PaceContentNegotiationSection

>
>Ok, so a GET to http://example.com would specifying Accept:
>application/atomserv+xml;q=1.0 would result in a redirect (permanent or
>temporary) to the appropriate service document for the authenticated
>user.  Am I missing something?
>

Yes, you are.  If a request comes in which has a higher q-value for APP than 
it does for HTML the response is index.atomsrv, if HTML wins out the response 
is index.html, no redirection involved.  The request for index.atomsrv is 
then negotiated on the basis of AUTH headers (which would be the starting 
point if HTML representations weren't involved), so the request for index.
atomsrv is really a request for user.atomsrv, which is what I return in 
Content-Location and classify accordingly as a URI collision since the 
request was for /index.something not /user.anything -- the resource is varied 
across requests instead of the representation being varied across requests.

-EJB

>> Really, I thought this was the purpose of the MIME type, under the examples 
>> others have given there's no reason I can fathom that it can't be an 
>> existing XML MIME type of some sort, 'applicaton/xml' or such.  The only 
>> reason I could deduce for it was to allow negotiation.
>> 
>
>There are several uses for the mime type, conneg is just one.
>
>- James
>