<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Center for Information Development Management</title>	<link>http://tc.eserver.org/publisher/Center_for_Information-Development_Management</link>
	<description>A listing of works published by Center for Information Development Management 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>Center for Information Development Management</title>
		<link>http://tc.eserver.org/dir/Center_for_Information-Development_Management</link>
	</image>
	<item>
		<title>Linking DITA Topics Through Relationship Tables</title>
		<link>http://tc.eserver.org/32365.html</link>
		<guid>http://tc.eserver.org/32365.html</guid>
		<description>DITA provides a powerful means of linking using relationship tables. The benefit of using a relationship table is the ability to create and maintain links in one place with the map rather than in the topics. Links can be created both between topics of the same information type and between topics of different information types that are not directly related through parent/child relationships. Therefore, the best practice for linking in DITA is to use a relationship table within a map.</description>
	</item>
	<item>
		<title>Wikinomics: What does it Mean for Technical Communication?</title>
		<link>http://tc.eserver.org/31005.html</link>
		<guid>http://tc.eserver.org/31005.html</guid>
		<description>Communication technology has changed the way we think of the workplace. It is no longer a physical location with equipment and personnel coming together in one place. Equipment and people can now be spread across the campus, across the city, across the country, or across the globe. At the same time the authors write that the hierarchical structure of companies is changing along with the geography. Employees no longer need to do specific tasks given to them by a local supervisor, but instead they can all take responsibility for the welfare of the organization. Each and every employee can have his or her ideas for innovation taken seriously. An interesting corollary to this discussion, not brought up by Tapscott and Williams, are benefits of the collaborative workplace, not directly related to the bottom line.</description>
	</item>
	<item>
		<title>Is a Documentation Wiki in your Future?</title>
		<link>http://tc.eserver.org/29554.html</link>
		<guid>http://tc.eserver.org/29554.html</guid>
		<description>If we can solicit user participation in a Web 2.0 knowledge community (a volunter wiki documentation, for example), we might have a powerful means for creating high quality content. But how should this process work?</description>
	</item>
	<item>
		<title>Baumol&apos;s Disease: Is There a Cure?</title>
		<link>http://tc.eserver.org/28183.html</link>
		<guid>http://tc.eserver.org/28183.html</guid>
		<description>Baumol would never have expected in 1967 that a technological innovation like the internet would make it possible to create a sealed-off labor force in a third-world country.</description>
	</item>
	<item>
		<title>Is DITA Going to Tip?</title>
		<link>http://tc.eserver.org/28181.html</link>
		<guid>http://tc.eserver.org/28181.html</guid>
		<description>We seem to be heading in the right direction. The danger is that we keep talking to one another rather than evangelizing to a broader community.</description>
	</item>
	<item>
		<title>Job Postings</title>
		<link>http://tc.eserver.org/28182.html</link>
		<guid>http://tc.eserver.org/28182.html</guid>
		<description>A collection of job postings to answer the needs of information-development managers around the world.</description>
	</item>
	<item>
		<title>Structuring Your Documents for Maximum Reuse</title>
		<link>http://tc.eserver.org/28184.html</link>
		<guid>http://tc.eserver.org/28184.html</guid>
		<description>A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let&apos;s explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents.</description>
	</item>
	<item>
		<title>Making a Business Case for Single Sourcing</title>
		<link>http://tc.eserver.org/14081.html</link>
		<guid>http://tc.eserver.org/14081.html</guid>
		<description>As we learned in the February 2001 issue of Best Practices, in JoAnn Hackos&apos; review of the book, &lt;i&gt;The Balanced Scorecard,&lt;/i&gt; selling innovative ideas to upper management is important. The Balanced Scorecard approach includes a customer perspective, an internal-business-process perspective, and a learning and growth perspective, in addition to the financial perspective. A solid and balanced business case allows you to gain management support and reach your goal.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Center_for_Information-Development_Management.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>