This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Clause 3 of Schema Component Constraint: Attribute Declaration Properties Correct reads: 3 If the {type definition} is or is constructed from ID, then there is no {value constraint}. Similarly, clause 5 of Schema Component Constraint: Element Declaration Properties Correct reads: 5 If the {type definition} or {type definition}'s {content type}'s {simple type definition} is or is constructed from ID, then there is no {value constraint}. These are, I think, holdovers from the past: they reconstruct constraints originally formulated for SGML DTDs and carried over for compatibility reasons to XML 1.0 and 1.1 DTDs. But they violate the principle of orthogonality: why should value constraints be allowed for some types but forbidden for others? The spec becomes simpler and the design cleaner if these ad hoc rules are dropped. The WG's decision on bug 4348 reflects the view that compatibility with the ID-related constraints of SGML and XML DTDs no longer needs to be a high-priority goal. I believe we should remove these unhelpful constraints.
Discussed at 2005-06-01 telecon. The WG adopted the suggested change.
The proposal adopted by the Working Group has now been integrated into the status quo documents on the server; accordingly, I'm changing the status to 'RESOLVED'.