<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Sherwood, Kaitlin Duck</title>	<link>http://tc.eserver.org/authors/Sherwood,_Kaitlin_Duck</link>
	<description>A bibliography of works by Sherwood, Kaitlin Duck 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>Sherwood, Kaitlin Duck</title>
		<link>http://tc.eserver.org/dir/Sherwood,_Kaitlin_Duck</link>
	</image>
	<item>
		<title>A Beginner&apos;s Guide to Effective Email</title>
		<link>http://tc.eserver.org/18855.html</link>
		<guid>http://tc.eserver.org/18855.html</guid>
		<description>In a conversation, there is some minimum of shared context. You might be in the same physical location, and even on the phone you have, at minimum, commonality of time. When you generate a document for paper, usually there is some context embedded in the medium: the text is in the proceedings of a conference, written on a birthday card, handed to your professor with a batch of Econ 101 term papers, or something similar.&#xD;&#xD;With email, you can&apos;t assume anything about a sender&apos;s location, time, frame of mind, profession, interests, or future value to you. This means, among other things, that you need to be very, very careful about giving your receivers some context. This section will give specific strategies for doing so.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Sherwood,_Kaitlin_Duck.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>