<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Waferbaby</title>	<link>http://tc.eserver.org/authors/Waferbaby</link>
	<description>A bibliography of works by Waferbaby 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>Waferbaby</title>
		<link>http://tc.eserver.org/dir/Waferbaby</link>
	</image>
	<item>
		<title>Omniweb and Standards</title>
		<link>http://tc.eserver.org/25511.html</link>
		<guid>http://tc.eserver.org/25511.html</guid>
		<description>How does Omniweb fare when it comes to web standards? Earlier versions, while highly praised for an elegant user interface and strong support of international character sets, fell drastically short in CSS and W3C DOM support.</description>
	</item>
	<item>
		<title>Slash Forward (Some URLs are Better Than Others)</title>
		<link>http://tc.eserver.org/25506.html</link>
		<guid>http://tc.eserver.org/25506.html</guid>
		<description>A frequently overlooked step in this process is the structure of your links--the actual URLs you’ll be using to point to items on your site. Here are a few handy tips.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Waferbaby.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>