- From: Daniela CLARO <Daniela.CLARO@eseo.fr>
- Date: Wed, 26 Apr 2006 10:10:59 +0200
- To: <public-sws-ig@w3.org>
Hi Xuan, > > One more question is about the relationship between dynamic > service composition and dynamic service invocation. If the > purpose of dynamic service composition is for dynamic service > invocation, given the example of retrieving an aerial photo > from Microsoft's Terraservice, how such dynamic composition > will enable the dynamic invocation? For me, one think is dynamic composition, i.e. when your goal is to construct a stair(ws1) and for this you need to supply the concrete(ws2). However the ws2 (supply concrete) you do not know yet. Thus the dynamic composition is responsible to put the ws2 in your composition to achieve the goal 'create a stair'. On the other hand, dynamic invocation, we can have already done dynamic composition, and at the moment you will execute these services w1 and w2, the w2 is offline. Thus you should find another service, with the same functionalities to replace the ws2. Thus we can have dynamic compositions and dynamic invocations or both! This is my point of view :o)! And most of the papers in planning, as I could observe, treats dynamic invocation. Actually I do not know if they treat dynamic composition also, do they? >In this case, the known > WSDL documents can be identified, thus you know the IOPEs for > this task. Yes... > I never tried the dynamic invocation in Java, but in .NET, I > know it's a difficulty to build dynamic invocation in the > traditional WSDL approach. I think dynamic invocation as people are doing, as I have read in some papers is using planning and semantic web, because how you will find other services, with the same functionalities (and probably others non-functional criteria as QoS) without semantics, it will be more difficult. Thus many approaches are using planning with semantics. The paper Template-based Composition of Semantic Web Services E. Sirin, B. Parsia, J. Hendler used a planner based on Java, the Jshop. I created a planning algorithm using a rule-based engine, called JESS. It not efficient as a planner with relaxed restrictions as a HTN, but we should start by something! JESS is completely integrated with Java. JSHOP I do not know, but the authors can say something about it! I created a dynamic composition and not a dynamic invocation. In my invocation I consider that everything works fine! Hope that helps, Daniela
Received on Wednesday, 26 April 2006 08:11:31 UTC