- From: Roy T. Fielding <fielding@apache.org>
- Date: Sun, 2 Feb 2003 23:43:09 -0800
- To: Miles Sabin <miles@milessabin.com>
- Cc: www-archive@w3.org
> So if your thesis (which is a Resource which isn't on the web) is at > http://.../thesis, If my thesis were at that URI, then it would be on the Web. > and GETs on that URI return an HTML representation, > could it also be true that http://.../thesis also identifies a web page > (which is a different Resource which _is_ on the web)? If my thesis were identified by that URI, then a GET on that URI might result in an HTML representation, but the URI would never directly identify that representation. If it did, I wouldn't be able to change the representation. Web pages are a construct resulting from an action on the resource. > If not, why not. Because resource and representation are separate concepts within the architecture and visibly different within the implementations, thus deserving of different identifiers in those circumstances where the naming authority wishes the representation to be separately identifiable. If the representation is identified by the resource URI, then how does the server differentiate between different representations of a single resource, particularly in the presence of remote authoring and content negotiation? ....Roy
Received on Monday, 3 February 2003 03:07:36 UTC