[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: The markup minimalist
You need to establish your scenario first. * If you want to leave the responsibility for ordering and grouping and traversing data to the developer, then arrangements closer to 3NF may be appropriate. * If you have a target algorithm or expected existing system, then arranging your data to fit them may be best. Ignore the sneers of abstract modelers. * If you have a strong idea of the usual patterns of access (e.g. documents), then rich hierarchical markup may be best: some nosql systems do this. * If you dont want to penalize any application or developer, then you are in the scenario-free world of voodoo pronouncements. You think you are free, but you will just be ruled by slogans and know-alls and informed guesses. I expect a viable data format needs to be at least good for something, at least one thing, rather than designed to be good for nothing. But a caution about flatness: when people have a flat format but need structure, they lower the structure into names: you get long structured names and ids with many segments and dots and minus: out of reach of most validation. Data has structure, and we can decide whether it is appropriate to expose or bury that structure. cheers On 02/11/2014 1:32 AM, "Costello, Roger L." <costello@mitre.org> wrote:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|