W3C home > Mailing lists > Public > www-ws@w3.org > April 2003

Re: conditional inputs

From: David Martin <martin@ai.sri.com>
Date: Thu, 10 Apr 2003 07:05:55 -0700
Message-ID: <3E957A43.A9733AD6@ai.sri.com>
To: Debbie Richards <richards@ics.mq.edu.au>
CC: www-ws@w3.org

The specification of whether an input is mandatory or optional is done using
cardinality restrictions, as provided by DAML+OIL (and also by OWL).
Specifying an exact cardinality of 1 (or some bigger number, for that matter)
indicates that it's mandatory.  In this code sample from CongoProcess.daml,
the bookName input of the LocateBook process is specified in this way:

<daml:Class rdf:ID="LocateBook">
  <rdfs:subClassOf rdf:resource="&process;#AtomicProcess"/>
  <rdfs:subClassOf>
    <daml:Restriction daml:cardinality="1">
      <daml:onProperty rdf:resource="#bookName"/>
    </daml:Restriction>
  </rdfs:subClassOf>
</daml:Class>

If there's no cardinality stated for an input property, it is optional.

Regards,
David Martin

Debbie Richards wrote:

> Hi,
>
> In [1] it is stated that "inputs can be mandatory or optional" (p359).
> Could you please explain how this is supported by DAML-S as I can't find
> any examples, discussion or description in the upper level ontologies.
>
> thanks
>
> Debbie Richards
>
> [1] The DAML Services Coalition: Anupriya Ankolekar, Mark Burstein, Jerry
> R. Hobbs, Ora Lassila, David L. Martin, Drew McDermott, Sheila A.
> McIlraith, Srini Narayanan, Massimo Paolucci, Terry R. Payne and Katia
> Sycara.  "DAML-S: Web Service Description for the Semantic Web." In The
> First International Semantic Web Conference (ISWC), 2002.
Received on Thursday, 10 April 2003 10:04:59 GMT

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