This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4380 - Proposal for Assertion InterfaceMessageReference-0042
Summary: Proposal for Assertion InterfaceMessageReference-0042
Status: RESOLVED WONTFIX
Alias: None
Product: WSDL
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact: WSDL Mailing List
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-08 23:43 UTC by Jonathan Marsh
Modified: 2007-03-29 17:02 UTC (History)
0 users

See Also:

Attachments

Description Jonathan Marsh 2007-03-08 23:43:36 UTC
Comment 1 Jonathan Marsh 2007-03-08 23:48:06 UTC 
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>
Comment 2 Jonathan Marsh 2007-03-29 17:02:42 UTC 
Per http://lists.w3.org/Archives/Public/www-ws-desc/2007Mar/att-0083/20070329-ws-desc-minutes.html#item04 closed with no action.

The specification of a uniqueness constraint is incompatible with the optionality of the attribute.