Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Schema redefintions in cascade

From: "Michael Kay" <mike@--------.--->
To: "'Antoli, Leo'" <Leo.Antoli@-----.--->, <xml-dev@-----.---.--->, <xmlschema-dev@--.--->
Date: 3/13/2006 10:42:00 PM

When XMLSpy">XMLSpy tells you one thing and everyone else tells you the opposite,
most punters would lay their bets on the majority opinion being right:
though of course one can't quote chapter and verse without seeing your code.

redefines is defined to be pervasive. If you redefine X, then all references
to X, wherever they appear, are considered to refer to the new X. This means
that it's impossible to have two different redefinitions of the same X in
force at the same time, which is what you seem to be trying to achieve.

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

> 
> I am changing an existing schema using the "redefine" tag. 
> The original
> schema file is left untouched. As some elements must be both 
> restricted and
> extended, I have created two schema files. The first one redefines the
> original schema file restricting some elements and the second 
> one redefines
> the restricting schema file adding some extensions. An 
> element existing in
> the original file can be restricted in the first file and 
> then extended in
> the second one.
> It works fine in XMLSpy">XMLSpy - it has a proprietary schema 
> validator - but it's
> not working fine in other systems such as Saxonica, Stylus 
> Studio, Xerces or
> Oracle's schema validator. I think nested redefines (or 
> includes) can be
> done according to the W3C Schema recommendations. 
> 
> I would like to know if my approach is correct and if there 
> is another way
> to achieve the same results. Any suggestion to solve this 
> issue is more than
> welcome.
> 
> 
> Thank you very much.
> 
> Kind Regards,
> Leo Antoli
> 
> 
> 
> 



From ht@i... Tue Mar 14 10:28:40 2006
Received: from maggie.w3.org ([193.51.20


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