Cart
[Home] [By Thread] [By Date] [Recent Entries]
Ahh, redefinition. This isn't really type derivation since redefinition is pervasive. Actually it is much worse especially since you can't prevent redefinition like you can derivation or substitution. -- PITHY WORDS OF WISDOM In any contest between power and patience, bet on patience. This posting is provided "AS IS" with no warranties, and confers no rights. > > > -----Original Message----- > From: Jeff Lowery [mailto:jlowery@s...] > Sent: Thursday, September 05, 2002 9:55 AM > To: 'ht@c...'; Paul Prescod > Cc: xml-dev@l... > > Okay, I've got my mind right. > > It's not an enumeration of simpletype values that I remember, > but more along the lines of Paul's example, below. The > example is from Eric vdV's book, p. > 203 (paraphrased below): > > <group name="name"> > <choice> > <element ref="a"/> > <element ref="b"/> > </choice> > </group> > > <redefine schemaLocation="foo.xsd"> > <group name="name"> > <choice> > <group ref="name"/> > <element ref="c"/> > </choice> > </group> > </redefine> > > Quoth: "... the effect of this redefinition is to allow a > new element ([c]) to be accepted instead of a [a] or [b]." > > > > ----------------------------------------------------------------- > The xml-dev list is sponsored by XML.org > <http://www.xml.org>, an initiative of OASIS > <http://www.oasis-open.org> > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > To subscribe or unsubscribe from this list use the subscription > manager: <http://lists.xml.org/ob/adm.pl> > >
|
