<?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;Professionalism</title>	<link>http://tc.eserver.org/dir/Articles/Information-Design/Professionalism</link>
	<description>A listing of the most recently indexed works about Articles and Information Design and Professionalism 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>Articles&gt;Information Design&gt;Professionalism</title>
		<link>http://tc.eserver.org/dir/Articles/Information-Design/Professionalism</link>
	</image>
	<item>
		<title>Being Shallow</title>
		<link>http://tc.eserver.org/28918.html</link>
		<guid>http://tc.eserver.org/28918.html</guid>
		<description>Information Architects are often put on the defensive by spears flung by brethren in related disciplines. In taking the accusations seriously and accepting truths within them, Grant Campbell reveals greatest strengths in shallowness, insularity, and being &apos;relegated&apos; to history.</description>
	</item>
	<item>
		<title>Defining the Damn Thing</title>
		<link>http://tc.eserver.org/23871.html</link>
		<guid>http://tc.eserver.org/23871.html</guid>
		<description>Defining information architecture is a reccuring theme in all IA forums, and frequently leads to re-naming efforts as well, from information therapist to experience designer. This page is dedicated to that ongoing struggle.</description>
	</item>
	<item>
		<title>(Not) Defining the Damn Thing</title>
		<link>http://tc.eserver.org/21372.html</link>
		<guid>http://tc.eserver.org/21372.html</guid>
		<description>Discussions of how we should label ourselves and define our work are like flu epidemics. They break out from time to time, follow a fairly predictable course, and often make us want to barf.</description>
	</item>
	<item>
		<title>What&apos;s in a Name? Or, What Exactly Do We Call Ourselves?</title>
		<link>http://tc.eserver.org/21306.html</link>
		<guid>http://tc.eserver.org/21306.html</guid>
		<description>Defining the audience for Boxes and Arrows sparked the same heated discussion as the community-at-large about what exactly do we call ourselves?</description>
	</item>
	<item>
		<title>What&apos;s In A Name?</title>
		<link>http://tc.eserver.org/20927.html</link>
		<guid>http://tc.eserver.org/20927.html</guid>
		<description>In defining a field, each person seems to look at the world and place themselves in the center of the circle, giving their specialty top billing as the summation of all the others. What exactly is gained by this political one-upmanship? In the face of this inflation, I find myself pulling back to the simplest craft title I can find. Or avoiding titles altogether.</description>
	</item>
	<item>
		<title>We Are All Connected: The Path from Architecture to Information Architecture</title>
		<link>http://tc.eserver.org/20877.html</link>
		<guid>http://tc.eserver.org/20877.html</guid>
		<description>Information architecture has a great deal to do with traditional architecture—especially in the ability of each discipline to plan and connect various important elements together.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Information-Design/Professionalism.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>