<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Earley, James M.</title>	<link>http://tc.eserver.org/authors/Earley,_James_M.</link>
	<description>A bibliography of works by Earley, James M. 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>Earley, James M.</title>
		<link>http://tc.eserver.org/dir/Earley,_James_M.</link>
	</image>
	<item>
		<title>Managing Modular Documentation Using a Database</title>
		<link>http://tc.eserver.org/13254.html</link>
		<guid>http://tc.eserver.org/13254.html</guid>
		<description>While implementing a Modular Documentation Method and the development of Responsive Hypermanuals (Lettvin, 1999), concerns were raised as to how to effectively manage the potential explosion of seemingly fractured document components (modules) while maintaining key infrastructure and quality assurance mechanism already in place.&#xD;This paper examines one unique solution to this problem:&#xD;building a web-based database application that manages&#xD;and tracks modules, documents and resources for any&#xD;documentation project. In addition, it has a built-in&#xD;structure for handling a robust documentation process.&#xD;Some advantages and obstacles in developing a modular&#xD;documentation database solution for the web are&#xD;discussed.&#xD;</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Earley,_James_M..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>