<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technical Communication Center &#187; DITA</title>
	<atom:link href="http://www.technicalcommunicationcenter.com/category/dita/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technicalcommunicationcenter.com</link>
	<description>Technical Writing &#38; Communication Tips, Trends &#38; Tutorials by Ugur Akinci, Ph.D.</description>
	<lastBuildDate>Fri, 03 Feb 2012 10:34:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<div id='fb-root'></div>
					<script type='text/javascript'>
						window.fbAsyncInit = function()
						{
							FB.init({appId: null, status: true, cookie: true, xfbml: true});
						};
						(function()
						{
							var e = document.createElement('script'); e.async = true;
							e.src = document.location.protocol + '//connect.facebook.net/en_US/all.js';
							document.getElementById('fb-root').appendChild(e);
						}());
					</script>	
						<item>
		<title>Unspoken Issue for New DITA Writers: High Entry Threshold</title>
		<link>http://www.technicalcommunicationcenter.com/2011/11/01/unspoken-issue-for-new-dita-writers-high-entry-threshold/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/11/01/unspoken-issue-for-new-dita-writers-high-entry-threshold/#comments</comments>
		<pubDate>Tue, 01 Nov 2011 14:44:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[Structured Authoring]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=12358</guid>
		<description><![CDATA[© Ugur Akinci I receive reader letters about DITA (Darwin Information Typing Architecture) these days that more or less ask the same question: how difficult is it for a technical writer to specialize in single-sourcing and structured authoring? Should they learn DITA? And what are the chances of finding employment as a “DITA Writer” these [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/11/01/unspoken-issue-for-new-dita-writers-high-entry-threshold/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Things to Think About Before Converting Legacy Technical Documents to XML</title>
		<link>http://www.technicalcommunicationcenter.com/2011/08/16/things-to-think-about-before-converting-legacy-technical-documents-to-xml/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/08/16/things-to-think-about-before-converting-legacy-technical-documents-to-xml/#comments</comments>
		<pubDate>Tue, 16 Aug 2011 11:44:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=12057</guid>
		<description><![CDATA[© Ugur Akinci Don Bridges, Commercial Tech Docs Manager at dclab.com has good points about converting legacy documents to XML in general, or to a DITA platform in particular. During a webinar he presented last week, a presentation sponsored both by Data Conversion Laboratory (www.dclab.com) and Single-Sourcing Solutions (www.single-sourcing.com), he raised a number of questions [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/08/16/things-to-think-about-before-converting-legacy-technical-documents-to-xml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retail FrameMaker Training</title>
		<link>http://www.technicalcommunicationcenter.com/2011/08/12/retail-framemaker-training/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/08/12/retail-framemaker-training/#comments</comments>
		<pubDate>Fri, 12 Aug 2011 18:14:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=12064</guid>
		<description><![CDATA[© Ugur Akinci Imagine you&#8217;d like to learn Adobe FrameMaker but not in a cover-to-cover &#8220;wholesale&#8221; fashion. Perhaps you&#8217;d like to go &#8220;retail&#8221; and learn one small task at a time. Perhaps you&#8217;d  like to learn just how to author tables, or create footnote elements, or how to edit text. Then OnTrackCBT.com might be what [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/08/12/retail-framemaker-training/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Things That Will Never Change Despite Technological Changes in Technical Writing</title>
		<link>http://www.technicalcommunicationcenter.com/2011/07/27/5-things-that-will-never-change-despite-technological-changes-in-technical-writing/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/07/27/5-things-that-will-never-change-despite-technological-changes-in-technical-writing/#comments</comments>
		<pubDate>Wed, 27 Jul 2011 12:58:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[E-Learning]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=11936</guid>
		<description><![CDATA[© Ugur Akinci The technology of technical writing is changing really fast. But the thing is we don’t really need to keep up with all of it, depending on where we stand in the overall landscape of technical communications. Or let me put it this way: there are things that will never change as long [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/07/27/5-things-that-will-never-change-despite-technological-changes-in-technical-writing/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Best Single Sourcing and Structured Authoring Practices from MadCap Flare</title>
		<link>http://www.technicalcommunicationcenter.com/2011/07/07/best-single-sourcing-and-structured-authoring-practices-from-madcap-flare/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/07/07/best-single-sourcing-and-structured-authoring-practices-from-madcap-flare/#comments</comments>
		<pubDate>Thu, 07 Jul 2011 14:24:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=11872</guid>
		<description><![CDATA[© Ugur Akinci MadCap Flare is one of the better single sourcing and structured authoring software available in the market today, together with AuthorIt, EPublisher, and Adobe FrameMaker. Here are some good advice from MadCap about the best way to go about shifting from a non-structured to a single sourcing platform: 1) Select a small [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/07/07/best-single-sourcing-and-structured-authoring-practices-from-madcap-flare/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Book Review: THE STATE OF STRUCTURED AUTHORING by Alan S. Pringle and Sarah S. O’Keefe</title>
		<link>http://www.technicalcommunicationcenter.com/2011/06/23/technical-book-review-the-state-of-structured-authoring-by-alan-s-pringle-and-sarah-s-o%e2%80%99keefe/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/06/23/technical-book-review-the-state-of-structured-authoring-by-alan-s-pringle-and-sarah-s-o%e2%80%99keefe/#comments</comments>
		<pubDate>Thu, 23 Jun 2011 05:31:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[DITA]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[technical communication]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=11827</guid>
		<description><![CDATA[© Ugur Akinci “Structured authoring” and “single sourcing” have been hot buzz phrases for quite a few years now. If you’re a technical writer, I’m sure you’re either applying these documentation methods in your daily work, getting ready to implement them, or learning about them. I personally am in the last two categories, both still [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/06/23/technical-book-review-the-state-of-structured-authoring-by-alan-s-pringle-and-sarah-s-o%e2%80%99keefe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WebWorks ePublisher &#8212; An Introduction</title>
		<link>http://www.technicalcommunicationcenter.com/2011/06/22/webworks-epublisher-an-introduction/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/06/22/webworks-epublisher-an-introduction/#comments</comments>
		<pubDate>Wed, 22 Jun 2011 17:46:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[MS Word]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=11817</guid>
		<description><![CDATA[© Ugur Akinci WebWorks ePublisher is a single-sourcing and structured authoring application that accepts your FrameMaker, MS Word, or OASIS DITA content and publishes it as Web content, online help, Wiki pages, PDF, and e-books. You can even mix and compile all three types of source materials (FM, Word, DITA) and create a seamless &#8220;hybrid&#8221; [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/06/22/webworks-epublisher-an-introduction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TECHNICAL BOOK REVIEW: &#8220;Practical DITA&#8221; &#8211; A Nuts-and-Bolts Guide to Structured Technical Writing</title>
		<link>http://www.technicalcommunicationcenter.com/2011/04/13/technical-book-review-practical-dita-a-nuts-and-bolts-guide-to-structured-technical-writing/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/04/13/technical-book-review-practical-dita-a-nuts-and-bolts-guide-to-structured-technical-writing/#comments</comments>
		<pubDate>Wed, 13 Apr 2011 13:10:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[DITA]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[single sourcing]]></category>
		<category><![CDATA[technical communication]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=11151</guid>
		<description><![CDATA[© 2011 Ugur Akinci Julio Vasquez has written a great book: Practical DITA. It&#8217;s a tightly-written thin volume (only 100 pages including the Index) that has a lot of nuts-and-bolts type of practical how-to information on DITA &#8212; Darwin Information Typing Architecture. The distinguishing characteristic of this short but comprehensive volume is the way it [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/04/13/technical-book-review-practical-dita-a-nuts-and-bolts-guide-to-structured-technical-writing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>A Source of Potential &#8220;Component&#8221; Conflict in a Multi-User Structured Authoring Environment</title>
		<link>http://www.technicalcommunicationcenter.com/2011/02/04/a-source-of-potential-component-conflict-in-a-multi-user-structured-authoring-environment/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/02/04/a-source-of-potential-component-conflict-in-a-multi-user-structured-authoring-environment/#comments</comments>
		<pubDate>Fri, 04 Feb 2011 12:46:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[XML]]></category>
		<category><![CDATA[Author-It]]></category>
		<category><![CDATA[components]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[single sourcing]]></category>
		<category><![CDATA[technical communication]]></category>
		<category><![CDATA[topics]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=10466</guid>
		<description><![CDATA[© 2011 Ugur Akinci Writing &#8220;components&#8221; instead of &#8220;pages&#8221; is the future of technical communications (if not technical training and e-learning). When it comes to documentation, it really makes sense to &#8220;write once and publish multiple times&#8221;, as the saying goes. And that&#8217;s only possible if we all get used to writing &#8220;components&#8221; (sometimes also [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/02/04/a-source-of-potential-component-conflict-in-a-multi-user-structured-authoring-environment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Things to Avoid in Modular Component Writing for &#8220;Structured Authoring&#8221; and Single-Sourcing</title>
		<link>http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/</link>
		<comments>http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/#comments</comments>
		<pubDate>Sat, 29 Jan 2011 13:22:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[Structured Authoring]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[XML]]></category>
		<category><![CDATA[component writing]]></category>
		<category><![CDATA[single sourcing]]></category>

		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=10373</guid>
		<description><![CDATA[© 2011 Ugur Akinci In true &#8220;structured authoring&#8221; the &#8220;components&#8221; you create (write, draw, etc.) are saved in the database of a Content Management System (CMS). The negative side of this type of &#8220;writing&#8221; is that you lose the local context and formatting. What you&#8217;re creating is not &#8220;only&#8221; an X-type of document but a [...]]]></description>
		<wfw:commentRss>http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

