Hi Folks,
The Unique Particle Attribution (UPA) error is driving me crazy. UPA doesn't make sense in a DFDL schema because the DFDL properties eliminate the ambiguity. Here's a schema that produces a UPA error: <xs:element name="record"> <xs:complexType> <xs:sequence> <xs:element name="Section_Code" type="fixedLength_string" dfdl:length="1"/> <xs:choice dfdl:choiceDispatchKey="{Section_Code}"> <xs:sequence dfdl:choiceBranchKey="D"> <xs:element name="Subsection_Code" type="fixedLength_string" dfdl:length="1"/> </xs:sequence> <xs:sequence dfdl:choiceBranchKey="E"> <xs:element name="Subsection_Code" type="fixedLength_string" dfdl:length="1"/> </xs:sequence> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> The UPA error occurs because there are two Subsection_Code elements within the record element. If this was a plain XML Schema, then I can understand the UPA error because an XSD validator wouldn't know whether to use the first or the second Subsection_Code element to validate XML. But this isn't a plain XML Schema, it is a DFDL schema and the choiceBranchKey let's us know that the first Subsection_Code should be used when the Section_Code = D, the second should be used when Section_Code = E. Is there any way to disable UPA errors? /Roger