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

Occurrence Question

• To: xml-dev@l...
• Subject: Occurrence Question
• From: Michele Vivoda <idmichele@y...>
• Date: Sun, 26 Mar 2006 20:36:55 +0200 (CEST)
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.it; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type; b=fB6vy1t626+tnxsaMBvkJE8uEBbtpYXDAWP5UMG4AypAemgIY4e+0ljga6eT64GOuHBYSfEODkdXvdFoeN4KienQVvh6J0XQQLFnWOwqCZRL9KwJAyegAmLPukChlW3Rr8XKz74tvWGt1elVlOCfnNGYspXA+fqTBAezZjhMeTE= ;

Hi All,

I would like to know if these two snippets
have the same 'meaning' (for xml schema):

<xs:choice>
   <xs:element minOccurs="0" maxOccurs="unbounded"
ref="col"/>
   <xs:element minOccurs="0" maxOccurs="unbounded"
ref="colgroup"/>
</xs:choice>

AND

<xs:choice minOccurs='0'>
   <xs:element maxOccurs="unbounded" ref="col"/>
   <xs:element maxOccurs="unbounded" ref="colgroup"/>
</xs:choice>

Options I thought:

1) they express the same schema components 
  (don't think so, since min and max are attributes of
particle component)
2) they express different components but these
components validate the same instances.
3) they are different and validate different instances
(presumably    
  because the first one wants at least one selected
particle for the choice).
4) In some contexts they have surely the same meaning,
in others they might not (?).
5) None of the above

Thanks
Michele Vivoda


	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it

• Prev by Date: Re: Bad programmers use recursion, xslt (Offtopic...)
• Next by Date: [ANN] nux-1.5 release
• Previous by thread: Call for fast XML implementations
• Next by thread: [ANN] nux-1.5 release
• Index(es):
  • Date
  • Thread