- From: Bijan Parsia <bparsia@isr.umd.edu>
- Date: Fri, 3 Dec 2004 07:58:53 +0900
- To: Paul Libbrecht <paul@activemath.org>
- Cc: public-sws-ig@w3.org, Naveen Srinivasan <naveen@cs.cmu.edu>
On Dec 3, 2004, at 12:53 AM, Paul Libbrecht wrote: > Le 2 déc. 04, à 16:34, Bijan Parsia a écrit : > >>> I am all but an expert but isn't this somewhat simplistic to use all >>> these translations transparently ? >> Usually, there is some sort of augmentation or alteration done at >> each level. Well, java2wsdl is usually transparent *except* in so far >> as you might want to specify alternative bindings (which is >> significant!). When going form WSDL2OWL-S, you *at least* want to add >> to the profile something about the type, constraints, and capabilties >> of the service. So you've added informaton! Actually, it's similar to >> what you might add when creating a UDDI entry. > > But isn't augmentation and alteration at each level, precisely against > the goals of this development environment ? No. From their paper: "Once the code is generated, the developer generates the WSDL description of the Web service with the support of Apache’s Java2WSDL 5 and the OWL-S description with the support of WSDL2OWLS 6. The results of this process are a complete WSDL, OWL-S Grounding descriptions, and a skeletal OWL-S Process Model and Profile. While WSDL2OWL-S greatly facilitates the developer activities, many aspects of the description are left to be complited. Specifically, the developer needs to add control flow and data flow information as well as to complete the Profile non-functional parameters." I would add also that type augmentation also often happens (mistakenly, in my view, but it does). Cheers, Bijan Parsia.
Received on Thursday, 2 December 2004 23:00:37 UTC