-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: wd32
-
Fix Version/s: wd33
-
Component/s: None
-
Labels:None
-
Environment:
Toby Considine
-
Resolution:
In current schema, all PartyIDs are derived from PartyID (implicitly through substitution group). PartyID itself was previously abstract, and now is concrete. THis periodically causes processing errors, particuarly when MinOccurs is allowed. For example:
For example, the type EiTarget includes (abreviated)
<xs:sequence>
<xs:element ref="eitc:venID" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="eitc:partyID" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
As currently defined a venID is a PartyID, so the processor may be unable to determine whether a listed venID is one of the unbounded venIDs or the first of the unbounded partyIDs. THis only occurs because of the indeterminacy of the count of venID above. there would be no problem if, for example, venID was specified as minOccurs="1" maxOccurs="1"