<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>Book Review: Perl & XML</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Title: Perl & XML</FONT>
<BR><FONT SIZE=2>Authors: Erik T. Ray and Jason McIntosh</FONT>
<BR><FONT SIZE=2>Publisher: O'Reilly</FONT>
<BR><FONT SIZE=2>Published: 2002_04</FONT>
<BR><FONT SIZE=2>ISBN: 059600205X</FONT>
<BR><FONT SIZE=2>Pages: 216</FONT>
</P>
<P><FONT SIZE=2>I was underwhelmed by this text. I like slim books. I particularly look out for well written short technical books that get right to the meat of a subject. This is not one of those books. There is simply not enough value added content in this book above and beyond what is already publicly available. My advice? Read Kip Hampton's articles at <A HREF="http://www.xml.com/pub/au/83" TARGET="_blank">http://www.xml.com/pub/au/83</A> and the module documentation on the Comprehensive Perl Archive Network (<A HREF="http://www.cpan.org" TARGET="_blank">http://www.cpan.org</A>), don't read this book.</FONT></P>
<P><FONT SIZE=2>P&X assumes that the reader is already intimately familiar with both Perl and XML, but not the point where they intersect. As such, the authors frequently punt on XML details. Perhaps it is just me, but I think the problem is that book targets a small or non-existent segment of the market. Most people competent in both Perl and XML won't need an overview of Perl XML modules. They'll already have read the available documentation and be watching the appropriate mailing lists (<A HREF="http://listserv.activestate.com/mailman/listinfo/perl-xml" TARGET="_blank">http://listserv.activestate.com/mailman/listinfo/perl-xml</A>). What's needed is book on XML for Perl programmers.</FONT></P>
<P><FONT SIZE=2>I'll give the book credit as a compendium of the Perl modules available for working with XML. Its not particularly bad, but it is not particularly comprehensive or detailed either. Much of the coverage is dated. And I'll note, as others have, that the example code isn't very practical or useful. A little more information comparing and contrasting the modules covered, where their use is appropriate and the developer communities behind them, would have gone a long way toward making this a better book. </FONT></P>
<BR>
<P><FONT SIZE=2>--</FONT>
<BR><FONT SIZE=2>Garrett Goebel</FONT>
<BR><FONT SIZE=2>IS Development Specialist</FONT>
</P>
<P><FONT SIZE=2>ScriptPro Direct: 913.403.5261</FONT>
<BR><FONT SIZE=2>5828 Reeds Road Main: 913.384.1008</FONT>
<BR><FONT SIZE=2>Mission, KS 66202 Fax: 913.384.2180</FONT>
<BR><FONT SIZE=2>www.scriptpro.com garrett at scriptpro dot com</FONT>
</P>
</BODY>
</HTML>