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

Re: Content Sniffing impact on HTTPbis - #155

From: Ian Hickson <ian@hixie.ch>
Date: Sun, 14 Jun 2009 04:09:44 +0000 (UTC)
To: Mark Nottingham <mnot@mnot.net>
Cc: Julian Reschke <julian.reschke@gmx.de>, Mark Baker <distobj@acm.org>, Adam Barth <w3c@adambarth.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <Pine.LNX.4.62.0906140407160.1648@hixie.dreamhostps.com>
On Sun, 14 Jun 2009, Mark Nottingham wrote:
> 
> The first task of a specification is to clearly, unambiguously state how 
> to implement.

*Exactly*. And there is no need to refer to a theoretical separation 
between "resources" and "resource representations" to do that.


> Changing terminology because lots of people don't understand the 
> concepts of the Web won't improve their understanding of the Web; they 
> have to apply themselves for that to happen.

No. Their understanding of the Web is fine. The problem is that the Web 
doesn't actually match what you want it to be. There is no actual 
difference between the "resource" and the "resource representation". The 
"resource" as you describe it _doesn't exist_. It's a theoretical 
construct that is completely unnecessary to describe how the Web works.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Sunday, 14 June 2009 04:10:17 GMT

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