The XSL Challenge

Friday May 21st, 1999

C. David Tallman has news of an interesting article at In it, Michael Leventhal of CITEC (the group creating DocZilla) takes off the gloves and challenges XSL to best XML/CSS/DOM in a competition of functionality/usability in the web application space. Interestingly, Mozilla plays an important role in the contest. From

"Anything XSL can do in the Web environment, I can do better using technologies supported by current W3C Recommendations. Of course, what is 'meaningful' in the Web environment is open to a variety of interpretations. Therefore, the subject of the challenge should be one that the XSL camp and I agree is meaningful. I am also ready to make this bet a little bit more than an academic exercise. If I lose, I will pledge that I, and my crack mozilla development team, will assist in implementing XSL in the mozilla open source project. If my opponents lose they will agree to desist from XSL advocacy, vote against an XSL Recommendation if they are members of the W3C, and will join me in calling for full, flawless, and unequivocal vendor support of CSS1 and CSS2, DOM Level 1, and XML 1.0 as the very first and top priority of the web community."

#15 Re:The XSL Challenge

by Heikki Toivonen <>

Monday May 24th, 1999 2:00 AM

You are replying to this message

Just a reminder: if you always convert yor XML documents on the server to HTML, the user loses the benefits of smart markup. Sure, you can send a query to the server and let it search in XML and again return results in HTML, but one of the reasons why XML was created in the first place was to enable smart searches on the client (and thus reducing network traffic and load on the server).

It is true that we do not have too many options for browsers capable of handling XML. And I think Michael is right on target for blaming XSL for some of the delay.