<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;TC&gt;Information Design</title>	<link>http://tc.eserver.org/dir/Articles/TC/Information-Design</link>
	<description>A listing of the most recently indexed works about Articles and TC and Information 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;TC&gt;Information Design</title>
		<link>http://tc.eserver.org/dir/Articles/TC/Information-Design</link>
	</image>
	<item>
		<title>Technical Communication Trends and Ideas</title>
		<link>http://tc.eserver.org/34715.html</link>
		<guid>http://tc.eserver.org/34715.html</guid>
		<description>Technical Communication continues to change as we find new ways to meet the needs of our audiences. I have attended several conferences recently and discussed several of the latest trends with other technical communicators. This article provides a quick list of several of these trends and ideas.</description>
	</item>
	<item>
		<title>Sheep, Chaos, and User Experience</title>
		<link>http://tc.eserver.org/34705.html</link>
		<guid>http://tc.eserver.org/34705.html</guid>
		<description>The people who own the creation, collection, and distribution of content may not be the same people in the very near future. I also believe technical communication is part of information architecture and user experience design. While the technical communication community, specifically many STC members, also work in usability or information design, the culture of the user has changed faster than the culture within the tech comm community.</description>
	</item>
	<item>
		<title>Interview with the Creator of the EServer TC Library</title>
		<link>http://tc.eserver.org/33380.html</link>
		<guid>http://tc.eserver.org/33380.html</guid>
		<description>Tom Johnson has an interview the site&apos;s creator, Geoff Sauer, who explains some of the details behind the site. I found the discussion of their taxonomy particularly interesting, as it&apos;s a problem I&apos;ve struggled with in my own site.</description>
	</item>
	<item>
		<title>STC Body of Knowledge Site Map (draft)</title>
		<link>http://tc.eserver.org/32386.html</link>
		<guid>http://tc.eserver.org/32386.html</guid>
		<description>A draft site map to attempt to represent the field(s) of technical communication within a hierarchical tree diagram.</description>
	</item>
	<item>
		<title>Defining a TC Body of Knowledge</title>
		<link>http://tc.eserver.org/31207.html</link>
		<guid>http://tc.eserver.org/31207.html</guid>
		<description>The Body of Knowledge effort is currently being led by a team of experienced industry and academic STC members. This spring, you will be invited to look at the initial outline of a hierarchy of domains, skills, and knowledge levels. This BoK is yours to develop; the start-up team is simply trying to put together a straw site to start the collaborative effort.</description>
	</item>
	<item>
		<title>Open Access Digital Repositories: An Indian Scenario</title>
		<link>http://tc.eserver.org/28576.html</link>
		<guid>http://tc.eserver.org/28576.html</guid>
		<description>Open access digital repositories give barrier-free access to literature for study and research to users worldwide. They solve the pricing and permission crises for scholarly materials. This paper deals with open access digital repositories in India. The results of the study reveal that the repositories contain both published and unpublished documents, like seminar proceedings, conference papers, theses, dissertations, research reports, books, and so on. The results also point out that open access digital repositories in India are mostly subject specific and commonly use open source information repository software like DSpace, Greenstone Digital Library Software, and GNU EPrints. It is observed that generally the open access digital repositories use OAI-PMH (protocol for metadata harvesting), so that they can be accessed using search tools such as Web search engines, whereas a few don&apos;t use it but provide direct access to their documents through their websites.</description>
	</item>
	<item>
		<title>Participatory Team Process in Information Design</title>
		<link>http://tc.eserver.org/23743.html</link>
		<guid>http://tc.eserver.org/23743.html</guid>
		<description>Information Design often focuses on product over process and ignores the valuable role that technical communicators can play in facilitating a true team design&#xD;activity. In this paper, authors argue for a definition of&#xD;information design that focuses on process and offer a&#xD;proven methodology called Participatory Team Process in&#xD;recognition of its roots in Participatory Design. Authors&#xD;discuss tenets of methodology; spell out the technical&#xD;communicator’s role as facilitator, information manager,&#xD;writer, and editor; and offer three examples of products&#xD;created with the process: a computer interface, safety rule&#xD;book, and curriculum guide.</description>
	</item>
	<item>
		<title>Finding the Schema That Works</title>
		<link>http://tc.eserver.org/20327.html</link>
		<guid>http://tc.eserver.org/20327.html</guid>
		<description>Schema theory says that humans acquire information by building and holding models of that information in their minds. To facilitate learning of new information, writers essentially define a schema for their audience and present new information within that schema. But how do they know that a given schema will work?&#xD;Drawing on examples from the computer software field, this workshop shows that developing a schema to effectively deliver knowledge to an audience requires looking beyond the apparent organization of ideas.</description>
	</item>
	<item>
		<title>Tips and Tricks of Information Management</title>
		<link>http://tc.eserver.org/19466.html</link>
		<guid>http://tc.eserver.org/19466.html</guid>
		<description>Technical communication, when it comes down to basics, is getting the right information across to the right audience, with results. But how do you wade through all&#xD;that ocean of information? How do you sort them,&#xD;separate them, store, and retrieve them at your&#xD;fingertips?&#xD;In this presentation you will learn tools such as L files&#xD;and Mailword, and share other tips and tricks of&#xD;managing information in an open discussion with other&#xD;participants.</description>
	</item>
	<item>
		<title>At the Heart of Information Ecologies: Invisibility and Technical Communication</title>
		<link>http://tc.eserver.org/14222.html</link>
		<guid>http://tc.eserver.org/14222.html</guid>
		<description>The ecological metaphor for technological systems provides a useful supplement to others dealing with the question of human control over technologies. However, it fails to develop adequately its own reliance on communication as the means whereby human values may be embedded in technologies, or to recognize the role of professional communicators in that process.</description>
	</item>
	<item>
		<title>Confessions of a Gardener: A Review of Information Ecologies</title>
		<link>http://tc.eserver.org/14221.html</link>
		<guid>http://tc.eserver.org/14221.html</guid>
		<description>This review of Information Ecologies places the text in the mediating tradition that seeks a middle ground between rigid technological determinism and indifferent value neutrality. The biological metaphors for situated technology use make interesting reading,but the stories may not be compelling evidence that users really can shape technological change from the local level. </description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/TC/Information-Design.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>