[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
How to design XML to have broad utility and yet also enableefficient application processing?
- From: "Costello, Roger L." <costello@mitre.org>
- To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
- Date: Tue, 19 Nov 2013 10:41:37 +0000
Hi Folks,
Liam Quin wrote:
XML frees your information from being
optimized for, and specific to, any one
program.
An obvious question arises:
What is the right way to design XML?
I believe the answer is:
Design XML so that it reflects (models)
the real world.
But real-world designs (models) may not be well-suited to efficient application processing. A second question arises:
How do we design XML to have broad
utility while still enabling efficient
application processing?
I believe the answer is:
Each application should transform the
XML into a form that enables the
application to process it efficiently.
Do you agree with this?
Is there anything else you would add?
/Roger
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]