- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Thu, 12 May 2005 14:03:19 -0700
- To: "David Orchard" <dorchard@bea.com>, "Roberto Chinnici" <Roberto.Chinnici@Sun.COM>
- Cc: <public-ws-desc-comments@w3.org>
- Message-ID: <7DA77BF2392448449D094BCEF67569A50784D73C@RED-MSG-30.redmond.corp.microsoft.com>
Thank you for your comment, tracked as LC54 [1]. There was insufficient interest in pursuing this functionality at this time, and felt our extension mechanisms would be sufficient. If we don't hear from you within two weeks, we'll assume this resolution is satisfactory. [1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC54 ________________________________ From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-comments-request@w3.org] On Behalf Of David Orchard Sent: Wednesday, September 29, 2004 11:35 AM To: public-ws-desc-comments@w3.org Cc: Roberto Chinnici Subject: WSDL Last Call issue Last Call issue: WSDL 2.0 does not have a mechanism for a WSDL receiver to determine if a new interface that extends another interface is compatible or incompatible with the original interface. Proposed solution WSDL interface extends attribute is split to 2 attributes, extends and imports. A new interface that is compatible with another interface may use the "extends" attribute. Compatibility means that a requesting agent using the original interface can successfully use the derived interface as if it were the original interface. The definition of "extends" is along the lines of "lists the interfaces that this interface compatibly derives from". A new interface that is incompatible with another interface must use the "imports" attribute. The definition of "imports" is along the lines of "lists the interfaces that this interface uses but are not compatible with". A new component property called "imported interfaces" is introduced. Cheers, Dave Orchard & Roberto Chinnici
Received on Thursday, 12 May 2005 21:03:37 UTC