[Cosmo] content negotiation and cosmo

[Brian Moseley]

just read an interesting article about using content negotation with
web services at
<http://bitworking.org/news/WebServicesAndContentNegotiation>.

this is relevant to cosmo in that webdav does not specify what servers
are supposed to return in response to GETs for collections. at the
moment cosmo returns an html "directory listing" for a regular
collection and a composite icalendar object for a calendar collection.
i've given some thought to implementing content negotiation for
collections so that clients could ask for text/html, text/icalendar,
and maybe even application/xml+atom (removing the need for the current
separate /feed/atom/... feed urls).

what do you all think about the issues raised by this article? would
you prefer that cosmo do as much content negotation as possible,
letting the client specify the format of the response via the Accept
header, or should we continue with separate urls for each supported
response content type?