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

RE: The Component Model is Underconstrained wrt the WSDL 2.0 Schema

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Fri, 20 May 2005 20:43:10 -0700
Message-ID: <7DA77BF2392448449D094BCEF67569A5079E99B4@RED-MSG-30.redmond.corp.microsoft.com>
To: "Arthur Ryman" <ryman@ca.ibm.com>
Cc: <public-ws-desc-comments@w3.org>
Thank you for your comment - we tracked this as a Last Call comment LC81
[1].  The Working Group agreed to add statements constraining the
component model to ensure a legal component model instance can always be
serialized as a WSDL 2.0 document.  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#LC81

 

 

________________________________

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: The Component Model is Underconstrained wrt the WSDL 2.0 Schema

 


As written, the Component Model is missing constraints that enable
typical instances of the Component Model to be represented as WSDL 2.0
documents. This problem is over and above the differences in the
character sets and name values allowed by the Component Model versus
XML. 

For example, consider and Interface that extends no other Interfaces and
that contains a single Operation. Both the Interface and the Operation
have a QName. However, the Component Model does not constrain their
namespace names to be equal, as would be the case if the Component Model
instance came from a WSDL 2.0 document. 

I think there is no value in making the Component Model much more
general than what can be expressed in WSDL 2.0 documents (except for the
character issues). 

I recommend that the Component Model be tightened up to allow its
instances to be represented by WSDL 2.0 documents, except when prevented
by differences in character sets and name value spaces. (BTW, I am
unconvinced that allowing any exceptions is very valuable.) 

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:17 GMT

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