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

problems parsing CongoProcess.owl

From: Dan Connolly <connolly@w3.org>
Date: Mon, 29 Mar 2004 09:10:52 -0600
To: public-sws-ig@w3.org
Message-Id: <1080573051.2470.1734.camel@dirk>

I was looking at the OWL-S examples, and I'm pretty
sure I found a bug in

   465    <process:hasInput>
   466      <process:Input rdf:ID="CongoBuyBookCreditCardNumber">
   467        <process:parameterType rdf:resource="#&xsd;#string"/>
   468      </process:Input>
   469    </process:hasInput>

I'm pretty sure that should be:

   467        <process:parameterType rdf:resource="&xsd;#string"/>

Hmm... after I fixed that, I'm still having trouble. This
isn't rdf-grammatical:

   342      <process:Sequence>
   343        <process:components rdf:parseType="Collection">
   344                                          <process:AtomicProcess
<process:CompositeProcess rdf:resource="#CongoBuyBook"/>
   346        </process:components>
   347      </process:Sequence>

I'm not sure what you meant.
If anybody has tools that work on OWL-S documents and some
OWL-S documents they work on, please point me/us at them.

fyi, notes:

Dan Connolly, W3C http://www.w3.org/People/Connolly/
see you at the WWW2004 in NY 17-22 May?
Received on Monday, 29 March 2004 10:10:46 UTC

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