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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

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

Subject: Re: [ubl-comment] Two elements not packaged in UML documents

As I was responsible for the UML diagrams i apologise for omitting the SalesConditions ABIE.  I bieleive it should have been part of the Item package.

the Period ABIE is slightly different, as it is re-used by two different packages  (Delivery and Contract) and i felt it would be confusing to put it in only one! i guess this is the arbitrariness of the packaging decisions.

thank you for pointing this out to us and i am glad to see you are developin g some useful UBL software libraries.  is this a commercial project or a freeware offering?.

Carlos Lozano wrote:
Hi all,
   I am developing a C++ library whose purpose is to provide an API for building UBL documents. For every complex type described in the XSD I am building a C++ class, and I am packaging the classes in the way described in UML documents released with UBL 1.0 (Item, Procurement, Tax, ...).
   After packaging all the elements I have detected that there are two complex types (PeriodType and SalesConditionsType described in CommonAggregateComponents) that appear referenced in some UML documents but they aren't packaged in any package.
   Which package could be the right one for them? Can they be packaged in an existing package or new packages should be created? 
    Carlos Lozano

tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160

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