[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: How to differentiate between a NO-CHANGE andDATA-ITEM-TO-BE-REMOVED in UBL-OrderChange-2.0.xsd
Hi, How should one populate an instance document based on UBL-OrderChange-2.0.xsd in the following scenario: - The original UBL-Order-2.0 instance contained several OrderLines. - One of these OrderLines had 3 BuyerProposedLineItems - Later on, an update occurs to the order, resulting in a instance document based on UBL-OrderChange-2.0.xsd: The second BuyerProposedLineItem is to be removed - How would one differentiate between NO-CHANGE and DATA-ITEM-TO-BE-REMOVED? Should I use the OrderLineStatusCode to indicate this unambigously? - In other cases however, such as UBL-CatalogueItemSpecificationUpdate-2.0.xsd, there is no such a status if I wanted to remove one of the many Notes. Obviously, the issue arises whenever an instance is meant to update previously transmitted data. In short, for UPDATING instance documents, how do I differentiate between NO-CHANGE and DATA-ITEM-TO-BE-REMOVED? Populate all necessary data items, including UNCHANGED ones? That would mean that absent (occurrences of) tags could mean a DELETE if data values for them were specified previously. I would think however that this is in conflict with UBL NDR rule [IND6] The absence of a construct or data in a UBL instance document MUST NOT carry meaning. Your thoughts on this are much appreciated. Regards Juerg Tschumperlin Wellington, New Zealand DISCLAIMER This e-mail is intended for the addressee only and may contain information which is subject to legal privilege. The contents are not necessarily the official view or communication of the Ministry of Education. If you are not the intended recipient you must not use, disclose, copy or distribute this e-mail or any information in, or attached to it. If you have received this e-mail in error, please contact the sender immediately or return the original message to the Ministry by e-mail, and destroy any copies. The Ministry does not accept any liability for changes made to this e-mail or attachments after sending. All e-mails have been scanned for viruses and content by security software. The Ministry reserves the right to monitor all e-mail communications through its network.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]