- From: <ewallace@cme.nist.gov>
- Date: Tue, 2 Dec 2003 10:55:23 -0500 (EST)
- To: public-sws-ig@w3.org, www-rdf-rules@w3.org
Titi Roman <dumitru.roman@deri.ie> asserted: >...in OWL-S, a rule language should be deployed only for the reason that > it may help in describing preconditions and effects in a more comfortable > way(i.e. not having to use for example in OWL-S Profile the definitions of >"preconditions" and "effect", but rather considering the rule: > >_if a buyer has a valid Account and a valid Credit Card, then he can buy the >book_ *snip* >) or for the reason that it gives more expressivity (if yes, please explain >what this expressivity means and how it is achieved or can be achieved). The rule above only expresses preconditions and not any effects of executing the service. Thus providing no understanding of what it means to "buy the book" and illustrating less than half of what needs to be expressed by preconditions and effects. Even this just addresses the ServiceProfile bit of DAML-S. There is also a need for rules to express parts of ProcessModels in the ServiceModel component. -Evan Evan K. Wallace Manufacturing Systems Integration Division NIST
Received on Tuesday, 2 December 2003 10:55:25 UTC