• From: Michael Kay <mike@s...>
• To: xml-dev@l...
• Date: Tue, 09 Aug 2011 13:56:36 +0100

> 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
Saxonica

• Follow-Ups:
  • Re: XSD Question: what is the current recommendation regardinglarge values for maxOccurs?
    • From: Michael Glavassevich <mrglavas@c...>
  • Re: XSD Question: what is the current recommendationregarding large values for maxOccurs?
    • From: John Cowan <cowan@m...>

• References:
  • XSD Question: what is the current recommendation regarding largevalues for maxOccurs?
    • From: "Costello, Roger L." <costello@m...>