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

Re: <all> and minOccurs="0" Problem

• From: ht@c... (Henry S. Thompson)
• To: Eddie <eddie@a...>
• Date: Fri, 14 Sep 2001 10:49:02 +0100

Eddie <eddie@a...> writes:

> > > -----Original Message-----
> > > From: Radek Wisniewski [mailto:rw@d...]
> > > Sent: Thursday, September 13, 2001 10:00 AM
> > > To: Martin Gudgin
> > > Cc: Radek Wisniewski; xml-dev@l...
> > > Subject: Re:  <all> and minOccurs="0" Problem
> > >
> > >
> > > Yes, it works fine. But the question remains unanswered: What is the sence
> > > of <all minOccurs="0"> attribute?
> > > What interesting, I can't deklare such en value in any way because:
> > > 1) under <complexType>, element <all> must have both attributes minOccurs
> > > and maxOccurs set to 1
> 
> No, the entire <xs:all> group can be optional as well, i.e allowed values for
> minOccurs on the xs:all element itself is 0 or 1.

Eddie is correct -- the XML Schema WG has agreed a correction here, as 
two different parts of the REC contradict each other on this point,
but the resolution will be that 0 or 1 is allowed.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@c...
		     URL: http://www.ltg.ed.ac.uk/~ht/

• Follow-Ups:
  • Re: <all> and minOccurs="0" Problem
    • From: Radek Wisniewski <rw@d...>

• References:
  • RE: <all> and minOccurs="0" Problem
    • From: "David E. Cleary" <davec@p...>
  • Re: <all> and minOccurs="0" Problem
    • From: Eddie <eddie@a...>

• Prev by Date: XML transform
• Next by Date: Re: xml schema trouble
• Previous by thread: Re: <all> and minOccurs="0" Problem
• Next by thread: Re: <all> and minOccurs="0" Problem
• Index(es):
  • Date
  • Thread