W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

Re: Content Sniffing impact on HTTPbis - #155

From: Roy T. Fielding <fielding@gbiv.com>
Date: Sun, 14 Jun 2009 13:06:13 -0700
Message-Id: <87906802-7677-4511-BC8A-D1A71ED5B2C8@gbiv.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
To: Ian Hickson <ian@hixie.ch>
On Jun 14, 2009, at 12:21 PM, Ian Hickson wrote:
> On Sun, 14 Jun 2009, Julian Reschke wrote:
>>
>> HTTP URIs are URLs, and URLs simply are URIs that also double as
>> locators (see RFC 3986). I don't see how this changes the  
>> definition of
>> being an identifier at all.
>
> I'm not arguing that they aren't identifiers, I'm arguing that when  
> you
> dereference them you get an actual concrete resource, and that saying
> that you get a resource representation is pointless and confusing  
> hair-
> splitting which doesn't actually help people understand the specs when
> they implement them, since the thoretical "resource" construct never
> actually needs to be dealt with in practice.

I'd like to see how you would describe a resource that accepts POSTed
information without ever returning a "bag of bits", how you are going
to describe a resource whose only purpose is to redirect to the
"site of the day", or how you would implement a gateway to my
friend's air conditioning unit.  I could enumerate thousands of
examples of how limited your view of the Web really is, but then
I already have done that many times.  Read the archives.

....Roy
Received on Sunday, 14 June 2009 20:06:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:03 GMT