thanks for this bill, i agree that we have wandered from our naming of object classes with Order Response. This seems to have slipped through the editing process. However, the issue with Order and OrderHeader/OrderSummary is different. >From discussions within the LC team, we believe that there is only one object class (called 'Order'). the fact we have split this into two 'containers' OrderHeader and OrderSummary does not affect the underlying model. this can be seen when we ask why some elements are in OrderHeader and some in OrderSummary - it is an arbitary distinction. for example, why is PaymentMeans in the Header and PriceAmount in the Summary??? these reflect historical positions based on printing technology! we had discussed merging the Header/Summary so we end up with the logically correct Order and LineItem as the two major object classes. As it stands this is an example of the ambiguous way we are dealing with what Arofan's paper calls 'grouping elements'. hopefully the forthcoming discussions will resolve this once and for all. Burcham, Bill wrote:
40AC2C8FB855D411AE0200D0B7458B2B073455CF@scidalmsg01.csg.stercomm.com > I changed UBL000422 to OrderResponse.Order.Identifier yielding an element with tag name OrderID. The Zip archive containing the modified schema and updated diagrams is attached. I did not repair other names associated with order response. It seems that we've got a pervasive problem with the Object Class for order response in the UBL Spreadsheet, to wit, we've specified an Object Class of Order rather than OrderResponse . Hmm... now I'm looking at the Object Class column for other properties of Order Response... ResponseCode is a big red flag -- it's object class is Acknowledgement . That cannot be. Similar problems exist in the Order tab. Properties of ABIE's like OrderHeader have Object Class named Order (should be OrderHeader ). Same for OrderSummary where properties have Object Class of Order again (should be OrderSummary ). If you have a look at the Re-used Types tab you see that it i s uniformly the case that property rows (white background) have Object Class set to the previous ABIE row (pink background). This should be uniformly the rule across all tabs. Anyhow, the tweaked diagrams and schema are attached. -Bill