<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Things to Avoid in Modular Component Writing for &#8220;Structured Authoring&#8221; and Single-Sourcing</title>
	<atom:link href="http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/</link>
	<description>Technical Writing &#38; Communication Tips, Tutorials, and Trends</description>
	<lastBuildDate>Tue, 21 May 2013 14:39:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/comment-page-1/#comment-8815</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 31 Jan 2011 14:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=10373#comment-8815</guid>
		<description><![CDATA[Sandy, thanks for the feedback and good luck to you with your project! Ugur]]></description>
		<content:encoded><![CDATA[<p>Sandy, thanks for the feedback and good luck to you with your project! Ugur</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy</title>
		<link>http://www.technicalcommunicationcenter.com/2011/01/29/things-to-avoid-in-modular-component-writing-for-structured-authoring-and-single-sourcing/comment-page-1/#comment-8811</link>
		<dc:creator>Sandy</dc:creator>
		<pubDate>Mon, 31 Jan 2011 13:51:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.technicalcommunicationcenter.com/?p=10373#comment-8811</guid>
		<description><![CDATA[Hi Ugur,
Another area where this type of writing is beneficial is with high-level product customization where hardware may be used in one product type, but not in another.  This makes creating dedicated documentation easier.  In fact, I am in the process of converting our legacy documentation over to this format - a challenge to say the least.]]></description>
		<content:encoded><![CDATA[<p>Hi Ugur,<br />
Another area where this type of writing is beneficial is with high-level product customization where hardware may be used in one product type, but not in another.  This makes creating dedicated documentation easier.  In fact, I am in the process of converting our legacy documentation over to this format &#8211; a challenge to say the least.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
