<?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: Changing Trends in ECM</title>
	<atom:link href="http://www.apoorv.info/2006/06/03/changing-trends-in-ecm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.apoorv.info/2006/06/03/changing-trends-in-ecm/</link>
	<description>Random Thoughts</description>
	<lastBuildDate>Sat, 31 Jul 2010 10:05:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Rika Ng</title>
		<link>http://www.apoorv.info/2006/06/03/changing-trends-in-ecm/comment-page-1/#comment-131</link>
		<dc:creator>Rika Ng</dc:creator>
		<pubDate>Sat, 17 Jun 2006 16:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/index.php/2006/06/03/changing-trends-in-ecm/#comment-131</guid>
		<description>Lazy? Sounds more like sweeping the rubbish under the carpet. A problem ignored will fester and grow into a monster that bite you in the future (assuming you are still supporting that CMS, haha).

Frankly, some content are just not meant to be sliced and diced into nice and neat fields. Best example: static corporate data that never changes year after year after year. The onus is on the CM implemention team to recognize those very early in the project and to educate the users accordingly, so that everybody can stop wasting time on such low value-added stuff and focus on the more important deliverables.</description>
		<content:encoded><![CDATA[<p>Lazy? Sounds more like sweeping the rubbish under the carpet. A problem ignored will fester and grow into a monster that bite you in the future (assuming you are still supporting that CMS, haha).</p>
<p>Frankly, some content are just not meant to be sliced and diced into nice and neat fields. Best example: static corporate data that never changes year after year after year. The onus is on the CM implemention team to recognize those very early in the project and to educate the users accordingly, so that everybody can stop wasting time on such low value-added stuff and focus on the more important deliverables.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
