Brian,
a shot in the dark, but since attribute order is important but
apparently can't be guaranteed, could you perhaps stuff the oid
and update time into XML Processing Instructions injected as
preceeding sibblings for each element/object that has an id
you care about?
Doug
On Mon, 24 Mar 2014 01:25:01 PM Brian Aberle wrote:
> Peter said,
> "Basically, it seems you believe that some number of endpoints are
> going to share some deep understanding of the same object model so that you
> can subsequently exploit this shared understanding to enable some
> efficiencies in the XML parsing process?"
>
> Not exactly, it not that they intimately share an object model, they only
> share a key to the data. Every Invoice has an invoice Number. EDI 810
> says so. When modeling that in XML set the oid= to the unique key(in this
> case the invoice number). Attribute order matters,oid must be first
> however, OID IS NEVER REQUIRED. It is as you say - an optimization - it is
> an optional optimization. Nobody will be forced to retrofit into an
> existing design that was depending on the principle that attribute order
> is, was, and always will be insignificant. I can imagine that in some
> existing implementations adding "oid" under the conditions that it be first
> may not be simple, in other cases it's a 1 liner. If "oid" is unknown, the
> data goes through the logic already in place. If "oid" is there then we
> can parse triple fast.