<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Defending Enterprise Content Management</title>
	<atom:link href="http://wordofpie.com/2007/11/16/defending-enterprise-content-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordofpie.com/2007/11/16/defending-enterprise-content-management/</link>
	<description>Ponderings on Life, the Universe, and Information</description>
	<lastBuildDate>Tue, 15 May 2012 21:39:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Yack</title>
		<link>http://wordofpie.com/2007/11/16/defending-enterprise-content-management/#comment-1762</link>
		<dc:creator><![CDATA[Yack]]></dc:creator>
		<pubDate>Mon, 26 Nov 2007 20:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://wordofpie.wordpress.com/2007/11/16/defending-enterprise-content-management/#comment-1762</guid>
		<description><![CDATA[The promise of ECM is only truly realized when a customer is trying to solve a multi-channel content use, re-use and distribution problem. Just because they happen to have disparate WCM, Document Management, Records Management, etc needs, doesn&#039;t mean they need a singular ECM platform. That being said, a single platform can provide the value of (1) single throat to choke (2) simpler administration if the platform is really unified and (3) open opportunities for reuse that the customer may not have even dreamed of in their current world.]]></description>
		<content:encoded><![CDATA[<p>The promise of ECM is only truly realized when a customer is trying to solve a multi-channel content use, re-use and distribution problem. Just because they happen to have disparate WCM, Document Management, Records Management, etc needs, doesn&#8217;t mean they need a singular ECM platform. That being said, a single platform can provide the value of (1) single throat to choke (2) simpler administration if the platform is really unified and (3) open opportunities for reuse that the customer may not have even dreamed of in their current world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pie</title>
		<link>http://wordofpie.com/2007/11/16/defending-enterprise-content-management/#comment-1608</link>
		<dc:creator><![CDATA[Pie]]></dc:creator>
		<pubDate>Wed, 21 Nov 2007 15:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://wordofpie.wordpress.com/2007/11/16/defending-enterprise-content-management/#comment-1608</guid>
		<description><![CDATA[Nagu, addressing your points...

- True.  However I am working on that &lt;a href=&#039;http://wordofpie.wordpress.com/2007/08/09/redefining-enterprise-content-management/&#039; rel=&quot;nofollow&quot;&gt;definition&lt;/a&gt;.  Too often, people think that ECM + Web 2.0 = ECM 2.0.  That can&#039;t be the case.  That is just advanced UI.  Another post on this soon.

- The point here is that eRoom, Web Publisher, and other Documentum UIs should be able to connect to the Repository through DFS and not DFC.  The Content Applications &lt;a href=&#039;http://wordofpie.wordpress.com/2007/08/22/the-ecm-wsdl-discussion-leading-to-more/&#039; rel=&quot;nofollow&quot;&gt;shouldn&#039;t be tied to a specific ECM Platform&lt;/a&gt;.  

- I am referring to adding wiki and blog support.  Easier linking and an updated look and feel as well.  This is for user acceptance and ease of use.]]></description>
		<content:encoded><![CDATA[<p>Nagu, addressing your points&#8230;</p>
<p>- True.  However I am working on that <a href='http://wordofpie.wordpress.com/2007/08/09/redefining-enterprise-content-management/' rel="nofollow">definition</a>.  Too often, people think that ECM + Web 2.0 = ECM 2.0.  That can&#8217;t be the case.  That is just advanced UI.  Another post on this soon.</p>
<p>- The point here is that eRoom, Web Publisher, and other Documentum UIs should be able to connect to the Repository through DFS and not DFC.  The Content Applications <a href='http://wordofpie.wordpress.com/2007/08/22/the-ecm-wsdl-discussion-leading-to-more/' rel="nofollow">shouldn&#8217;t be tied to a specific ECM Platform</a>.  </p>
<p>- I am referring to adding wiki and blog support.  Easier linking and an updated look and feel as well.  This is for user acceptance and ease of use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nagu</title>
		<link>http://wordofpie.com/2007/11/16/defending-enterprise-content-management/#comment-1522</link>
		<dc:creator><![CDATA[Nagu]]></dc:creator>
		<pubDate>Mon, 19 Nov 2007 05:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://wordofpie.wordpress.com/2007/11/16/defending-enterprise-content-management/#comment-1522</guid>
		<description><![CDATA[Hi, the equation ECM + SOA = ECM 2.0  looks impressive.however since there is no unanimity in ECM definition,i&#039;m not sure equations make things more clear at this point of time.

Regarding EMC making DCTM DFS oriented,consultants long before have started making web services out of DFC.m not sure how much value addition dctm 6 would be.

&quot;Spend money to make eRoom part of the Web 2.0 world&quot; eroom is for an enterprise.whats the point of making it web 2.0 product?]]></description>
		<content:encoded><![CDATA[<p>Hi, the equation ECM + SOA = ECM 2.0  looks impressive.however since there is no unanimity in ECM definition,i&#8217;m not sure equations make things more clear at this point of time.</p>
<p>Regarding EMC making DCTM DFS oriented,consultants long before have started making web services out of DFC.m not sure how much value addition dctm 6 would be.</p>
<p>&#8220;Spend money to make eRoom part of the Web 2.0 world&#8221; eroom is for an enterprise.whats the point of making it web 2.0 product?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

