W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > November 2004

Operation Name Mapping Requirement Bug

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Thu, 11 Nov 2004 17:44:15 -0500
To: public-ws-desc-comments@w3.org
Message-ID: <OFBACAB06E.BABE45BD-ON85256F49.00793C7B-85256F49.007CE064@ca.ibm.com>
The Operation Name Mapping Requirement [1] has a bug.

Consider an interface that has two operations that both return the same 
GED output message, e.g. a Car search service that has findByColour and 
findByHorsepower operations which both return ListOfCars. Assume this 
operation uses a request-response MEP so the response is always corelated 
with the request. 

According to the ONMR, these operations are ambiguous because they have 
the same GED for their output message. The Interface component must have 
either a Feature or an Extension element component that describes how the 
sender is enabling the recipient to distinguish the messages.

This is a spec bug since in this case there is no ambiguity on the input 
messages. The requirement text needs to be corrected to restrict the case 
where the ONMR applies. Also, even those the output messages are the same, 
there is no amibuity since the output is corelated with the input.

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

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 Thursday, 11 November 2004 22:44:30 GMT

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