Title: RE: [xml-dev] Better design: "flatter is better" or "nesting is better" ?





Yes.  Even if it seems exorbitant, that was also a primary reason 

for the success of PDF: storing the document in fixed format. 


Legal requirements for auditability are numerous.  This varies 

by application.  Some are disturbed to see these requirements, 

and I suggest they find other employers because the implications 

are serious for the data base owner.


In a messaging system with queries, it is sometimes the case one 

has to store the transactions, which node issues them, the identity 

of the user (really, the login because identity is much tougher 

to prove), the time of the transaction, the modification made, 

the state prior to the modification, etc.


Those watching the news out of the Beltway last night and this

morning understand why.  Software detects anomalous activity, 

investigation returns a set of suspects, then physical monitoring 

is used to acquire inculpatory evidence prior to indictment and 

arrest.  If the system is well-architected, that happens before 

damage is extensive.  If not, the results are as demonstrated.


len


From: Ken North [mailto:kennorth@s...]


RE: [xml-dev] Better design: "flatter is better" or "nesting is better" ?>> Keep

the audit trail in mind.  Some forms of persistence

are for purely legal reasons.


One time an audience member asked me "Why would you ever want to store the

complete XML document if you're using an SQL database?"


Before I could answer, the person in front of him turned around and said "It's a

legal requirement. I work for the state of Utah and we have to preserve all tax

returns in the form they are received".