- From: Michael Mealling <michael@neonym.net>
- Date: Tue, 30 Jul 2002 10:25:02 -0400
- To: "Ian B. Jacobs" <ij@w3.org>
- Cc: www-tag@w3.org
On Tue, Jul 30, 2002 at 08:38:03AM -0400, Ian B. Jacobs wrote: > [Ian] > DC: TimBL wants a guarantee that someone will > never find a car at the other end. I don't think you can/should do that. First of all you have to define what the "other end" is and how you got there. It is perfectly reasonable to expect the output of a URI to a POST operation to cause a car to be delivered to my location within the next 10 minutes. Its called a taxi service. I can even define one that will purchase and deliver a new car in less than 24 hours. Given the latency of some email those time periods are prefectly reasonable network response times. If in the RDF/web services there is a URI (even an HTTP one which irks me personally) that denotes the actual physical car, it is very reasonable to have a series of simple processes that are the equivalent of a GET on that physical thing. This is essentially what Amazon is in the business of doing with its One Click service. Denying that those are part of the architecture is arbitrarily decided that the web architecture is limited to particular transport layers which isn't a good thing. RDF is an important development here because it finally gives us the ability to determine from a consuming application just what the semantics are of that GET operation. Especially when you can get into statements about what representation of the 'car' concept you want. Do you want a digital representation in JPEG or do you want it to appear out front for a test drive? > [Ian] > TB: I suggest we publish these logs and stand > back and see what happens on www-tag. You asked for it! ;-) -- -------------------------------------------------------------------------------- Michael Mealling | Vote Libertarian! | urn:pin:1 michael@neonym.net | | http://www.neonym.net
Received on Tuesday, 30 July 2002 10:26:54 UTC