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

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

• To: xml-dev@l...
• Subject: Re: xs:group/xs:choice[@minOccurs | @maxOccurs]
• From: Bob Foster <bob@o...>
• Date: Sat, 26 Jun 2004 02:25:51 -0500
• In-reply-to: <000a01c45ae9$56a6fa80$6d61a485@ichiran>
• References: <000a01c45ae9$56a6fa80$6d61a485@ichiran>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608

I'm a bit puzzled by this. I can see why he can't have a 
minOccurs/maxOccurs on the group item as specified but why not on the 
choice nested in the group. This looks legal to me and I am curious what 
processors do not accept it.

Bob Foster
http://xmlbuddy.com/

Takuki Kamiya wrote:

> xs:group with "name" attribute makes it a model group, that is why
> it cannot have min/maxOccurs. To make sense to have occurrence
> properties, it has to be a particle, which you can achieve by xs:group
> with "ref" attribute that references a named model group. xs:group
> with "ref" attribute should be able to carry min/maxOccurs attributes
> on them.
> -Takuki Kamiya

• Follow-Ups:
  • Re: xs:group/xs:choice[@minOccurs | @maxOccurs]
    • From: Eric van der Vlist <vdv@d...>
  • Re: xs:group/xs:choice[@minOccurs | @maxOccurs]
    • From: ht@i... (Henry S. Thompson)

• References:
  • RE: xs:group/xs:choice[@minOccurs | @maxOccurs]
    • From: "Takuki Kamiya" <tkamiya@u...>

• Prev by Date: Re: XML Technologies: Progress via Simplification or Complexification?
• Next by Date: Re: xs:group/xs:choice[@minOccurs | @maxOccurs]
• Previous by thread: Re: xs:group/xs:choice[@minOccurs | @maxOccurs]
• Next by thread: Re: xs:group/xs:choice[@minOccurs | @maxOccurs]
• Index(es):
  • Date
  • Thread