<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;DocBook&gt;DITA</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/DocBook/DITA</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and DocBook 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;Documentation&gt;DocBook&gt;DITA</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/DocBook/DITA</link>
	</image>
	<item>
		<title>DocBook to DITA Conversion Automation - Improving the Yield?</title>
		<link>http://tc.eserver.org/35041.html</link>
		<guid>http://tc.eserver.org/35041.html</guid>
		<description>With DITA implementations on the rise, and an entrenched DocBook community already in place, the resulting market interest has spurred interest in automated DocBook to DITA conversion. So I would expect offerings of automated DocBook to DITA conversion scripts to emerge in the next 6-10 months. This article addresses the real questions, &quot;What should I expect from automated tools?&quot; and &quot;Will they work for me?&quot; from the viewpoint of live experience with numerous DocBook to DITA conversions. The answers to these questions are not usually obvious.</description>
	</item>
	<item>
		<title>Modular Docs Part 2: DITA vs. DocBook</title>
		<link>http://tc.eserver.org/34486.html</link>
		<guid>http://tc.eserver.org/34486.html</guid>
		<description>When IBM decided to focus on topic-oriented documentation, it created the Darwin Information Typing Architecture (DITA), even though there was already a huge investment in DocBook. Moving to a new architecture was a decidedly non-trivial undertaking--both technically and politically--so it is worth an inquiry as to the reasons for making that move.</description>
	</item>
	<item>
		<title>DocBook versus DITA: Will the Real Standard Please Stand Up?</title>
		<link>http://tc.eserver.org/33968.html</link>
		<guid>http://tc.eserver.org/33968.html</guid>
		<description>More than a decade ago DocBook became the standard for the few brave souls forging ahead in XML publications. DocBook offered a cheaper and more efficient way to publish to multiple formats. Single-sourcing became a reality for hardware and software companies. However, in recent years, many in technical documentation publications have proclaimed DITA as the standard for XML documentation. DITA offered architecture in which to create and publish structured content.&#xD;&#xD;Are these two seemingly rival standards really that different? This article from Teresa Mulvihill answers this question with comparative examples, and allows you, the audience, to decide for yourselves.</description>
	</item>
	<item>
		<title>DocBook or DITA?</title>
		<link>http://tc.eserver.org/32087.html</link>
		<guid>http://tc.eserver.org/32087.html</guid>
		<description>XML is the future. You hear it at every conference you go to, in every magazine you pick up, in every article you read on-line. For technical writers, right now that future comes down to two products—DocBook or DITA. But what exactly are they, and which one should you choose? They are schemas for creating XML.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/DocBook/DITA.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>