I have run into a problem when trying to use the Orbeon form schemas. The schemas use the “all” element incorrectly. If you look at the simplified schema below you can see that the “staging-area” tag is wrapping the repeating “staging-area_staging-repeat” tag within an “all” element. The rules for an “all”element are:
• Each element in the xsd:all group must occur zero or once; that is minOccurs and maxOccurs must each be 0 or 1
• The xsd:all group must be the top level element of its type
• The xsd:all group may contain only individual element declarations; no choices or sequences
<xs:schema xmlns:vc="
http://www.w3.org/2007/XMLSchema-versioning" xmlns:xf="
http://www.w3.org/2002/xforms" xmlns:xs="
http://www.w3.org/2001/XMLSchema" vc:minVersion="1.1">
<xs:element name="form">
<xs:complexType>
<xs:all>
<xs:element name="staging-area">
<xs:complexType>
<xs:all>
<xs:element maxOccurs="unbounded" minOccurs="1" name="staging-area_staging-repeat">
<xs:complexType>
<xs:all>
<xs:element name="staging-area_staging-repeat_name"></xs:element>
<xs:element name="staging-area_disturbed-area"></xs:element>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="staging-area_output-text"></xs:element>
</xs:all>
</xs:complexType>
</xs:element>
</xs:all>
</xs:complexType>
</xs:element>
</xs:schema>
The simplest solution here is to change all of the “all” elements to “sequence” elements. The Orbeon developers may have avoided “sequence” because they didn’t want to enforce an order on the elements. The schema would have to become significantly more complex to accomplish that.
Locked
