[owl-s] OWL-S API and Document/Literal (wrapped) support

Chris Parish chris.parish at oxfordcc.co.uk
Wed Jan 18 05:14:35 EST 2006


Ronald,

I am managing to call document/literal style web services, but I think it
may get a bit confused with message "parts".

I have a WSDL operation defined by the following:

<wsdl:operation name="NHSABtoNHS" parameterOrder="NHSABtoNHS">
	<wsdl:input message="NHSABtoNHSRequest" name="NHSABtoNHSRequest" />
	<wsdl:output message="NHSABtoNHSResponse" name="NHSABtoNHSResponse" />
</wsdl:operation>

...

<wsdl:message name="NHSABtoNHSRequest">
  	<wsdl:part element="NHSABtoNHS" name="NHSABtoNHS" />
</wsdl:message>

...

<wsdl:types>
	...
	<element name="NHSABtoNHS">
		<complexType>
			<sequence>
				<element maxOccurs="1" minOccurs="0" name="NHSA" type="xsd:string" />
				<element maxOccurs="1" minOccurs="0" name="NHSB" type="xsd:string" />
			</sequence>
		</complexType>
	</element>
	...
</wsdl:types>

Now, my understanding is that the input of this operation has a single
"part" called "NHSABtoNHS", but the OWL-S API seems to treat this case as
having 2 message parts NHSA and NHSB, ie. the first level of element names.

In calling this service I have defined the following grounding in the OWL-S.
Note also that I think the namespace defined in the wsdlMessagePart below
gets ignored and just the local name gets used.

	<grounding:WsdlGrounding rdf:ID="Grounding_NHSABtoNHS">
		<service:supportedBy
rdf:resource="#Service_NHSABtoNHS"></service:supportedBy>
		<grounding:hasAtomicProcessGrounding
rdf:resource="#ProcessGrounding_NHSABtoNHS"></grounding:hasAtomicProcessGrou
nding>
	</grounding:WsdlGrounding>

	<grounding:WsdlAtomicProcessGrounding rdf:ID="ProcessGrounding_NHSABtoNHS">
		<grounding:wsdlInputMessage
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/NHSABtoNHSRequest</grounding:wsdlInputMess
age>
		<grounding:wsdlOutputMessage
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/NHSABtoNHSResponse</grounding:wsdlOutputMe
ssage>
		<grounding:wsdlDocument
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://localhost:8080
/axis/services/BPELExecutionPlanTestServiceSoap?wsdl</grounding:wsdlDocument
>
		<grounding:owlsProcess
rdf:resource="#Process_NHSABtoNHS"></grounding:owlsProcess>
		<grounding:wsdlInput rdf:resource="#Input_NHSA"></grounding:wsdlInput>
		<grounding:wsdlInput rdf:resource="#Input_NHSB"></grounding:wsdlInput>
		<grounding:wsdlOutput rdf:resource="#Output_NHS"></grounding:wsdlOutput>
		<grounding:wsdlOperation
rdf:resource="#Operation_NHSABtoNHS"></grounding:wsdlOperation>
	</grounding:WsdlAtomicProcessGrounding>

	<grounding:WsdlOperationRef rdf:ID="Operation_NHSABtoNHS">
		<grounding:operation
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/NHSABtoNHS</grounding:operation>
		<grounding:portType
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/BPELExecutionPlanTestServiceSoap</groundin
g:portType>
	</grounding:WsdlOperationRef>

	<grounding:WsdlInputMessageMap rdf:ID="Input_NHSA">
		<grounding:wsdlMessagePart
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/NHSA</grounding:wsdlMessagePart>
		<grounding:owlsParameter rdf:resource="#NHSA"></grounding:owlsParameter>
	</grounding:WsdlInputMessageMap>

	<grounding:WsdlInputMessageMap rdf:ID="Input_NHSB">
		<grounding:wsdlMessagePart
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/NHSB</grounding:wsdlMessagePart>
		<grounding:owlsParameter rdf:resource="#NHSB"></grounding:owlsParameter>
	</grounding:WsdlInputMessageMap>

	<grounding:WsdlOutputMessageMap rdf:ID="Output_NHS">
		<grounding:owlsParameter rdf:resource="#NHS"></grounding:owlsParameter>
		<grounding:wsdlMessagePart
rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.oxfordcc.c
o.uk/BPELExecutionPlanTestService/NHSABtoNHSResult</grounding:wsdlMessagePar
t>
	</grounding:WsdlOutputMessageMap>

Any further comments on this would be welcome, since I am not convinced that
the OWL-S API is currently handling these inputs in the correct manner.

Chris

-----Original Message-----
From: owl-s-bounces at lists.mindswap.org
[mailto:owl-s-bounces at lists.mindswap.org]On Behalf Of Ronald Kutschke
Sent: 17 January 2006 15:37
To: owl-s at lists.mindswap.org
Subject: [owl-s] OWL-S API and Document/Literal (wrapped) support



Dear all,

does the owl-s api support the wsdl style/use document/literal (wrapped)?

I grounded a document/literal wsdl and tried to execute it but the api
wants to sent rpc/encoded soap responses to the soap endpoint (which of
course fails).

I also tried to use xslt but it doesn't work. It just ignores the xsl
commands.


thanks for your help
regards ronald
_______________________________________________
OWL-S mailing list
OWL-S at lists.mindswap.org
http://lists.mindswap.org/mailman/listinfo/owl-s


..................................................................................................

This message and any attachments may contain OCC confidential
or proprietary information. If you are an unintended recipient: 

(i) immediately delete the information contained herein and contact the author; and 
(ii) do not disclose, distribute, or duplicate any information from this message or any 
of its attachments.




More information about the OWL-S mailing list