Following the paper trail on this leads towhich is a bug against XSD 1.0 that was never resolved. So I think the answer to your question is that it's a known bug in the spec.In most cases, but perhaps not all, when there's a known bug in XSD 1.0, consulting XSD 1.1 will give you the preferred resolution.Michael KaySaxonica