<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>XML.org</title>	<link>http://tc.eserver.org/publisher/XML.org</link>
	<description>A listing of works published by XML.org 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>XML.org</title>
		<link>http://tc.eserver.org/dir/XML.org</link>
	</image>
	<item>
		<title>Introduction to the DITA Maturity Model</title>
		<link>http://tc.eserver.org/35012.html</link>
		<guid>http://tc.eserver.org/35012.html</guid>
		<description>One of DITA’s most attractive features is its support for incremental adoption: you can adopt DITA quickly and easily using a subset of its capabilities, and then add investment over time as your content strategy evolves and expands.&#xD;However, this incremental continuum has also resulted in confusion, as communities at different stages of adoption claim radically different numbers for cost of migration and return on investment.&#xD;&#xD;The DITA Maturity Model addresses this confusion by dividing DITA adoption into six levels, each with its own required investment and associated return on investment. You can assess your own capabilities and goals relative to the model and choose the appropriate initial adoption level for your needs and schedule.</description>
	</item>
	<item>
		<title>Improving Relationships in Relationship Tables</title>
		<link>http://tc.eserver.org/34720.html</link>
		<guid>http://tc.eserver.org/34720.html</guid>
		<description>While topic relationships can be stored in the topics themselves, as products evolve and user interfaces change, a topic that was required for release 1.0 of a product may no longer be needed in release 2.3. If related topics are maintained at the topic level, removing a topic that is no longer part of the system may involve modifying the related topics of a dozen different DITA files.</description>
	</item>
	<item>
		<title>Evaluating DITA-Enabled Content Management Systems</title>
		<link>http://tc.eserver.org/34723.html</link>
		<guid>http://tc.eserver.org/34723.html</guid>
		<description>This presentation describes how authoring DITA topics and managing &#xD;those topics in a content management system (CMS) will contain &#xD;translation costs while improving overall information quality. This is not a recommendation for any particular product. It is a guide to how one group built their candidate list and computes return on investment.</description>
	</item>
	<item>
		<title>The Xquery Language and the DITA Open Toolkit</title>
		<link>http://tc.eserver.org/34275.html</link>
		<guid>http://tc.eserver.org/34275.html</guid>
		<description>Xquery is a powerful query language designed specifically for XML content. It can be used for querying, processing, manipulation, and transformation of xml content. This presentation demonstrates how Xquery can be used to add to the feature set of the Dita Open Toolkit by introducing automatic glossary processing.</description>
	</item>
	<item>
		<title>Myths About Technical Writing</title>
		<link>http://tc.eserver.org/31890.html</link>
		<guid>http://tc.eserver.org/31890.html</guid>
		<description>When you start working with DITA, there are some things that you may feel you need for traditional reasons that you won&apos;t find in DITA. Before you try to modify or specialize DITA, it may be worthwhile to rethink some technical writing practices that are outdated and not recommended today.</description>
	</item>
	<item>
		<title>The Wisdom of Crowds Meets the Wisdom of Authors: How XML Enables the Semantic Web</title>
		<link>http://tc.eserver.org/31865.html</link>
		<guid>http://tc.eserver.org/31865.html</guid>
		<description>Combining semantic markup with a granular authoring approach like DITA holds a lot of promise for content creators and consumers alike. Content becomes easy to define and even easier to discover. The combination also holds a lot of promise for the future of the Semantic Web itself. In fact, creating the Semantic Web might be as easy as authoring content in DITA.</description>
	</item>
	<item>
		<title>DITA Knowledge Base</title>
		<link>http://tc.eserver.org/27048.html</link>
		<guid>http://tc.eserver.org/27048.html</guid>
		<description>The DITA Knowledge Base pages provide a reliable basis of technical and educational information on the standard.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/XML.org.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>