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] schema & polymorphism - resolving duplicate element defini

[ Lists Home | Date Index | Thread Index ]

"Chris Hoehn" <chris@hellohawaii.com> writes:

> I've got two schemas, A & B, that each define an element named EltC.  A and
> B both use the same targetNamespace. A and C are both defined by a
> "standards body" so I do not want to modify their definitions.
> If I want to create another schema, Z,  which aggregates A & B (i.e. A & B
> are children in Z), I have the problem of a duplicate definition of EltC.  I
> have, to this point, tried creating Z by <include> or <import> of A & B.
> Both of which give the problem of a duplicate definition.  This seems so be
> an issue of polymorphism to me.
> My question is... how can I properly <import> (or <include>) A & B in Z such
> that there is not this definition conflict?  Is this even possible if A & B
> have the same targetNamespace value?

Well, there's really nothing W3C XML Schema can do to help you.
You've got conflicting definitions, and the authors of A & B went out
of their way to make it impossible for you to fix the problem

To see why it's hard, think about what you want the _result_ (Z) to
validate for EltC instances, given the contradiction.  Which one wins,
if either?  The schema processor can't read your mind here, alas.

  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/


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

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