Re: [Bug 4380] Proposal for Assertion InterfaceMessageReference-0042

Hi Jonathan,

I see the update on bug description for 4380 as
"
The specification of a uniqueness constraint is incompatible with the
optionality of the attribute.
"

I am trying to understand the rationale of this explanation, but with no
luck. :-( Maybe I am missing something here.
Would it be possible to elaborate more on this?

regards,
Ram




On 3/8/07, [email protected] <[email protected]> wrote:
>
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=4380
>
>
>
>
>
> ------- Comment #1 from [email protected]  2007-03-08 23:48 -------
> 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>
>
>


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

-Ramkumar Menon
A typical Macroprocessor