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

Re: OWL-S API (how to make it read the work-flow)

From: Evren Sirin <evren@cs.umd.edu>
Date: Tue, 25 May 2004 23:54:06 -0400
Message-ID: <40B414DE.1000607@cs.umd.edu>
To: Jeff Dalton <jeff@inf.ed.ac.uk>
Cc: Dónal Murtagh <domurtag@cs.tcd.ie>, public-sws-ig@w3.org

Sorry, I couldn't reply to you last week while I was out of town. The 
problems about reading composite service descriptions were fixed in the 
SVN and now there is a new release of the API that contains these bug 
fixes along with more code examples and a small tutorial. There is also 
a new mailing list created (owl-s@lists.mindswap.org) for API related 
questions. The API is available under MIT license. You can find the 
license terms here: http://www.mindswap.org/2004/owl-s/api/license.shtml

Thanks,
Evren

Jeff Dalton wrote:

>Quoting Dónal Murtagh <domurtag@cs.tcd.ie>:
>
>  
>
>>Good work! I found out from the author of the API that the owl-s.jar
>>in the current release is not the most recent. I downloaded the latest
>>version from http://svn.mindswap.org/owl-s/trunk/lib/owl-s.jar and
>>that fixed the problem too.
>>    
>>
>
>Thanks; but now I'm a bit puzzled, because when I look at that
>version, it still seems to have the problem.
>
>(Mouse, mouse, mouse).  Ok, I can see what's happening now.
>
>OWLSReader_1_0 still does 
>
>   getProperty(OWLS_1_0.Process.theProperty)
>
>But in owls/vocabulary/jena/OWLS_1_0.java, theProperty
>is defined to be "theParameter":
>
>  public static Property theProperty =
>     ResourceFactory.createProperty(URI, "theParameter");
>
>(And similarly atClass is defined using "atProcess".)
>
>So it looks like a quick fix that will be tidied up later.
>
>Cheers,
>Jeff
>
>
>
>
>  
>
Received on Wednesday, 26 May 2004 00:02:09 UTC

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