Xan Gregg wrote:

>> Given the following XML segment:
>>
>> <foos>
>>    <foo id="1490" name="myName"/>
>>    <foo id="9091" name="myNAME"/>
>> </foos>
>>
>> shouldn't a uniqueness constraint:
>>
>>    <xsd:element name="foos">
>>    <xsd:complexType>
>>        <xsd:sequence>
>>        <xsd:element name="foo" type="foo_type" maxOccurs="unbounded"/>
>>        </xsd:sequence>
>>    </xsd:complexType>
>>    <xsd:unique name="name_id">
>>        <xsd:selector xpath="foo"/>
>>        <xsd:field xpath="@name"/>
>>    </xsd:unique>
>>    </xsd:element>
>>
>> throw an error?  ...
>> Shouldn't unique be case-sensitive?
>
>
> Yes, and I don't see any other problems with your example.  Are you 
> sure your processor enforces identity constraints?

Using the sample program, sax.Counter, of Xerces 2.6.2 with the flags, 
-v -s -f -np, will throw:
'Duplicate unique value [myNAME] declared for identity constraint of 
element "foos".'
when the case is the same.

-Jeff Dahl

From xan.gregg@j...  Mon Apr 12 10:25:17 2004
Return-Path: <xan.greg