This directory contains a variety of Web browsers with varying levels of XML support including.
Of these only, Internet Explorer 5.0 for Windows can directly display XML files. The remainder use XML internally for various functions such as Netscape's What's Related or Amaya's MathML support.
This directory contains XML parsers and XSL formatting engines including:
This directory contains the official specification documents for many of the technologies discussed in this book including XML 1.0, Namespaces in XML, and more.
This directory contains complete large examples of XML documents. Some (but not all) of these are based on smaller examples printed in the book. For instance, you'll find complete statistics for the 1998 Major League Baseball season including all players and teams.
This directory contains the full source code of each numbered listing in the XML Bible, exactly as it appears in the book, organized by chapter.
The utilities directory contains a single program —Tidy, compiled for a variety of platforms. Tidy can clean up most HTML files so that they become well-formed XML. Tidy can correct many common problems and warn you about the ones you need to fix yourself. Tidy was written for the W3C by Dave Raggett. The latest version can be found at http://www.w3.org/People/R ggett/tidy.
The pdf directory contains Acrobat PDF files for this entire book. To read them you'll need the free Acrobat reader software which you can get for most major platforms from Adobe's Web site. Feel free to put them on your local hard disk for easy access. And I don't really care if you loan the CD-ROM to some cash-strapped undergrad who finds it cheaper to tie up a school printer for a few hours printing all 1000+ pages rather than spend $49.95 for a printed copy. (If your using your own printer, toner, and paper, it's much cheaper to buy the book.)
However, I would very much appreciate it if you do not place these files on any Web or ftp servers. This includes intranet servers, password protected sites, and other things that aren't meant for the public as large. Most local sites and Intranets are far more exposed to the broader net that most people think. Today's search engines are very good at locating content that was supposed to be hidden. Putting mirror copies of these files around the Web makes it extremely difficult to keep all the files up to date and make sure that search engines find the right copies.