RE: Restricting attribute use from optional to required

> But it is then more than a little bit awkward - as I have to 
> add a new complexType that restricts the complexType 'parent' 
> and then within it I have to repeat all the stuff declared 
> the 'parent' and its parent types (by extension) etc.

Yes, that's a particularly nasty feature of derivation by restriction.

If you're only restricting the attributes, and not the content model, you
can get around it by having both the base type and the derived type
reference the same named model group.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 

Received on Monday, 17 August 2009 13:29:10 UTC