• To: xml-dev@l...
• Subject: Re: help in processing compositor's in XML Schema?
• From: "Thomas B. Passin" <tpassin@c...>
• Date: Mon, 11 Mar 2002 21:04:20 -0500
• References: <3A967FE7B99E134C9FE65E2C136560300DE05C@l...>

[CHIUSANO, Joseph]

> You can accomplish this with model groups. You can create one model group
to
> hold the "header" elements, and one to hold the "child" elements (both
must
> be declared globally). Within each model group, specify the "choice"
> compositor to avoid having order enforced. For example:
>
> <xsd:group name="HeaderElementGroup">
>      <xsd:all>
>           <xsd:element name="header1" type="[sometype]">
>           <xsd:element name="header2" type="[sometype]">
>           <xsd:element name="header2" type="[sometype]">
>      </xsd:all>
> </xsd:group>
>

Maybe, but it depends on the cardinality that Bill needs.  If he needs
exactly one of each but wants them to be unordered, I don't think you can do
that with XML Schema, even with "choice" model groups (because you can't
require exactly one of each).  Schematron can do it nicely, though.

Cheers,

Tom P

• References:
  • RE: help in processing compositor's in XML Schema?
    • From: "CHIUSANO, Joseph" <JCHIUSANO@l...>

• Prev by Date: Re: Stupid Question (was RE: XML doesn't deserveits "X".)
• Next by Date: Problem with noNameSpaceSchemaLocation
• Previous by thread: RE: help in processing compositor's in XML Schema?
• Next by thread: RE: help in processing compositor's in XML Schema?
• Index(es):
  • Date
  • Thread