This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the Microsoft IdentityConstraint test idH031, the node selected by the field selector in an identity constraint has a complex type with simple content, and the test considers this to be valid. The specification requires that the field has a simple type. See Validation Rule: Identity-constraint Satisfied, clause 3. This is arguably an error in the spec, but the spec does say quite clearly that it must be a simple type, which rules out a complex type with simple content.
Also applies to idK011 idL076 idL077
It was discussed on the xmlschema-dev forum at http://lists.w3.org/Archives/Public/xmlschema-dev/2003Feb/0025.html and the conclusion was that identity constraints are supposed to work on SimpleContent as well. [for Zafar Abbas]
Noted that this has changed in 1.1 to allow a complex type with simple content. Bug #5780 has been raised against the 1.0 spec. We will leave this bug open making it dependent on 5780.
WG decided: Duplicate idH031, mark the duplicate stable and 1.1 only. (Action to HT.)
WG decided (addendum): take tests: idH031 idK011 idL076 idL077 create a duplicate of each, and mark the duplicate stable and 1.1 only. (Action to HT.)
1.1-only copies created, with names idH031a, idK011a. idL076a, idL077a
Made stable 1.1-only copies named idH031a, idK011a, idL076a, idL077a