On Wednesday, March 26, 2003, at 12:45 PM, Richard O. Hammer wrote:
Kenneth Sizer wrote:Not to play devil's advocate, but...
Why is "Ideally all data, including that for static pages, is XML"?? What business/technical need is met by using XML for simple, static pages?
(and, in reality, "marketing says customers will think that's cool" is often a valid business need)
This touches something that is still an issue for me. I can't see why XML has become so broadly used.
Hey, I've got a great idea! Let's store all of our data in *text files*! It'll be a great leap forward :-)
Maybe I'm just getting too old to learn new tricks, but I too don't see the point of XML beyond using it for file storage like with OpenOffice. If an industry can come up with a standard definition for XML for use with its particular type of data that's nice, but beyond that.
What's the point of using XML on a web-based project? Data is usually in a database, and if you need an abstraction layer on top of that, objects work just fine, wether its EJB or whatever abstraction you choose to use. Adding XML seems to not only add complexity and massive overhead, but doesn't seem to give you anything in return. The much vaulted separation of data from presentation you get with XML stylesheets has been around more than two decades in other architectures from XML came along, thank you very much.
________________________________________________________________________ _________
Run, run, run, as fast as you can. You can't catch me, I'm the stinky cheese man!
-- michael at czeiszperger dot org, Chapel Hill, NC
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
