<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Business Communication&gt;Collaboration&gt;Genre</title>	<link>http://tc.eserver.org/dir/Articles/Business-Communication/Collaboration/Genre</link>
	<description>A listing of the most recently indexed works about Articles and Business Communication and Collaboration and Genre 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>Articles&gt;Business Communication&gt;Collaboration&gt;Genre</title>
		<link>http://tc.eserver.org/dir/Articles/Business-Communication/Collaboration/Genre</link>
	</image>
	<item>
		<title>Forming Perceptions of Entrepreneurial Discourse: The Effectiveness of Oral or Transcribed Communication</title>
		<link>http://tc.eserver.org/26583.html</link>
		<guid>http://tc.eserver.org/26583.html</guid>
		<description>This paper explores the possibility that trained business communication professionals might perceive differentially the quality of the identical entrepreneurial presentations, depending on whether they are in audio or print form.  By conducting a comparative analysis of heard and read &#xD;versions of these speeches, we uncovered evidence which frames the following discourse.  &#xD;Results point to the variables which shape either (1) oral communication with an immediately- &#xD;present audience, or (2) written transcripts with a distanced or imagined set of readers.  This has &#xD;aided us in identifying the funding for new ventures.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Business-Communication/Collaboration/Genre.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>