RE: Operation Name Mapping Requirement Bug

Thank you for your comment, which we tracked as LC82 [1].  The WG agreed
to fix this by adopting the proposal at

If you find this resolution unacceptable please let us know within two






[] On Behalf Of Arthur
Sent: Thursday, November 11, 2004 2:44 PM
Subject: Operation Name Mapping Requirement Bug


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


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:

Received on Thursday, 9 June 2005 21:30:00 UTC