|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Better design: "flatter is better" or "nesting is better"
It was persistent while you were working on it. Then you disposed of it. If you don't like the word "persistent", then come up with a different term. Perhaps "active"? Whatever... Your XML won't care, but both you and your application probably should because the data model impacts performance and efficiency. Our core question here is focused on proper modeling of the XML structures -- whether they should be normalized or not. If the XML is transient, then it probably ought to be normalized, because it offers the best optimization for transformation. If the XML is persistent, then application requirements ought to dictate the need for normalization. If the XML will be operated on by only one application, then the structure probably ought to be optimized for that specific application. If the XML will be operated on by more than one application, then the structure probably ought to be normalized. Anne On 10/4/05, Peter Hunsberger <peter.hunsberger@g...> wrote: On 10/4/05, Anne Thomas Manes <atmanes@g...> wrote:
|
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
|
|||||||||

Cart








