<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Tyson, Paul H</title>	<link>http://tc.eserver.org/authors/Tyson,_Paul_H</link>
	<description>A bibliography of works by Tyson, Paul H 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>Tyson, Paul H</title>
		<link>http://tc.eserver.org/dir/Tyson,_Paul_H</link>
	</image>
	<item>
		<title>Creating Documents with Structural Markup</title>
		<link>http://tc.eserver.org/24188.html</link>
		<guid>http://tc.eserver.org/24188.html</guid>
		<description>Now we come to the point of actually producing documents using structural markup—either eXtensible Markup Language (XML) or Standard Generalized Markup Language (SGML). Our sequence of topics illustrates the recommended steps to follow when you first implement structural markup: Learn about it and convince yourself and your organization of its benefits, identify your specific goals and expectations, and spend plenty of time selecting or designing your document structures. Only then should you get down to the specifics of how to produce XML or SGML documents. If you simply try to drop in an XML editor to replace your current word processing application, you will be lucky to avoid total disaster.</description>
	</item>
	<item>
		<title>Describing Document Structure, Part 2</title>
		<link>http://tc.eserver.org/21184.html</link>
		<guid>http://tc.eserver.org/21184.html</guid>
		<description>Discusses some different ways of describing your document structure so that both computers and humans know what you mean.</description>
	</item>
	<item>
		<title>Describing Document Structure</title>
		<link>http://tc.eserver.org/19679.html</link>
		<guid>http://tc.eserver.org/19679.html</guid>
		<description>Discusses some different ways of describing your document structure so that both computers and humans know what you mean.</description>
	</item>
	<item>
		<title>Designing Documents</title>
		<link>http://tc.eserver.org/15112.html</link>
		<guid>http://tc.eserver.org/15112.html</guid>
		<description>Explains how to produce documents with good structure, which is essential to the use of structural markup.</description>
	</item>
	<item>
		<title>Anything Worth Writing Is Worth Writing in XML</title>
		<link>http://tc.eserver.org/14780.html</link>
		<guid>http://tc.eserver.org/14780.html</guid>
		<description>Tyson supports the claim of his title with a detailed discussion of three important benefits of XML.</description>
	</item>
	<item>
		<title>Markup Mastery</title>
		<link>http://tc.eserver.org/14773.html</link>
		<guid>http://tc.eserver.org/14773.html</guid>
		<description>Tyson suggests how the principles and practices of structural markup language can make communication more effective.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Tyson,_Paul_H.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>