<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Stratman, James F.</title>	<link>http://tc.eserver.org/authors/Stratman,_James_F.</link>
	<description>A bibliography of works by Stratman, James F. in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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>Stratman, James F.</title>
		<link>http://tc.eserver.org/dir/Stratman,_James_F.</link>
	</image>
	<item>
		<title>Legal Communication in Technical Communication Programs: Worth Thinking About?</title>
		<link>http://tc.eserver.org/21549.html</link>
		<guid>http://tc.eserver.org/21549.html</guid>
		<description>What, if anything, should technical communication programs teach their students about the nature of law and the production of legal discourse? When is technical writing also legal writing, and vice versa; when is legal writing (really) technical? Are there distinctions worth maintaining and dissolving here? Do lawyers&apos; relationships to, and problems with, legal writing contexts and processes parallel in important ways technical writers&apos; relationships to, and problems with, technical writing contexts and processes? If they do, is a conversation between the disciplines worth institutionalizing, at least experimentally, in each other&apos;s programs?</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Stratman,_James_F..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>