ubl-ndrsc — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [ubl-ndrsc] RE: [ubl-lcsc] Newest version of the OO-design position paper.
MHonArc v2.5.2 -->ubl-ndrsc message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ubl-ndrsc] RE: [ubl-lcsc] Newest version of the OO-design position paper.
- From: "CRAWFORD, Mark" <[email protected]>
- To: "'[email protected]'" <[email protected]>,"'[email protected]'" <[email protected]>
- Date: Fri, 23 Aug 2002 09:28:12 -0400
Title: RE: [ubl-lcsc] Newest version of the OO-design position paper.
Gunther,
You wrote -
But
all (and really all) XML instances will be processed by applications and tools
only. Only the designers, developers and support peoples are reading less XML
instances partially. Therefore, we have to think about which kind of
"containers" and "groups" are necessary and efficient for applications (not for
humans).
I
don't think this fits with what we have identified as our core principles. To
wit -
� Legibility - UBL documents should be human-readable and reasonably clear
� Simplicity - The design of UBL must be as simple as possible (but no simpler).
Mark
Hello Joe,I do not know, why we need this high-level containers like "Header, Summary, Party etc.". This is a separation for humans, because all layouts of the hard copies of business documents are divided in this strucute.Kind regards,Gunther
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] — [Date Index] | [Thread Index] | [Month Index] | [List Home]