I'm one of the goofuses that still doesn't understand this very well. It's probably because when I ask someone (else) they just repeat in this monotone-just-got-possessed-by-an-alien tone exactly what I've read a hundred times on xml101.com. I hear too much HOW it can be used, rather than the ever-so-convincing: WHY.

yes, i know XML 'describes' data, but so what? all i can see is the cons:

1.) More development time creating the script that organizes the data into an XML page (parsers (serverside and client-side))

2.) Writing DTD's

3.) More development time (everyone is in crunch mode all the time it seems with all the layoffs, do we really need another layer to our already complicated job?)

4.) More bandwidth consumption.... let's see...... we take the data in our SQL/Oracle or Access DB, parse it on the server, and send that out only to be parsed again on the client.... WHAT?

I think my problem is that my boss wanted us to implement this JUST becuase XML is a buzzword... which makes me sick! But more importantly, I just haven't been shown an applicable use for it... a situation perhaps, where it MUST be used.

Also, can someone tell me that XML doesn't have to be used in every project? It's not really that much of a problem (don't see the problem with my current solution yet) solver.... IS IT???