[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xml-dev] <all> and minOccurs="0" Problem
- From: ht@cogsci.ed.ac.uk (Henry S. Thompson)
- To: Eddie <eddie@allette.com.au>
- Date: Fri, 14 Sep 2001 10:49:02 +0100
Eddie <eddie@allette.com.au> writes:
> > > -----Original Message-----
> > > From: Radek Wisniewski [mailto:rw@datenknecht.de]
> > > Sent: Thursday, September 13, 2001 10:00 AM
> > > To: Martin Gudgin
> > > Cc: Radek Wisniewski; xml-dev@lists.xml.org
> > > Subject: Re: [xml-dev] <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@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/