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

RE: Relation between OWL and OWL-S

From: Daniela CLARO <daniela.claro@eseo.fr>
Date: Thu, 25 Nov 2004 10:19:06 +0100
To: <public-sws-ig@w3.org>
Message-Id: <20041125091909.E9C2F14DF@harley.eseo.fr>

Thank you Drew, for your answer, and I really apologize my mistake using the
word “bank”, but fortunately you have understood my doubt. 

Concerning your questions...

>Q2: How does one deal with the ambiguity of words in HCI for web services?

>Good question, also asked by Charlie Abela.

This is actually one of my doubts, and I remember Charlie’s thread in this
list, and I also increased his question putting my point of views and also
my doubts concerning the ambiguity.   

>Q3: Must we do without Owl mechanisms such as inheritance when we use
Owl-S?  
>The answer is No!  Owl-S is an _application_ of Owl, and doesn't replace a 
>hair on its pointy little head.
About this Q3, I know that OWL-S is an OWL application, but actually my
doubt is how can I differentiate two individuals (services) like river bank
and economical bank in OWL-S? I think that this question is the same as Q2.



>Q4: Is there a problem with multiple inheritance if an agent is both a 
>service _and_ an "economical entity"?  I don't know, but I don't see why 
>there would be a problem.
Here I do not understand very well, neither I think that isn’t one doubt of
mine.  

Thus my question is how can I differentiate two individuals (services) like
river bank and economical bank in OWL-S? Actually how can I differentiate
two ambiguous individuals (services) in OWL-S? 

Thank you very much for your patience,
Daniela
 

-----Message d'origine-----
De : public-sws-ig-request@w3.org [mailto:public-sws-ig-request@w3.org] De
la part de Drew McDermott
Envoyé : mercredi 24 novembre 2004 15:24
À : public-sws-ig@w3.org
Objet : Re: Relation between OWL and OWL-S

> [Daniela CLARO]
> 
> If I have a web service called bank, what will I use to discover this 
> service?
> -My answer: I will use the description in the profile and also the 
> input > and output parameters
> 
> But if I have another service called bank, so how will I make the 
> differe> nce between them? Suppose that the first one refers to 
> economical bank and th> e second one is a wood bank for sitting on.
> 
> In OWL is clear that we can make this difference between the 
> hierarchical view proposed, so the economical bank will be localised 
> under economical tranche and wood bank will be localised under wood 
> section like my model
> below:
> 
> 		     ...
> 		 _____|_____
> 		|           | 
>   	  economical     wood
>             |           |
>            bank        bank
> 
> Using that model in OWL we can make this distinction, and how can I do 
> th> e same thing to discover a service in OWLS.
> 
> If I have a service called bank, how can I make this distinction?

It's hard to answer your question, because it mushes together several
distinct questions.  Let me try to separate them --

Q1: How does one avoid the ambiguity between different senses of the word
"bank" in the innards of ontologies?  The answer would be namespaces.  (By
the way, the banks you sit on are only banks in Italian; in English they are
"benches," which comes from the Italian, but conveniently changed spelling,
thus eliminating the confusion.  To compensate, the earthen walls of rivers
are called "banks," so if we have a web service selling tours of river
margins, the confusion is
restored.)

Q2: How does one deal with the ambiguity of words in HCI for web services?
Good question, also asked by Charlie Abela.

Q3: Must we do without Owl mechanisms such as inheritance when we use Owl-S?
The answer is No!  Owl-S is an _application_ of Owl, and doesn't replace a
hair on its pointy little head.

Q4: Is there a problem with multiple inheritance if an agent is both a
service _and_ an "economical entity"?  I don't know, but I don't see why
there would be a problem.

Does any of these alternative questions come close to what you intended?  

-- 

                                         -- Drew McDermott
                                            Yale University
                                            Computer Science Department
Received on Thursday, 25 November 2004 09:19:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 16 March 2008 00:10:58 GMT