Identity Constraints

I am rather confused by some types of multi field identity constraints. The
example in the schema primer: (at
http://www.w3.org/TR/xmlschema-0/#specifyingUniqueness)

<unique name="dummy1">
  <selector xpath="r:regions/r:zip"/>
  <field    xpath="@code"/>
  <field    xpath="r:part/@number"/>
 </unique>

seems to be what I want, BUT I can't reconcile this with the validation
rules in the standard (3.11.4):

"3 For each node in the ·target node set· all of the {fields}, with that
node as the context node, evaluate to either an empty node-set or a node-set
with exactly one member, which must have a simple type."

Specifically the second field would appear to have multiple values for a
single node in the target set (a 'zip' element).

Is there a good explanation anywhere of the use of identity constraints
where the fields are not all at the same depth?

Thanks for any help,
Mark Thornton

Received on Thursday, 7 March 2002 12:08:35 UTC