- From: Arthur Ryman <ryman@ca.ibm.com>
- Date: Mon, 22 Mar 2004 13:51:29 -0500
- To: <paul.downey@bt.com>
- Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
- Message-ID: <OF735EAFB3.44BC1839-ON85256E5F.0066C0EC-85256E5F.006796AD@ca.ibm.com>
Paul, There are things in WSDL 2.0 that cannot be expressed in WSDL 1.1, e.g. interface inheritance. However, it is probably feasible to imbed WSDL 1.1 into WSDL 2.0, although you may have to invent some extensions (e.g. for SOAP encoding). Arthur Ryman, Rational Desktop Tools Development phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063 intranet: http://w3.torolab.ibm.com/DEAB/ <paul.downey@bt.com> Sent by: www-ws-desc-request@w3.org 03/22/2004 11:23 AM To <www-ws-desc@w3.org> cc Subject WSDL 1.1 to WSDL 2.0 mapping one of the more difficult questions i'm being asked at the moment is how we will migrate from our WSDL 1.1 documents into WSDL 2.0 when it arrives. This task would be vastly simplified if there was a standard mapping between the two languages, with an indication of which WSDL 1.1 features cannot be expressed in WSDL 1.1 and vice-versa. Given we now have a nice component model for WSDL 2.0, is it feasible to provided WSDL 1.1 serialisation and deserialisation for WSDL 2.0 ? If so, could this be written up as a W3C note under this WG ? Paul -- Paul Sumner Downey Web Services Integration BT Exact
Received on Monday, 22 March 2004 13:52:05 UTC