<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Eisenberg, J. David</title>	<link>http://tc.eserver.org/authors/Eisenberg,_J._David</link>
	<description>A bibliography of works by Eisenberg, J. David in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Eisenberg, J. David</title>
		<link>http://tc.eserver.org/dir/Eisenberg,_J._David</link>
	</image>
	<item>
		<title>Get Ready for HTML 5</title>
		<link>http://tc.eserver.org/35164.html</link>
		<guid>http://tc.eserver.org/35164.html</guid>
		<description>Ready or not, here it comes. Despite the confusion surrounding its evolution, real-world HTML 5 is right around the corner. Longtime ALA contributor J. David Eisenberg returns to get us all up to speed on the markup we’re about to be writing.</description>
	</item>
	<item>
		<title>Validating a Custom DTD</title>
		<link>http://tc.eserver.org/35165.html</link>
		<guid>http://tc.eserver.org/35165.html</guid>
		<description>In his article in this issue, Peter-Paul Koch proposes adding custom attributes to form elements to allow triggers for specialized behaviors. The W3C validator won’t validate a document with these attributes, as they aren’t part of the XHTML specification. This article will show you how to create a custom DTD that will add those custom attributes, and will show you how to validate documents that use those new attributes.</description>
	</item>
	<item>
		<title>Using XML</title>
		<link>http://tc.eserver.org/35166.html</link>
		<guid>http://tc.eserver.org/35166.html</guid>
		<description>The reason that we use XML instead of a specific application is that XML is not just a pretty face, living in isolation from the rest of the computing world. XML is more than a rulebook for generating custom markup languages. It is part of a family of technologies, which, working together, make your XML-based documents very useful indeed. To demonstrate what I mean, I decided to create a new XML-based markup language from scratch, and show what you can do with a document written in that language, using off-the-shelf tools.</description>
	</item>
	<item>
		<title>How to Read W3C Specs</title>
		<link>http://tc.eserver.org/35167.html</link>
		<guid>http://tc.eserver.org/35167.html</guid>
		<description>If you’re working with the latest technology, there may not be any user reference material at all; the only documentation available is the specification. In such a case, learning to read the spec is a necessity, not a luxury. </description>
	</item>
	<item>
		<title>Format Comparison Between ODF and MS XML</title>
		<link>http://tc.eserver.org/27706.html</link>
		<guid>http://tc.eserver.org/27706.html</guid>
		<description>There has been a lot of attention to the legal encumbrances in Microsoft&apos;s new MS XML format. In this article we&apos;ll look at the technical side, and try to show you how the design of these formats affect interoperability. After all, that is the purpose of open standards.</description>
	</item>
	<item>
		<title>Validating a Custom DTD</title>
		<link>http://tc.eserver.org/25260.html</link>
		<guid>http://tc.eserver.org/25260.html</guid>
		<description>This article will show you how to create a custom DTD that will add custom attributes, and will also show you how to validate documents that use those new attributes.</description>
	</item>
	<item>
		<title>Beyond the Browser: Technologies to Watch</title>
		<link>http://tc.eserver.org/20254.html</link>
		<guid>http://tc.eserver.org/20254.html</guid>
		<description>The Internet is not the World Wide Web. So what exactly lies beyond the browser? Eisenberg fearlessly predicts technologies to watch.</description>
	</item>
	<item>
		<title>DOM Design Tricks: Dynamic Text in the Document Object Model</title>
		<link>http://tc.eserver.org/20257.html</link>
		<guid>http://tc.eserver.org/20257.html</guid>
		<description>Be a code wizard … or, just look like one. In Part 3 of the DOM Design Tricks tutorial series, Eisenberg shows us how to dynamically change text on a page. The theory, examples, and scripts will work in Mozilla and IE5.</description>
	</item>
	<item>
		<title>Validating XML: A Pretty Complete Primer</title>
		<link>http://tc.eserver.org/20253.html</link>
		<guid>http://tc.eserver.org/20253.html</guid>
		<description>XML does not come with a spell checker, and will not work if written improperly. Eisenberg teaches you two nifty ways to validate your XML.</description>
	</item>
	<item>
		<title>How to Read (W3C Specs)</title>
		<link>http://tc.eserver.org/20234.html</link>
		<guid>http://tc.eserver.org/20234.html</guid>
		<description>Although they appear maddeningly incomprehensible at first, W3C specifications are actually great sources of information, once you understand their secrets. Learn how to read the specs.</description>
	</item>
	<item>
		<title>Using XML</title>
		<link>http://tc.eserver.org/13586.html</link>
		<guid>http://tc.eserver.org/13586.html</guid>
		<description>XML is not just a pretty face, living in isolation from the rest of the computing world. XML is more than a rulebook for generating custom markup languages. It is part of a family of technologies, which, working together, make your XML-based documents very useful indeed.</description>
	</item>
	<item>
		<title>Transformers: Using XSLT to Transform XML</title>
		<link>http://tc.eserver.org/13221.html</link>
		<guid>http://tc.eserver.org/13221.html</guid>
		<description>XSLT, the Extensible Stylesheet Language Transformation, can convert your XML data to HTML and other friendly formats. Introduce yourself to this snazzy technology.</description>
	</item>
	<item>
		<title>&quot;Forgiving&quot; Browsers Considered Harmful</title>
		<link>http://tc.eserver.org/10207.html</link>
		<guid>http://tc.eserver.org/10207.html</guid>
		<description>Current browsers are very forgiving; they quietly correct or gloss over many common HTML errors. This makes it easy for people to experience the joy of creating their own web pages with a minimum of frustration—if a page displays correctly, then it&apos;s “right.” Unfortunately, by hiding the need for structure that the web will require as it moves towards XHTML and XML, these forgiving browsers have helped create a world of structural HTML illiterates. As long as browsers continue to parse and display HTML that isn&apos;t well-formed or valid, we will never learn the right ways, and we will never get to a structural web.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Eisenberg,_J._David.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>