Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? [Thread Next] RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint?To: "Michael Kay" <mike@--------.--->, "Henry S. Thompson" <ht@---.--.--.--> Date: 4/16/2007 11:59:00 PM Thanks. Shlomo. -----Original Message----- From: Michael Kay [mailto:mike@s...] Sent: =E2 17 =E0=F4=F8=E9=EC 2007 14:11 To: Shlomo Yona; 'Henry S. Thompson' Cc: xmlschema-dev@w... Subject: RE: Determinization in case of ambiguity or Should XML = validators report on schemas that violate the UPA constraint? > > I had another example where an xsd:sequence with an implied > minOccurs="1" and maxOccurs="1" contains particles with = minOccurs="0". > What is the expected behavior when none of these particles > appear in an XML instance? It's quite valid to have a sequence with minOccurs="1" that contains = an element with minOccurs="0". Conceptually it means that the sequence = must occur, but if all the elements within the sequence are optional, then = the sequence is allowed to be empty. Of course in an instance document you = can't tell the difference between an empty sequence and an absent sequence, so = you might as well have written minOccurs="0" on the whole sequence, but in = the grammar they are subtly different. Michael Kay http://www.saxonica.com/ From esirois@c... Wed Apr 18 01:35:32 2007 Received: from maggie.w | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
