- From: Mark Nottingham <mnot@mnot.net>
- Date: Sun, 14 Jun 2009 14:15:05 +1000
- To: Ian Hickson <ian@hixie.ch>
- 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>
Of course resources are abstract, Ian. You may have no need to refer to anything but the response (or entity, or representation; all might be appropriate), but others do need to refer to the thing that the URI identifies, and the thing that generates the response. This argument seems to be covering the same ground quite quickly. As I said, if you want to press the point, go ahead and use the term this way in a submission; going around in circles on this list doesn't do any good. On 14/06/2009, at 2:09 PM, Ian Hickson wrote: > 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. `._.-(,_..'-- > (,_..'`-.;.' -- Mark Nottingham http://www.mnot.net/
Received on Sunday, 14 June 2009 04:15:43 UTC