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

Re: ExpressCongoBuy atomic service description

From: David Martin <martin@AI.SRI.COM>
Date: Tue, 04 Mar 2003 12:47:30 -0800
Message-ID: <3E6510E2.827F04CA@ai.sri.com>
To: Mithun Sheshagiri <mits1@cs.umbc.edu>
CC: www-ws@w3.org

Sheila and Mithun -

You are both right.  That is, as Sheila says, we deliberately did not specify a domain for
congoOrderShippedEffect, so that it could potentially be used with multiple different processes.
Of course the domain is implicitly "Process", because it's a subproperty of effect.  Similarly
for congoOrderShippedOutput.

However, it it also true that there is currently nothing that indicates which processes it should
be used with.  This could be done by specifying a restriction on the property that's associated
with ExpressCongoBuy.  For instance a cardinality restriction could be used:

<daml:Class rdf:ID="ExpressCongoBuy">
    ....
     <rdfs:subClassOf>
        <daml:Restriction daml:maxCardinality="1">
        <daml:onProperty rdf:resource="#congoOrderShippedEffect"/>
    </daml:Restriction>
    ....

Regards,
David Martin

Mithun Sheshagiri wrote:

> Hello Sheila,
>                        Thank you for the reply. I am still wondering how
> do I bind a particular I/P/O/E to a service if the domain is not
> specified. Since congoOrderShippedEffect is a part of ExpressCongo,
> don't we have to bind these somewhere. At what stage should this be
> happening?
>
> peace,
> mithun
>
> sam@KSL.Stanford.EDU wrote:
>
> >Hi Mithun,
> >
> >Thanks for your question about ExpressCongoBuy.  As you noted,
> >we did not explicitly define a domain for the properties
> >property:congoOrderShippedEffect
> >and
> >property:congoOrderShippedOutput.
> >This was done on purpose.  It certainly would not have been
> >incorrect to have defined a domain, but it was not necessary.
> >The advantage of not explicitly defining a domain is that it
> >enables these properties to be used by multiple processes.
> >For example, the non-express version of CongoBuy could have the
> >same conditional outputs and effects.  By not defining the domain
> >explicitly, it enables the use of the properties in the definition
> >of both processses.
> >
> >Hope this helps.
> >
> >Sheila
> >
> >
> >==============================================================================
> >
> >Sheila McIlraith, PhD                 Phone: 650-723-7932
> >Senior Research Scientist             Fax:  650-725-5850
> >Knowledge Systems Lab
> >Department of Computer Science
> >Gates Sciences Building, 2A-248       http://www.ksl.stanford.edu/people/sam
> >Stanford University                   E-mail sam@ksl.stanford.edu
> >Stanford, CA 94305-9020
> >
> >
> >
> >
> >       Hi All,
> >                    I need some clarification regarding the description of
> >       ExpressCongoBuy atomic service which is part of the ProcessModel
> >       described by the file
> >       <http://www.daml.org/services/daml-s/0.7/CongoProcess.daml>.
> >       Is property:congoOrderShippedEffect part of the ExpressCongoBuy service?
> >       If the answer is yes, shouldn't  it have a domain pointing to the
> >       ExpressCongoBuy class.
> >
> >       - <daml:Property rdf:ID="congoOrderShippedEffect">
> >         <rdfs:subPropertyOf
> >       rdf:resource="http://www.daml.org/services/daml-s/0.7/Process.daml#effect"
> >       />
> >       - <rdfs:range>
> >       - <daml:Class>
> >         <rdfs:subClassOf
> >       rdf:resource="http://www.daml.org/services/daml-s/0.7/Process.daml#ConditionalEffect"
> >       />
> >       - <rdfs:subClassOf>
> >       - <daml:Restriction>
> >         <daml:onProperty
> >       rdf:resource="http://www.daml.org/services/daml-s/0.7/Process.daml#ceCondition"
> >       />
> >         <daml:toClass rdf:resource="#BookInStock" />
> >         </daml:Restriction>
> >         </rdfs:subClassOf>
> >       - <rdfs:subClassOf>
> >       - <daml:Restriction>
> >         <daml:onProperty
> >       rdf:resource="http://www.daml.org/services/daml-s/0.7/Process.daml#ceEffect"
> >       />
> >         <daml:toClass rdf:resource="#OrderShippedEffect" />
> >         </daml:Restriction>
> >         </rdfs:subClassOf>
> >         </daml:Class>
> >         </rdfs:range>
> >         </daml:Property>
> >
> >       Similarly shouldn't the output: congOrderShippedOutput have a domian as
> >       well. Am I missing something?
> >
> >       peace,
> >       mithun
> >
> >
> >
> >
> >
Received on Tuesday, 4 March 2003 15:47:19 GMT

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