W3C home > Mailing lists > Public > public-sws-ig@w3.org > June 2004

[OWL-S] 2 minor additions to Grounding.owl

From: David Martin <martin@AI.SRI.COM>
Date: Tue, 15 Jun 2004 13:22:15 -0700
Message-ID: <40CF5A77.4080903@ai.sri.com>
To: public-sws-ig <public-sws-ig@w3.org>

Here are 2 new property declarations I'm planning to insert into 
Grounding.owl.  They are very simple, and I expect them to be 
noncontroversial.  They arose out of some requirements related to the 
"Semantic BPEL" project (that's probably not the correct name) of Sheila 
McIlraith and Dan Mandell.  Their purpose is simply to allow for more 
precise identification of a WSDL Port (or set of Ports) that may be used 
with an OWL-S atomic process.

Comments welcome.

-- David

<!-- wsdlService -->

<owl:DatatypeProperty rdf:ID="wsdlService">
   <rdfs:comment>
     A URI for a WSDL Service that provides the operation to which this
atomic process
     is grounded.
   </rdfs:comment>
   <rdfs:domain rdf:resource="#WsdlAtomicProcessGrounding"/>
   <rdfs:range rdf:resource="&xsd;#anyURI"/>
</owl:DatatypeProperty>

<!-- wsdlPort -->

<owl:DatatypeProperty rdf:ID="wsdlPort">
   <rdfs:comment>
     A URI for a WSDL Port that provides the operation to which this
atomic process
     is grounded.
   </rdfs:comment>
   <rdfs:domain rdf:resource="#WsdlAtomicProcessGrounding"/>
   <rdfs:range rdf:resource="&xsd;#anyURI"/>
</owl:DatatypeProperty>

=====

Notes on Properties of WsdlAtomicProcessGrounding

Each instance of WsdlAtomicProcessGrounding must have exactly one value
for owlsProcess and exactly one for wsdlOperation, which sets up a
one-to-one correspondence between an atomic process and a WSDL operation.

In addition, for each message part of the relevant WSDL input message,
there must be exactly one value of wsdlInput.  For each output of the
atomic process, there must be exactly one value of wsdlOutput. These
property instances show the correspondences between OWL-S inputs/outputs
and WSDL message parts.  In addition, single values are recommended (but
not required) for wsdlInputMessage and wsdlOutputMessage.

Note that the value of wsdlOperation may or may not uniquely identify a
particular WSDL port with which to interact.  If there are multiple such
ports offering the specified operation, an OWL-S enactment engine is
free to choose any of these ports.
If it is desired to further constrain the choice of ports, a
WsdlAtomicProcessGrounding may do so by specifying any number of values
for wsdlService and/or wsdlPort.
Received on Tuesday, 15 June 2004 16:20:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:54:13 UTC