xs choice maxoccurs unbounded,minoccurs 0 maxoccurs unbounded,xs group,maxoccurs unbounded,choice minoccurs,xs choice,xs choice unbounded,xs choice maxoccurs,choice minoccurs 0 maxoccurs unbounded,xs choice minoccurs, xml%%%xs choice maxoccurs unbounded - Re: xs:group/xs:choice[@minOccurs

[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: xs:group/xs:choice[@minOccurs | @maxOccurs]


xs choice maxoccurs unbounded
Bryce K. Nielsen wrote:

>This email will have better response on the xmlschema-dev mailing list
>(xmlschema-dev@w...) but I'll give it a go:
>
>xs:group's limit the min/max occurs of not just choice nodes, but all
>compositors (i.e. choice, sequence and all nodes). 
>

You mean all child nodes of xs:group not all nodes in a xs:group, right?

The reason I was curious is because I have to do the following:

<xs:group>
  <xs:choice>
    <xs:element ref="elem1" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="elem2" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="elem3" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="elem4" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="elem5" minOccurs="0" maxOccurs="unbounded"/>
  </
</

When it would be much simpler to write:

<xs:group>
  <xs:choice minOccurs="0" maxOccurs="unbounded">
    <xs:element ref="elem1"/>
    <xs:element ref="elem2"/>
    <xs:element ref="elem3"/>
    <xs:element ref="elem4"/>
    <xs:element ref="elem5"/>
  </
</
(BTW,  msxml accepts this)

I suppose there might be problems (?) if you do something like:

<xs:group>
  <xs:choice minOccurs="0" maxOccurs="unbounded">
    <!--*****-->
    <xs:group ref="group1"/>
    <!--*****-->
    <xs:element ref="elem1"/>
    <xs:element ref="elem2"/>
    <xs:element ref="elem3"/>
    <xs:element ref="elem4"/>
    <xs:element ref="elem5"/>
  </
</

-Rob

>The occurence options are
>controlled by the entire group, not the individual nodes within the group.
>Why this is, I'm not entirely certain, anyone else want to field the
>reasoning behind this?
>
>Bryce K. Nielsen
>SysOnyx, Inc. (www.sysonyx.com)
>Makers of xmlLinguist, the Text-to-XML Translator
>http://www.sysonyx.com/products/xmllinguist
>
>
>----- Original Message ----- 
>From: "Robert Koberg" <rob@k...>
>To: "XML Developers List" <xml-dev@l...>
>Sent: Friday, June 25, 2004 12:23 PM
>Subject:  xs:group/xs:choice[@minOccurs | @maxOccurs]
>
>
>  
>
>>Hi,
>>
>>Why can't you have minOccurs and maxOccurs attributes on a xs:choice
>>element that is a child of a xs:group element?
>>
>>-Rob
>>    
>>


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.