<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Content Management&gt;XML&gt;DITA</title>	<link>http://tc.eserver.org/dir/Articles/Content-Management/XML/DITA</link>
	<description>A listing of the most recently indexed works about Articles and Content Management and XML and DITA 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;Content Management&gt;XML&gt;DITA</title>
		<link>http://tc.eserver.org/dir/Articles/Content-Management/XML/DITA</link>
	</image>
	<item>
		<title>Easy Command Line Processing with the DITA Open Toolkit</title>
		<link>http://tc.eserver.org/35046.html</link>
		<guid>http://tc.eserver.org/35046.html</guid>
		<description>The DITA Open Toolkit can transform your DITA files into a wide variety of output types. When you first install it, it&apos;s easy to get the impression that you need to know Ant well to use it, but you can pack most of its available options into a single Java™ command line.</description>
	</item>
	<item>
		<title>DITA Is Not the Answer</title>
		<link>http://tc.eserver.org/31749.html</link>
		<guid>http://tc.eserver.org/31749.html</guid>
		<description>Single sourcing is good, I’m sure most of us can agree on that, but I’ve recently been wondering if perhaps DITA isn’t quite good enough?</description>
	</item>
	<item>
		<title>Striving for Success in DITA Conversion - A Quick Reference</title>
		<link>http://tc.eserver.org/31750.html</link>
		<guid>http://tc.eserver.org/31750.html</guid>
		<description>Planning your conversion is always helpful, and should be part of your overall content strategy review.</description>
	</item>
	<item>
		<title>Dynamic Content Delivery using DITA</title>
		<link>http://tc.eserver.org/30232.html</link>
		<guid>http://tc.eserver.org/30232.html</guid>
		<description>This whitepaper defines a new publishing paradigm, which we will call dynamic content delivery. Dynamic delivery changes the rules, putting the reader in charge of what content is important and how it should be packaged. It transforms publishing to an audience of many to publishing to an audience of one. </description>
	</item>
	<item>
		<title>Wikis, Docs, and the Reuse Proposition</title>
		<link>http://tc.eserver.org/30229.html</link>
		<guid>http://tc.eserver.org/30229.html</guid>
		<description>The Darwin Informaton Typing Architecture (DITA) is an XML-based document format that was designed from the ground up for reuse. It rocks. Content Managment Systms (CMSes) are designed to hold XML data. So in theory, a CMS system that lets you edit like a Wiki would be everything you need. But getting a system like that to work is a pretty tricky proposition. </description>
	</item>
	<item>
		<title>Streamlining Content Creation and Publishing with XMetaL and DITA</title>
		<link>http://tc.eserver.org/30120.html</link>
		<guid>http://tc.eserver.org/30120.html</guid>
		<description>To streamline the product documentation process, many technical publication teams are moving to Darwin Information Typing Architecture (DITA). Learn best practices for applying this information model, and hands-on techniques for improved content creation and publishing with JustSystems XMetaL.</description>
	</item>
	<item>
		<title>Lessons From The Trenches: DocZone.com Is Doing It With DITA</title>
		<link>http://tc.eserver.org/27891.html</link>
		<guid>http://tc.eserver.org/27891.html</guid>
		<description>Interviews Chris Hill of DocZone.com and explores the lessons his firm learned while implementing the Darwin Information Typing Architecture (DITA).</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Content-Management/XML/DITA.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>