W3C home > Mailing lists > Public > www-ws@w3.org > June 2004

Re: OWL-S process preconditions

From: Donal Murtagh <domurtag@cs.tcd.ie>
Date: Sat, 19 Jun 2004 14:33:49 +0100
Message-ID: <1087652029.40d440bdc3557@mymail.tcd.ie>
To: www-ws@w3.org, public-sws-ig@w3.org

> The current frontrunner is to represent conditions as literals, either
> XML literals or some other kind.  An attribute of a condition is its
> logical language.  Example:
> 
>    <owls:AtomicProcess>
>       <owls:hasPrecondition>
> 	<owls:Expression expressionLanguage="&swrl;#SWRL"
> 	                 rdf:parseType="Literal">
>            <ruleml:body rdf:parseType="Collection">
> 	      <swrl:individualPropertyAtom>
> 		 <swrl:propertyPredicate rdf:resource="creditCardAuth"/>
> 		 <swrl:argument1 rdf:resource="#cc"/>
> 		 <swrl:argument2 
rdf:datatype="&xsd;#string">Yes</swrl:argument2>
> 	      </swrl:individualPropertyAtom>
>            </ruleml:body rdf:parseType="Collection">
> 	</owls:Expression>
>       </owls:hasPrecondition>
>    </owls:AtomicProcess>
> 
> The reason to use literals is to "hide" the RDF from the main RDF
> parser.  What a knowledgeable Owl-S parser must actually do is
> re-parse the hidden RDF chunks later, when it's possible to do
> appropriate substitutions.  In the example above, the
> individualPropertyAtom is not really about the variable "#cc"; it's
> about the _value_ of that variable in some context.  When that value
> is available, the RDF can be reprocessed to yield a statement about
> the authorization status of that credit card.

If I understand your example correctly, it's equivalent to:
creditCardAuth(?cc, Yes)

Incidentally, should this atom be a Datavalued Property Atom, as the range is a 
data value?

Cheers,
Dónal
Received on Saturday, 19 June 2004 09:34:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:45 GMT