• From: Michael Glavassevich <mrglavas@c...>
• To: xml-dev@l...
• Date: Tue, 9 Aug 2011 10:21:25 -0400

Michael Kay <mike@s...> wrote on 08/09/2011 08:56:36 AM:

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

A similar story for Xerces-J. Counters are used to handle the simpler cases.

> 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
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@c...
E-mail: mrglavas@a...

• References:
  • XSD Question: what is the current recommendation regarding largevalues for maxOccurs?
    • From: "Costello, Roger L." <costello@m...>
  • Re: XSD Question: what is the current recommendation regardinglarge values for maxOccurs?
    • From: Michael Kay <mike@s...>