[OASIS Issue Tracker] Created: (ENERGYINTEROP-592) Clean up inheritance and substitution in partyIDs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Clean up inheritance and substitution in partyIDs
-------------------------------------------------

                 Key: ENERGYINTEROP-592
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-592
             Project: OASIS Energy Interoperation TC
          Issue Type: Bug
    Affects Versions: wd32
         Environment: Toby Considine
            Reporter: Toby Considine
            Assignee: Toby Considine
             Fix For: WD33


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"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira