<?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: Designing Your Information Architecture for Content Reuse: Five Best Practices</title>
	<atom:link href="http://thecontentwrangler.com/2008/02/22/designing_your_information_architecture_for_content_reuse_five_best_practic/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2008/02/22/designing_your_information_architecture_for_content_reuse_five_best_practic/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Tue, 16 Mar 2010 01:29:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Sheffield</title>
		<link>http://thecontentwrangler.com/2008/02/22/designing_your_information_architecture_for_content_reuse_five_best_practic/comment-page-1/#comment-273</link>
		<dc:creator>Richard Sheffield</dc:creator>
		<pubDate>Fri, 22 Feb 2008 14:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=369#comment-273</guid>
		<description>&lt;p&gt;Great information! You captured our biggest reuse problem with this statement:
&lt;/p&gt;
&lt;p&gt;
&#8220;To avoid unintentionally changing reused content and unknowingly propagating changes throughout the enterprise, you must have a reuse strategy in place to know who is reusing or consuming what content.&#8221;
&lt;/p&gt;
&lt;p&gt;
Using metatdata, the content in my enterprise can dynamically appear based on various segmentation definitions as well as by country (120 countries served). We have found that infrequent users just refuse to do the due diligence needed to avoid propagating changes to an inappropriate context. Changes that are OK for Gernany might not be OK for France, but they just don&#8217;t understand the complexity since they only make changes once or twice a year. So we have had to pull all content editing baack into a centralized, dedicated staff.
&lt;/p&gt;
&lt;p&gt;
Seems like this is the trend.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Great information! You captured our biggest reuse problem with this statement:
</p>
<p>
&#8220;To avoid unintentionally changing reused content and unknowingly propagating changes throughout the enterprise, you must have a reuse strategy in place to know who is reusing or consuming what content.&#8221;
</p>
<p>
Using metatdata, the content in my enterprise can dynamically appear based on various segmentation definitions as well as by country (120 countries served). We have found that infrequent users just refuse to do the due diligence needed to avoid propagating changes to an inappropriate context. Changes that are OK for Gernany might not be OK for France, but they just don&#8217;t understand the complexity since they only make changes once or twice a year. So we have had to pull all content editing baack into a centralized, dedicated staff.
</p>
<p>
Seems like this is the trend.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
