W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > May 2005

RE: Extension Components are not Described

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Fri, 20 May 2005 20:43:08 -0700
Message-ID: <7DA77BF2392448449D094BCEF67569A5079E99B3@RED-MSG-30.redmond.corp.microsoft.com>
To: "Arthur Ryman" <ryman@ca.ibm.com>, <public-ws-desc-comments@w3.org>
Thank you for your comment - we tracked this as a Last Call comment LC80
[1].  The Working Group declined to make any changes to the spec as a
result, not seeing compelling value in an architected solution for
component extensions.  If we don't hear otherwise within two weeks, we
will assume this satisfies your concern.

 

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC80

 

________________________________

From: public-ws-desc-comments-request@w3.org
[mailto:public-ws-desc-comments-request@w3.org] On Behalf Of Arthur
Ryman
Sent: Thursday, November 11, 2004 2:44 PM
To: public-ws-desc-comments@w3.org
Subject: Extension Components are not Described

 


Part 1 mentions Extension components, but does not descibe them in any
detail. For example, they are mentioned in the Operation Name Mapping
Requirement [1] and in the Component URI References [2]. If Extension
components are important, they should be defined. For example, I'd
expect that they at least have a QName. 

[1]
http://www.w3.org/TR/2004/WD-wsdl20-20040803/#Interface_OperationName 
[2] http://www.w3.org/TR/2004/WD-wsdl20-20040803/#extension-elements 

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, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/
Received on Saturday, 21 May 2005 03:43:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:31 GMT