[
Lists Home |
Date Index |
Thread Index
]
Hmmm…I don't think that approach will work in this case, as the
top-level element name is the same in both cases ("human"). Here's my
thought process:
(1) Declare abstract element:
<xsd:element name="humanelement" abstract="true"/>
(2) Declare first substitutable element:
<xsd:element name="human" type="femaletype"
substitutionGroup="humanelement"/>
(3) Declare second substitutable element:
<xsd:element name="human" type="maletype"
substitutionGroup="humanelement"/>
This is where the problem lies - you are attempting to 2 global elements
named "human" of different data types.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
Strategy and Technology Consultants to the World
"Bryce K. Nielsen" wrote:
>
> In a way it's possible. May not be as clean as you'd like, but you can
> always create a "malehuman" type and a "femalehuman" type, then through
> choice or substitution groups limit the subelements.
>
> Bryce K. Nielsen
> SysOnyx, Inc. (www.sysonyx.com)
> Makers of xmlHack, The Simple XML Editor
> http://www.sysonyx.com/products/xmlhack
>
> -----------------------------------------------------------------
> 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://www.oasis-open.org/mlmanage/index.php>
|
