RE: Message Reference Component is Underspecified

Thank you for your comment - we tracked this as a Last Call comment
LC105 [1].  The Working Group agreed to add the value "#other" to the
component model and the schema.

 

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#LC105

 

 

 

________________________________

From: public-ws-desc-comments-request@w3.org
[mailto:public-ws-desc-comments-request@w3.org] On Behalf Of Arthur
Ryman
Sent: Sunday, January 09, 2005 1:11 PM
To: public-ws-desc-comments@w3.org
Cc: Vlad Klicnik
Subject: Message Reference Component is Underspecified

 


The Message Reference Component description [1] doesn't define the
semantics of the message when the optional {message content model}
property is absent. 

If the property is absent is that the same as #any? 

[1] http://www.w3.org/TR/2004/WD-wsdl20-20040803/#MessageReference 

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/