W3C home > Mailing lists > Public > xmlschema-dev@w3.org > March 2006

RE: Schema redefintions in cascade

From: Michael Kay <mike@saxonica.com>
Date: Mon, 13 Mar 2006 22:42:14 -0000
To: "'Antoli, Leo'" <Leo.Antoli@Misys.com>, <xml-dev@lists.xml.org>, <xmlschema-dev@w3.org>
Message-ID: <E1FIvkD-0005LI-N2@aji.w3.org>

When XML Spy 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

> 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 XML Spy - 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
Received on Monday, 13 March 2006 22:43:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:56:09 UTC