<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Nagelhout, Ed, Julie Staggers and Denise Tillery</title>	<link>http://tc.eserver.org/authors/Nagelhout,_Ed,_Julie_Staggers_and_Denise_Tillery</link>
	<description>A bibliography of works by Nagelhout, Ed, Julie Staggers and Denise Tillery 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>Nagelhout, Ed, Julie Staggers and Denise Tillery</title>
		<link>http://tc.eserver.org/dir/Nagelhout,_Ed,_Julie_Staggers_and_Denise_Tillery</link>
	</image>
	<item>
		<title>Risk Communication, Space, and Findability in the Public Sphere: A Case Study of a Physical and Online Information Center</title>
		<link>http://tc.eserver.org/35003.html</link>
		<guid>http://tc.eserver.org/35003.html</guid>
		<description>This article uses theories of space and findability to analyze a public information center as an example of multi-modal risk communication. The Yucca Mountain Information Center is an informational space created by the Department of Energy to inform the public about the proposed nuclear waste repository planned for Yucca Mountain, Nevada. As a public space, the Center uses fact sheets, posters, and three-dimensional displays to make arguments about the storage of nuclear waste; we argue that the physical space, text, displays, and online space are all elements of risk communication. We offer a new way to read these elements of risk communication and suggest potential opportunities for public agency.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Nagelhout,_Ed,_Julie_Staggers_and_Denise_Tillery.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>