W3C home > Mailing lists > Public > public-sws-ig@w3.org > November 2004

Suitable OWL-S profile

From: Charlie Abela <charlie@semantech.org>
Date: Tue, 2 Nov 2004 01:55:08 +0800
Message-ID: <1099331708.4186787ce3b8d@>
To: public-sws-ig@w3.org


work on service matchmaking has focused mainly on matching the inputs and
outputs that a requester presents with those that a service stored in the
matchmaker provides.
I want to discuss another aspect of the service matching phase. With the above
situation it seems that the agent searching for a service has to know which
inputs/outputs the service has to provide, independently of what the service is
used for.
I want to consider an example related to an airtravelling service (like the
BravoAir service). I want to consider the following situations:
1. suppose that the user is not making use of an agent to search for this
service but is manually trying to find it tru a search engine, the keywords
that this person enters could be similar to air travel and flights.
2.suppose that now the user makes use of an agent, the same type of search would
apply, cause one cannot assume that the person requester knows apriori what the
inputs and outputs would be so he will not instruct his agent about these.
Even though most examples I've seen state that the user will instruct his agent
tru a natural language interface, this solution seems to be quite far at the
moment, given also that there is no means of capturing context.

So given these situations, I would like to ask whether it would be more suitable
to provide a way for the user to be able to instruct his agent with info about
the type of service he requires and the objective he wants to reach and not by
providing the I/Os (the I/Os will be considered at a later stage of the
matching phase, since most air travel services have similar I/Os).

something along these lines:

serviceCategory -> air travel (points to some standard classification: UNSPSC or
Objective-> flight reservation (points to some air travel domain ontology)


This message was sent using IMP, the Internet Messaging Program.
Received on Monday, 1 November 2004 18:04:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:54:13 UTC