[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Invoices (was Re: XML's greatest culturaladvanta
To clarify a little. I would see this MCE-esque scenario as something like this: If the (XML, eg UBL) invoice contains any eneties marked with a 'MustUnderstand' attribute, say, but my finance app doesn't
have them on, say, a list of entities it already includes properly in its calculations, then it will reject the invoice (or at least mark it as an exception which the application cannot process
with regard to its calculations). Likewise, the application sending the invoice will need to be programmed such that all calculation-sensitive data can be (and is) marked 'MustUnderstand'.
Obviously there will be more to it than that in real life but it's an arhictectural pattern for XML (for business documents at least) I've been after for a long time. It nicely complements and perhaps
completes the architectural pattern of schema subsets. ---- Stephen D Green On 11 April 2013 08:23, Stephen D Green <stephengreenubl@gmail.com> wrote:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|