<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Risk Communication&gt;Environmental&gt;Civic</title>	<link>http://tc.eserver.org/dir/Articles/Risk-Communication/Environmental/Civic</link>
	<description>A listing of the most recently indexed works about Articles and Risk Communication and Environmental and Civic 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;Risk Communication&gt;Environmental&gt;Civic</title>
		<link>http://tc.eserver.org/dir/Articles/Risk-Communication/Environmental/Civic</link>
	</image>
	<item>
		<title>Communicating about Environmental Risk with Stakeholders</title>
		<link>http://tc.eserver.org/19455.html</link>
		<guid>http://tc.eserver.org/19455.html</guid>
		<description>To explore the barriers to successful communication about environmental risks, a research project addressed the following questions: what do people understand about the terminology and the graphics used in risk messages? what sorts of communication modes and timing do people prefer? Surveys and focus groups were conducted in two towns to explore the level and types of risk (e.g leaking gas tanks) with which people are uncomfortable. The findings extend the discoveries of other environmental communication&#xD;researchers: People are confused by regulatory language, they do not trust the government, and they want &apos;true stories,&apos; credible witnesses, and face-to-face interaction with other stakeholders.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Risk-Communication/Environmental/Civic.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>