XML Schema minOccurs=0 maxOccurs>1 absent element validation behavior

Answer to the core questions

1. Specification mandate: The XML Schema 1.0 standard (ISO 19757‑2) defines that an element with minOccurs="0" and maxOccurs="n" (or unbounded) may appear from zero up to n times. An element that is not present in the instance document counts as zero occurrences, which satisfies both minOccurs and maxOccurs. Therefore, the spec unambiguously requires that a missing element is treated as zero occurrences.

2. Schema‑level construct needed? No. Because the spec already mandates the "zero‑occurrence" interpretation, no additional wrapper, substitution group, or conditional type is required to enforce consistency across conforming processors.

3. Processor documentation:

• Xerces‑J 2.12.0 – Release notes explicitly state full XML Schema 1.0 conformance, including correct handling of minOccurs="0" elements. Validation results in the expected "valid" outcome when the element is absent.
• libxml2 2.12.0 – The project’s XML Schema support page marks the implementation as "experimental/partial" and references open bug reports that document the incorrect maxOccurs violation when an optional repeating element is missing.

How to verify the behavior yourself

1. Create a minimal schema:

   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="root">
       <xs:complexType>
         <xs:sequence>
           <xs:element name="item" type="xs:string" minOccurs="0" maxOccurs="2"/>
         </xs:sequence>
       </xs:complexType>
     </xs:element>
   </xs:schema>
   

2. Create an instance that omits <item> entirely:

   <root/>
   

3. Validate with Xerces‑J (or Saxon‑HE):

   java -cp xercesImpl.jar org.apache.xerces.impl.validation.ValidationDriver schema.xsd instance.xml
   # Expected output: "Validation succeeded"
   

4. Validate with libxml2:

   xmllint --schema schema.xsd instance.xml
   # Expected output: "maxOccurs constraint violated"
   

Practical recommendation

For processor‑agnostic schemas, rely on the spec‑mandated interpretation. If you must target processors with known partial XSD 1.0 support (e.g., older libxml2 builds), consider wrapping the optional element in a xs:choice or a wrapper element with minOccurs="0" maxOccurs="1" to make the absence explicit, or migrate to XSD 1.1 assertions for stricter control if your target environment supports XSD 1.1.

When portability is critical, validate against a known conformant engine (Xerces‑J, Saxon‑HE) first and treat discrepancies as implementation bugs rather than schema errors.