[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Element ordering
|
I find it to be problematic. In production, code does all the processing, true. But analysts, developers, support staff have to look at samples, write code, document, trouble-shoot issues when they arise, etc. When you combine element
names that donât quite match the data they describe along with elements coming out of logical order (and the various non-standard extensions that vendors add), it becomes difficult even for the most experienced developer to make sense of it all.
From: legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org>
On Behalf Of Othon, Enrique Oh I see. Well no problem, it just looked odd
😊 From:
legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org>
On Behalf Of James E Cabral Enrique, Itâs an artifact (good or bad) of the BOUML plugout that generates schemas in alphabetical order to align with the NIEM reference model. It would be a lot of work to change and I havenât convinced myself the effort is worth it. __ From:
legalxml-courtfiling@lists.oasis-open.org <legalxml-courtfiling@lists.oasis-open.org> on behalf of Othon, Enrique <Enrique.Othon@tylertech.com> Good morning, Quick question, Iâve noticed the ordering on some of the elements seems odd to me. For example, the connected document coming before the lead document, or in some cases other elements in between the lead and connected. Itâs not a big
deal since the xml is being processed by code, just visually looks odd. This is just an observation, Iâm not proposing a change at this time. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]