Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Schema composition questions

From: "Michael Kay" <mike@--------.--->
To: "'Michele Vivoda'" <idmichele@-----.-->,"'Shlomo Yona'" <S.Yona@--.--->,<xml-dev@-----.---.--->
Date: 7/13/2007 3:07:00 PM
> when I have doubts about include/composition I often look to 
> this illuminating post:
> 
> http://xsd.stylusstudio.com/2004Oct/post01000.htm#
> 

It's illuminating in that it clearly states one person's view of the
process. However, the notion that you can implement xs:include by creating
schema components from the referenced schema document and then including the
(perhaps modified) components is simplistic, because you don't have enough
information to construct the components until you have assembled all the
components that they refer to - for example, you don't know the {variety} of
a simple type until you have found its base type. So these components are at
best "skeletal components", a concept which isn't exactly clear from the
spec...

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


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