Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Re: Restricting attribute use from optional to required >Thread Next - Re: Restricting attribute use from optional to required RE: Restricting attribute use from optional to requiredTo: =?iso-8859-2?Q?'Jan_P=F8idal'?= <jan.pridal@-----.--->, Date: 8/17/2009 1:30:00 PM > 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 | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
