Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Restricting attribute use from optional to required

From: "Michael Kay" <mike@--------.--->
To: =?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 




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent