[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: To Normalize or Not to Normalize

• To: "Bullard, Claude L (Len)" <len.bullard@i...>
• Subject: Re: To Normalize or Not to Normalize
• From: Frank Richards <frank@t...>
• Date: Tue, 13 Dec 2005 17:50:07 -0500
• Cc: "'XML Developers List'" <xml-dev@l...>
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE0BB1FCC6@h...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE0BB1FCC6@h...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Well, what I'd hope (probably fruitlessly) to hear was

1.that the denormalization had been done for performance, and could 
likely go away after some benchmarking, and

2. That the names had made sense on an even earlier version of the 
product and had been retained to comfort (now long gone) old timers. 
Thus the names too could be fixed.

I'd settle for hearing that "it was very late that night." or "We 
thought it made sense but found out too late that we were wrong." At 
least then I could do what I wanted with a safe feeling.

If I don't find anything, well, the chance that cleanup will become a 
can of worms is a budget and schedule risk factor. And of course even 
with a solid answer budget and schedule.

Frank



Bullard, Claude L (Len) wrote:

>That is certainly a good first step.   Given the system, 
>that information may or may not exist, may be contradictory, 
>and has to be factored into other intelligence (eg, conversion 
>costs and opportunities).  
>
>What would you be looking for?
>  
>

• Follow-Ups:
  • Re: To Normalize or Not to Normalize
    • From: Tech Rams <techmailing@y...>

• References:
  • RE: To Normalize or Not to Normalize
    • From: "Bullard, Claude L (Len)" <len.bullard@i...>

• Prev by Date: Re: To Normalize or Not to Normalize
• Next by Date: Re: W3C XML Schema public home page tools listing updated
• Previous by thread: RE: To Normalize or Not to Normalize
• Next by thread: Re: To Normalize or Not to Normalize
• Index(es):
  • Date
  • Thread