W3C home > Mailing lists > Public > xmlschema-dev@w3.org > June 2004

RE: Occurrence constraints

From: Keith Suderman <suderman@cs.vassar.edu>
Date: Thu, 03 Jun 2004 18:05:59 -0400
Message-Id: <5.1.1.6.0.20040603180455.02561dc0@wheresmymailserver.com>
To: xmlschema-dev@w3.org

At 01:02 PM 6/3/2004 -0400, you wrote:

>The last clause of the following constraint rules out having
>both minOccurs="0" and maxOccurs="0" specified:

Thank you, I couldn't find that particular constraint no matter how hard I 
looked (I now realize I was always searching for "maxOccurs" not "{max 
occurs}"...).

>On the other hand, there are also multiple parenthetical comments, such as
>
>   (unless minOccurs=maxOccurs=0, in which case the item
>   corresponds to no component at all)
>
>But I think the constraint dominates.

The funny thing is, since I couldn't find the constraint myself, and no 
else responded, I was going to use a "vote" of my available 
parsers/validators (xerces, XSV, SQC, XML Spy and Oxygen) .  The outcome of 
the vote was 5-0 that it _is_ ok to have minOccurs=maxOccurs=0!

Thanks again,
Keith


--------------------------------------------------
Keith Suderman
Technical Specialist
American National Corpus
suderman@cs.vassar.edu
http://americannationalcorpus.org
Received on Thursday, 3 June 2004 18:06:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:44 GMT