[
Lists Home |
Date Index |
Thread Index
]
* Roger L. Costello <costello@mitre.org> [2005-01-29 12:20]:
> Hi Folks,
>
> Below I propose a few XML design principles. I am interested in hearing
> your thoughts on them, i.e., do you agree or disagree with them?
>
> Which is Better Design?
>
> Suppose that I have data about a grape vineyard. Below I show two lots on
> the vineyard, and a picker on one of the lots. I show two ways of designing
> the data. Which design is better?
>
> XML Design Principle #3
> Minimize the amount of nesting you use.
> Nested data is tightly coupled and uses implicit relationships, both of
> which are bad.
> Flat data is good data!
> Flat data is loosely coupled and promotes the use of explicit relationships,
> both of which are good.
Flat data is good data?
How do you go about creating an org chart then? Imagine I've
gone an removed the person's name, address, and such...
<organization>
<person id="john">
<person id="sue">
<person id="stephan"/>
</person>
<person id="shrinivas">
<person id="daniel"/>
</person>
</person>
</organization>
Is that a vaild use of heirarchy to whatever depth?
--
Alan Gutierrez - alan@engrm.com
|
