Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Making atleast one of multiple optional elements mandatory

From: Boris Kolpackov <boris@-------------.--->
To: NULL
Date: 3/2/2007 7:49:00 PM

"ANoobee" <avachali@g...> writes:

> > What is the best approach to force atleast one of a few optional
> > elements required in an XSD?
> > This is what I'm tring to do:
> >
> > <email>
> >    <to>
> >    <cc>
> >    <bcc>
> > </email>
> >
> > where to, cc and bcc are optional but email should contain atleast one
> > of them.
> >
>
> Additional information...
> The order in which the to, cc and bcc occur does not matter and each
> of them will be un-bounded.


You can use sequence of choice's for that:

<complexType name="email">
  <sequence maxOccurs="unbounded">
    <choice>
      <element name="to" type="string"/>
      <element name="cc" type="string"/>
      <element name="bcc" type="string"/>
    </choice>
  </sequence>
</complexType>


hth,
-boris

-- 
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent