<?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: Does single sourcing content work?</title>
	<atom:link href="http://www.onemanwrites.co.uk/2009/01/20/does-single-sourcing-content-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onemanwrites.co.uk/2009/01/20/does-single-sourcing-content-work/</link>
	<description>musings on technical communications</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:40:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: albert tatlock</title>
		<link>http://www.onemanwrites.co.uk/2009/01/20/does-single-sourcing-content-work/comment-page-1/#comment-20740</link>
		<dc:creator>albert tatlock</dc:creator>
		<pubDate>Wed, 03 Mar 2010 21:40:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/?p=284#comment-20740</guid>
		<description>Have a look at Author-it Xtend.  Xtend solves the visibility  problem by popping up suggestions while you type.  Xtend is configurable, and searches all text fragments in the database thus making single sourcing easy.</description>
		<content:encoded><![CDATA[<p>Have a look at Author-it Xtend.  Xtend solves the visibility  problem by popping up suggestions while you type.  Xtend is configurable, and searches all text fragments in the database thus making single sourcing easy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.onemanwrites.co.uk/2009/01/20/does-single-sourcing-content-work/comment-page-1/#comment-10589</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 09 Feb 2009 20:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.onemanwrites.co.uk/?p=284#comment-10589</guid>
		<description>Interesting post.

One suggestion I&#039;ve heard is to separate out the topics that are intended for reuse in a special area, so that writers know it is safe to reuse those topics (or content within those topics) without having the source changed unexpectedly. Because topics in that area could be used in any number of places, writers would know not to edit them without giving serious consideration to the impact changes might have on a variety of different outputs.</description>
		<content:encoded><![CDATA[<p>Interesting post.</p>
<p>One suggestion I&#8217;ve heard is to separate out the topics that are intended for reuse in a special area, so that writers know it is safe to reuse those topics (or content within those topics) without having the source changed unexpectedly. Because topics in that area could be used in any number of places, writers would know not to edit them without giving serious consideration to the impact changes might have on a variety of different outputs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

