]> $Id: Grounding.owl,v 1.38 2006/01/04 21:41:56 martin Exp $ Upper-level OWL ontology for Groundings that employ WSDL. Part of the OWL-S ontology; see http://www.daml.org/services/. This version is intended for use with WSDL 1.1. The OWL-S Coalition plans to produce a future version for use with WSDL 2.0, when it has been finalized (or nearly so). Note that other approaches to grounding may be accommodated within the OWL-S framework. This is the only approach produced to date by the OWL-S Coalition. For notes on version history, see http://www.daml.org/services/owl-s/1.2/status.html. A Grounding is just a collection of AtomicProcessGrounding instances, one for each atomic process in the process model. A class that relates elements of a OWL-S atomic process to a WSDL specification. Each instance of AtomicProcessGrounding must have exactly one value for owlsProcess. Rest of the AtomicProcessGrounding depends on the specifics of the grounding type. 1 The atomic process to which this grounding applies. A class used to map parameters in OWL-S to the parameters in the grounded operation. owlsParamater property is used to specify the OWL-S parameter. An input or output property of an atomic process. A MessageMap that maps inputs to grounding specification A MessageMap that maps outputs to grounding specification WsdlGrounding is A Grounding that grounds every process to a WSDL operation. A class that relates elements of a OWL-S atomic process to a WSDL specification. 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. 1 A WSDL operation to which the atomic process (referenced by owlsProcess) corresponds. A URI for a WSDL Service that provides the operation to which this atomic process is grounded. A URI for a WSDL Port that provides the operation to which this atomic process is grounded. A URI for the WSDL input message element corresponding to the inputs of the atomic process. There should be one instance of this property for each message part of the WSDL input message. A URI for the WSDL message element corresponding to the outputs of the atomic process. There should be one instance of this property for each output of the atomic process. A URI indicating the version of WSDL being used. A URI indicating a WSDL document to which this grounding refers. This isn't essential; primarily for convenience as documentation. This class provides a unique specification of a WSDL operation. WSDL 1.1, on which this version of the grounding is based, does not have a way to uniquely identify an operation with a single URI. Uniqueness is achieved using a pair (portType, operation). Restricting the cardinality of portType to one 1 Restricting the cardinality of operation to one 1 MessageMap for WSDL inputs and outputs A URI for a WSDL message part element. XSLT Tranformation to transform OWL-S parameters (inputs and outputs) to and from WSDL messages. This property exists mainly for declaring a cardinality restriction, and should not be instantiated directly. Instantiate xsltTransformationString or xsltTransformationURI. (Ranges are specified with the sub properties.) A string giving an XSLT Tranformation. A URI for an XSLT Tranformation. The purpose of a WsdlInputMessageMap is to show how to derive the WSDL input message parts from the OWL-S Parameter values. There should be one WsdlInputMessageMap for each WSDL input message part. There are two different kinds of input message maps: (1) DirectInputMessageMap - This is used when we have a 1-1 mapping between Inputs in the AtomicProcess and WSDL message parts. There are two cases: (a) The parameterType of the Input is an OWL class. The OWL class is used as the message part type in the WSDL document. (Note: for this case to be fully general, further work may be needed to establish conventions for serializing arbitrary OWL instances). (b) The parameterType is an XSD simple type, and the WSDL message part has the same type. (2) XSLTInputMessageMap - This is used when the the parameterType and the WSDL message part type is not the same. The WSDL type can be either simple or complex. In this case, a WSDL message part can be derived from multiple Inputs. 1 1 0 0 1 The purpose of WsdlOutputMessageMap is to show how to derive OWL-S Parameter values from the WSDL output message parts. There should be one WsdlOutputMessageMap for each Output of the corresponding AtomicProcess. There are two kinds of output message maps, similarly to input message maps. (1) DirectOutputMessageMap - This is used when we have a 1-1 mapping between WSDL message parts and Outputs in the Atomic Process. There are two cases: (a) The parameterType of the Output is an OWL class, and the OWL class is used as the message part type in the WSDL document. (Note: for this case to be fully general, further work may be needed to establish conventions for serializing arbitrary OWL instances). (b) The parameterType is an XSD simple type, and the WSDL message part has the same type. (2) XSLTOutputMessageMap - This is used when the the parameterType and the WSDL message part type is not the same. The WSDL type can be either simple or complex. In this case, an OWL Output can be derived from multiple WSDL message parts. 1 1 0 0 1