[MACCAWS] XHTML --> XML: Business Pros?

One thing we are going to have to tackle is telling our "bosses" why 
XHTML is a Good Thing(TM). 

I wondered if we could brainstorm a bit on this, not only for 
ourselves, but since I may have to make this case soon where I am 
employed.

So we know the basics are:

1. XHTML is good clean markup. (That's great, but my boss won't jump 
up and down about it - he doesn't give a rat's pa-tootie that its 
well formed.)

2. valid XHTML is valid XML. Ok, great - sounds good - but WHY is 
this good for my BOSS? What are some reasons I can give the business 
guy to move them in that direction? You can parse XHTML with an xml 
parser right? So what? What does that get him? That's what we will be 
asked. In effect, what is the ROI for XHTML? (eek, acronym pain)

3. XHTML is cleaner to maintain. Certainly we can say, this reduces 
maintenance costs.

Its a start..what would you add?


tom