- From: Dan Brickley <danbri@w3.org>
- Date: Mon, 24 Dec 2001 00:54:15 -0500 (EST)
- To: Tim Berners-Lee <timbl@w3.org>
- cc: Jonathan Borden <jborden@mediaone.net>, "Sean B. Palmer" <sean@mysterylights.com>, Dan Connolly <connolly@w3.org>, www-rdf-interest <www-rdf-interest@w3.org>
On Sun, 23 Dec 2001, Tim Berners-Lee wrote: > True. A resource for a non-HTTP space can be whatever that URI space says > it > is. It is just HTTP which really creates a world of documents. > > mailto: for example, defines a space of mailboxes which are not documents. > I should have limited what I said to the http: space. Am I right in thinking one can use HTTP 1.1 (the protocol) to ask an HTTP service about non-HTTP URIs? (Don't web-caches basically work this way?) I'm still of the opinion that many HTTP-named resources aren't network serializable, most notably web services (online thermometers, coffee pots etc, alongside the usual databases, web indexes...). HTTP's notion of document seems pretty weak, if it allows services and the like to count; weaker still if it includes all the stuff that one can ask an HTTP server about regardless of the species of name used. Dan
Received on Monday, 24 December 2001 00:54:18 UTC