Service Profile

Hi, I've been away from this list for quite some time and am trying to catch
up with some issues.

One of my last emails was related to the Service Profile and I would like to
re-latch with this issue here.
I have been noting with interest the developments occurring in other SWS
initiatives, such as WSMO and IRS II. Well one thing that I noted is the
separation between the service capabilities and service goals. Though in the
OWL-S profile there is a way to define both, at least to some extent, it is
a bit unnatural to think of services by their IOPEs. Are there any problems
with modifying the profile to reflect capabilities and goals and not just
IOPEs?
The idea I want to put forward is simple. From a user point of view it is,
in my opinion, almost impossible to identify the IOPEs for a required
service, at most, the user might be able to identify the category, taxonomy
or classification. From an agent point of view it might be different, but I
think that it's a mistake to reduce operations with Web Services to
agent/service interactions, excluding the user from the loop, at least at
the moment. Thus making the profile a bit more user friendly by adding some
constructs that can help separate service capabilities from goals can be
beneficial to an increase usage of the profile.

Regards

Charlie

Received on Monday, 24 January 2005 20:45:14 UTC