- From: Mark Baker <distobj@acm.org>
- Date: Tue, 22 Oct 2002 13:50:04 -0400
- To: www-ws-arch@w3.org
I'm taking at stab at outlining a REST based solution to the travel
agent use case in our usage scenarios, and I've noticed that it does
appear to be prescribing a Web services based solution, rather than
being solution-neutral as I'd expect a use case to be.
For example, in 3.1.5.1.2 it says;
3. The travel agent service finds a list of airlines.
4. For each airline found:
a. The travel agent service requests a description of how to
communicate with the service found.
b. The travel agent service requests a list of flights
accommodating the user.
rather than just;
3. The service finds a list of flights accomodating the user
4a suggests that something like WSDL is required, because the flight
info is somehow hidden behind an airline interface. On the Web, I'd
make sure that both the airlines and flights had URIs, so that search
engines (and other agents) could treat each as first class objects.
As I find more cases of this, I'll write it down and summarize when I'm
finished.
MB
--
Mark Baker, CTO, Idokorro Mobile. Ottawa, Ontario, CANADA.
http://www.markbaker.ca http://www.idokorro.com
Received on Tuesday, 22 October 2002 13:48:15 UTC