- From: Joshua Allen <joshuaa@microsoft.com>
- Date: Thu, 4 Jul 2002 23:35:21 -0700
- To: "Roy T. Fielding" <fielding@apache.org>, "Patrick Stickler" <patrick.stickler@nokia.com>
- Cc: "ext Paul Prescod" <paul@prescod.net>, "WWW TAG" <www-tag@w3.org>
> > Web applications do not have access to the actual resource, no, but > > a representation of the resource is analogous to getting the actual > > resource. For that to happen, the resource has to be digitally > > encoded in some fashion. > > We have had this discussion far too many times. Web applications may > or may not have access to the actual resource, depending on the properties Maybe that is because the discussion has veered off-topic. There is no question that HTTP returns a representation of a resource. However, that does not mean that URIs using the http: scheme should be used for things other than web pages. HTTP is just one protocol, with semantics that are useful for a finite set of circumstances. URIs in practice utilize many schemes besides just http:. Saying that all resources can or should be identified with http: URIs is completely insane.
Received on Friday, 5 July 2002 02:35:53 UTC