W3C home > Mailing lists > Public > public-sws-ig@w3.org > June 2006

What's the point in using OWL-S?

From: Gerhard Austaller <gerhard.austaller@o2online.de>
Date: Fri, 2 Jun 2006 06:30:25 +0200
To: <public-sws-ig@w3.org>
Message-ID: <000401c685fd$44e95400$9aa35382@ntdom.tk.informatik.tudarmstadt.de>


I still have not understood what exactly an agent can achieve with the owl-s
description of a service.

Let's take the Bravo Air example. For an agent to book a ticket it has to
"understand" the concepts used there. But where's the big advantage in
having an interface (in WSDL) defined or an annotated WSDL like WSDL-S? I
admit having the exact order of steps defined to achieve something is a step
in the right direction...

Now I want my agent also to book a ticket at another airline. So if this
airline uses another ontology that ontology also as to be understandable to
the agent made by an programmer. So do we assume that all airlines agree on
one ontology and further also on the process how to do something?

Do I miss something? Can please somebody explain or give me pointers what's
a programmer can gain from an owl-s description?

Received on Friday, 2 June 2006 16:30:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:32:54 UTC