- From: jean-michel nougayrede <nougay_j@epita.fr>
- Date: Thu, 9 Sep 2004 15:33:15 +0200
- To: <public-sws-ig@w3.org>
> > For example there is a web service A which sells a product P and > > then connect to another web service B in order to ship the product P. > > But the web service A doesn't know the web service B which can do > > the shipping. The web service A searches on the web in order to find > > one, and when it finds one, it uses it. > > But the problem is that the web service A doesn't know what are the > > functions to be called and with which arguments and in which order. > > It would make sense to use the WDSL description of the service. > I don't understand how we can automatize an execution of a web service with a WSDL description because I don't understand how a web service can understand a WSDL file. For example let's see this sample of WSDL: <message name="getCoursInput"> <part name="nomEntreprise" type="xsd:string" /> </message> <message name="getCoursOutput"> <part name="coursAction" type="xsd:float" /> </message> <portType name="BoursePortType"> <operation name="getCours"> <input message="getCoursInput" /> <output message="getCoursOutput" /> </operation> </portType> How a ws can know how to use the operation "getCours", which parameter to provide and the meaning of this operation? > > Must web services share the same language (in our case all the web > > services for the shipping have the same function and argument)? > > They don't need to use the same description (wsdl file) to be usable. > But in the search part of the problem, you can assume that they will > share some ontology. > What do you mean by ontology? Is it a common set of terms between two business entities? Thanks. Jean-Michel.
Received on Thursday, 9 September 2004 13:33:25 UTC