OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ttsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Redefinition of ComplexTypes

Dan Vint sent a comment into the 0p70 Review comments.  He questions the way the complexTypes were generated and being used.  In the joint NDR/LCSC call today we went through and reviewed the comments that related to NDR and TTSC.  This was suggested to be completely a TTSC issue.
Please review his comment, and lets discuss this.
Dan wrote:
In reviewing the Schemas that were generated I was surprised to see the redefinition of complexTypes for the various address and party types. For instance:
        <xsd:element name="Address" type="AddressType"/>
        <xsd:complexType name="AddressType" id="UBL000028">
        <xsd:element name="DeliverToAddress" type="DeliverToAddressType"/>
        <xsd:complexType name="DeliverToAddressType" id="UBL000145">
        <xsd:element name="JurisdictionAddress" type="JurisdictionAddressType"/>
        <xsd:complexType name="JurisdictionAddressType" id="UBL000309">  and there are others.

It seems that the only thing that really changes is the description of elements in the different aggregates, but from what I see the "address" content stays the same. I would have expected to see something like this:
        <xsd:element name="Address" type="AddressType"/>
        <xsd:complexType name="AddressType" id="UBL000028">
        <xsd:element name="DeliverToAddress" type="AddressType"  id="UBL000145"/>
        <xsd:element name="JurisdictionAddress" type="AddressType" id="UBL000309"/>

Was the previous sample what was really intended to be generated as the final schema? I see how it helps in the mapping of the definitions of all the various types of address, but it really complicates the final implementation when you have (in my sample) 3 different definitions of the same complexType, rather than reuse or extension of the basic AddressType.
With this schema I lose the connection between these similar/exact types, just to maintain documentation and mapping back to the spreadsheet. Maybe the complexType definition of AddressType could gather all the documentation together with something that indicates, when part of JurisdictionAddress, this means, X, and when part of DeliverToAddress this means Y.
Lisa Seaburg
Website: http://www.aeon-llc.com/
Email:  lseaburg@aeon-llc.com
Alternative Email: xcblgeek@yahoo.com
Phone: 662-562-7676
Cellphone: 662-501-7676
"Remember that great love and great achievements involve great risk."

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]