Clean up inheritance and substitution in partyIDs

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • wd33
    • Affects Version/s: wd32
    • Component/s: None
    • None
    • Environment:

      Toby Considine

    • Hide

      Created abstract actorID
      Made all PartyIDs of type actorID
      Payloads will be cleaned up in a spearate process.
      Accepted Ed's comments on clarity in spec 3.2.1

      Show
      Created abstract actorID Made all PartyIDs of type actorID Payloads will be cleaned up in a spearate process. Accepted Ed's comments on clarity in spec 3.2.1

      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"

            Assignee:
            Edward Cazalet (Inactive)
            Reporter:
            Toby Considine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: