W3C home > Mailing lists > Public > public-sws-ig@w3.org > April 2007

Re: Semantic Services

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Mon, 2 Apr 2007 04:37:52 +0100
Message-Id: <84566663-C5D9-4EEF-B48C-32EEF1CCB803@isr.umd.edu>
Cc: public-sws-ig@w3.org
To: Ivo Augusto <txithihausen@gmail.com>

On Mar 29, 2007, at 10:35 PM, Ivo Augusto wrote:

> Hello everbody...
>   I have searched about ontology to describes services, in this  
> case, OWL-S. Up to now, i have found many things about OWL-S  
> related to Semantic Web Services. Im interested about that  
> (Semantic Web Services), but it is not all. I would like to know if  
> are there another options for other technologies. Id like to know  
> if are there some ways to relate OWL-S to other kinds of services,  
> such as UPnP, Jini, and so on.

Yep, in several ways.

If you have a UPnP or Jini WSDL binding, then it's exactly the same  
as for SOAP or HTTP bindings.

You could also extend the grouding to go directly to the, e.g., UPnP.  
This was done as part of Fujitsu's task computing project:

There is code support for those groundings in the Mindswap OWL-S API:

If you dig around, you might find some example grounding files.

(e.g., I found one by googling:

(Note that there's also a grounding to direct java calls.)

> If so, what are the capacity of the interoperability among them  
> through the OWL-S, either in searches or in composition and  
> invocation of the services and if is there any API which does this  
> task. I also would like to know if are there papers about this theme!?


The OWL-S API should handle this fine. It did so for the  
TaskComputing project...you could discover, match, compose, and  
execute services with complete indifference to whether they were  
soapy or upnpy.

Received on Monday, 2 April 2007 03:38:08 UTC

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