- From: Evren Sirin <evren@cs.umd.edu>
- Date: Mon, 20 Dec 2004 23:42:14 -0500
- To: Tatiana Vieira <tascvieira@yahoo.com.br>
- CC: public-sws-ig@w3.org
Hi Tatiana, The "instantiation" of Parameter class is not related to the execution of processes. It is related to the OWL individuals found in the OWL-S descriptions. It simply says that we don't expect anybody to create a "direct" instance of Parameter class, i.e. having only one type assertion for a parameter like this: <process:Parameter rdf:ID="someParam"> In your OWL-S description, it is expected (though not mandatory) that you will explicitly say that a parameter is an input or output, i.e. by saying <process:Input rdf:ID="someParam"> OR <process:Output rdf:ID="someParam"> There are also different subclasses of Parameter class defined in OWL-S 1.1, such as Local and ResultVar, which you might use. Of course you can also extend the OWL-S ontologies to define your own subclasses of the Parameter class. Regards, Evren Tatiana Vieira wrote: > Hi people, > In the "OWL-S: Semantic Markup for Web Services" document, > Section 4.2.3, when there is a description about "hasParameter", we > found the following sentence: "...we do not expect this class to be > instantiated. It's role is solely making domain knowledge explicit". > What does it mean? What happens when a process is executed: does it > create an instance of each output parameter class? > Thank you in advance, > Tatiana. > > __________________________________________________ > Converse com seus amigos em tempo real com o Yahoo! Messenger > http://br.download.yahoo.com/messenger/ >
Received on Tuesday, 21 December 2004 04:42:42 UTC