OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] XSD Question: what is the current recommendation regardinglarge values for maxOccurs?

> Is that still the recommendation? Or, are validators more sophisticated now and can handle large values for maxOccurs?

I think you will find that some are, some aren't, and with some - it 
depends, based on where the maxOccurs lives in the content model. Saxon 
these days is fine with a large maxOccurs at the top level of a content 
model, but it can struggle if you have one within a choice especially if 
the choice itself has a maxOccurs.

I still find it a little implausible that there are "business 
requirements" not to have more than 500 Foo elements. What are these: 
order lines in a purchase order? Employees in a department? Contact 
names/addresses for a customer? I suspect they are not so much business 
requirements as limits imposed by older IT (or paper) processing systems.

Michael Kay

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS