W3C home > Mailing lists > Public > public-sws-ig@w3.org > February 2005

Representation of SWRL expressions in OWL-S

From: Daniel Elenius <elenius@csl.sri.com>
Date: Wed, 02 Feb 2005 11:03:13 -0800
Message-ID: <420123F1.1010209@csl.sri.com>
To: "daml-process@bbn.com" <daml-process@bbn.com>
CC: public-sws-ig@w3.org

In the OWL-S examples, we have SWRL-expressions such as

    <expr:SWRL-Condition rdf:ID="ExpressCongoBuyAcctExists">
      <rdfs:label>hasAcctID(ExpressCongoBuySignInInfo, ExpressCongoBuyAcctID)</rdfs:label>
      <expr:expressionLanguage rdf:resource="&expr;#SWRL"/>
        <expr:expressionBody rdf:parseType="Literal">
                <swrlx:propertyPredicate rdf:resource="#hasAcctID"/>
                <swrlx:argument1 rdf:resource="#ExpressCongoBuySignInInfo"/>
                <swrlx:argument2 rdf:resource="#ExpressCongoBuyAcctID"/>
            <rdf:rest rdf:resource="&rdf;#nil"/>

I have two concerns about this format:

1) Aren't all SWRL expressions supposed to be instances of the 
http://www.daml.org/rules/proposal/swrl.owl#Imp class? I know that this was the case in an intermediate
version of OWL-S, but this version does not seem to be available anymore. Expressions were rules with
empty heads (bodies?).

2) If this is not the case, i.e. we can use constructs from SWRL as we feel like it, then why do we have
an AtomList in the example above, where there is only one Atom? (The same occurs all over BravoAirProcess.owl
and CongoProcess.owl). We could just put the IndividualPropertyAtom directly under expressionBody.

And some bugs in the expressions:

3) In BravoAirProcess.owl, swrl expressions refer to #hasFlightItinerary, but this
property is never declared. In CongoProcess.owl, there is a reference to an undeclared #creditNumber
property (should be #cardNumber I think).

Received on Wednesday, 2 February 2005 19:03:19 UTC

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