<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Information Design&gt;Theory&gt;Web Design</title>	<link>http://tc.eserver.org/dir/Articles/Information-Design/Theory/Web-Design</link>
	<description>A listing of the most recently indexed works about Articles and Information Design and Theory and Web Design 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;Information Design&gt;Theory&gt;Web Design</title>
		<link>http://tc.eserver.org/dir/Articles/Information-Design/Theory/Web-Design</link>
	</image>
	<item>
		<title>Complexity Theory as a Way of Understanding our Role in the World-Wide Web</title>
		<link>http://tc.eserver.org/18171.html</link>
		<guid>http://tc.eserver.org/18171.html</guid>
		<description>Complexity theory offers a way of understanding our role within the World Wide Web. Postulating a rhetorical object based on object-oriented analysis and design, we can harness a number of ideas from complexity theory to gain a new perspective on the Web.&#xD;&#xD;This paper reviews a number of complexity ideas that may help technical communicators grapple with the exponential growth in the volume of inter-related and interacting rhetorical objects on the Web, viewing the rhetorical situation as the result of the law of increasing returns, which has brought us through a phase transition to a new environment, with its own emergent properties, creating new roles for writers, and new work for managers.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Information-Design/Theory/Web-Design.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>