OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Problems with xs:redefine

[ Lists Home | Date Index | Thread Index ]
  • To: Michael Kay <mike@saxonica.com>
  • Subject: RE: [xml-dev] Problems with xs:redefine
  • From: Kasimier Buchcik <K.Buchcik@4commerce.de>
  • Date: Thu, 24 Nov 2005 15:28:56 +0100
  • Cc: ML-xml-dev <xml-dev@lists.xml.org>
  • In-reply-to: <E1EfHa0-0006Vc-2N@mail.firmenpost.de>
  • References: <E1EfHa0-0006Vc-2N@mail.firmenpost.de>


On Thu, 2005-11-24 at 13:55 +0000, Michael Kay wrote:
> > Potential bug in Saxon 8.5.1: I noticed that it does not fire an
> > UPA error for the above scenario; on the other hand it does fire the
> > error if the @ref attributes are substituted for @name attributes.
> > A "different/same element declaration" issue?
> Yes, Saxon is testing only that the element declaration is unambiguously
> identified; if two distinct particles refer to the same declaration, Saxon
> doesn't report an error. It's a known and published limitation of Saxon that
> it doesn't implement this bug in the spec ;-)

A 'same declaration' could also be an identical component, couldn't it?
If yes, then shouldn't the following model be accepted by Saxon as well?
I'm a bit scared of the necessity of component identity checks here.

    <xs:element name="a"/>
    <xs:element name="b"/>
        <xs:element name="a"/>
        <xs:element name="b"/>




News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS