RE: Proposal for Assertion InterfaceMessageReference-0042

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

RE: Proposal for Assertion InterfaceMessageReference-0042

Jonathan Marsh-2

Thank you for this issue.  We tracked it as Issue 4380 [1] in our short Last Call period.  The Working Group closed it without action as the specification of a uniqueness constraint would prevent the attribute from being optional as it is now.

 

The spec should be in Proposed Recommendation shortly, if you disagree with the resolution of this issue please inform us as soon as possible.

 

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4380

 

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Ramkumar Menon
Sent: Thursday, February 15, 2007 2:06 PM
To: [hidden email]
Subject: Proposal for Assertion InterfaceMessageReference-0042

 

Hi Gurus,

 

The mentioned assertion states "For each Interface Message Reference component in the {interface message references} property of an Interface Operation component, its {message label} property MUST be unique.".

 

Correct me if I am wrong, but can we have the XSD capture this constraint explicitly ?

 

For instance,

 

<xs:element name="operation" type="wsdl:BindingOperationType">
  <xs:unique name="messageLabel">
    <xs:selector xpath="(wsdl:input|wsdl:output:wsdl:infault|wsdl:outfault)">
     <xs:field xpath="@messageLabel">
    </xs:selectpr>
  </xs:unique>
</xs:element>


rgds,

Ram
--
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor