> The thing that's missing, so far, is the structure--who reports to > whom, whether it's a direct report or dotted-line, what the hierarchy > is. You have to have that information to have a usable org chart.
The hierarchy of the XML document itself can provide that information. The only issue I can think of offhand is how you'd handle matrix management, but even that could be modeled strictly by hierarchy, using either duplicate elements or an attribute that lets one element "point" to another. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
