On Tue, Jun 1, 2010 at 6:35 PM, Erik Hetzner <[log in to unmask]> wrote:
> There is a time for a URI that can use content-negotiation (the Accept
> header, etc.) to get, e.g., PDF, HTML, or plain text. As an example:
>
> http://example.org/RFC1
>
> And there is a time when we want to explicitly refer to a particular
> resource that has only ONE type. For example, the canonical version of
> an RFC:
>
> http://example.org/RFC1.txt
>
> But these are different resources. If you want to be able to link to
> search results that must be returned in RSS, a query parameter or file
> extension is proper.
>
> But this query param or file extension, in my opinion, is quite
> different than HTTP content negotiation or the Accept header.
Nicely put Erik!
//Ed
|
