<?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 for Observing Content Management</title>
	<atom:link href="http://ecmobservations.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://ecmobservations.wordpress.com</link>
	<description>A regular delve into the world of Information Management</description>
	<lastBuildDate>Fri, 13 Nov 2009 21:23:08 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Future of ECM by EMC Momentum 2009 &#8211; Keynote &#171; Observing Content Management</title>
		<link>http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-198</link>
		<dc:creator>EMC Momentum 2009 &#8211; Keynote &#171; Observing Content Management</dc:creator>
		<pubDate>Fri, 13 Nov 2009 21:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-198</guid>
		<description>[...] Centric, and a move from Static Placement to Dynamic Movement, see my earlier post on the Future of ECM to see my views on [...]</description>
		<content:encoded><![CDATA[<p>[...] Centric, and a move from Static Placement to Dynamic Movement, see my earlier post on the Future of ECM to see my views on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on EMC Momentum 2009 &#8211; Day 1 Part 1 by Peter</title>
		<link>http://ecmobservations.wordpress.com/2009/11/10/emc-momentum-2009-day-1-part-1/#comment-196</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 12 Nov 2009 12:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/11/10/emc-momentum-2009-day-1-part-1/#comment-196</guid>
		<description>Congratulations to the award! It would have been great being in Athens, but hopefully next time...</description>
		<content:encoded><![CDATA[<p>Congratulations to the award! It would have been great being in Athens, but hopefully next time&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Future of ECM by Julian Wraith &#124; The Future of Content Management, the follow up</title>
		<link>http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-190</link>
		<dc:creator>Julian Wraith &#124; The Future of Content Management, the follow up</dc:creator>
		<pubDate>Mon, 14 Sep 2009 08:08:17 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-190</guid>
		<description>[...] Lee Smith [...]</description>
		<content:encoded><![CDATA[<p>[...] Lee Smith [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Future of ECM by Julian Wraith</title>
		<link>http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-187</link>
		<dc:creator>Julian Wraith</dc:creator>
		<pubDate>Tue, 08 Sep 2009 08:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-187</guid>
		<description>Great to see a post from the ECM angle (most of us peeps seem to like WCM too much). The difference between ECM and WCM is interesting when we talk about the future and ownership of the content. 

PS I found the post by chance and have added it to my post. If you want to tag it for google then add the following MD5 tag to the post: 6f82f1d2683dc522545efe863e5d2b73</description>
		<content:encoded><![CDATA[<p>Great to see a post from the ECM angle (most of us peeps seem to like WCM too much). The difference between ECM and WCM is interesting when we talk about the future and ownership of the content. </p>
<p>PS I found the post by chance and have added it to my post. If you want to tag it for google then add the following MD5 tag to the post: 6f82f1d2683dc522545efe863e5d2b73</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Future of ECM by Larry Cannell</title>
		<link>http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-186</link>
		<dc:creator>Larry Cannell</dc:creator>
		<pubDate>Mon, 07 Sep 2009 21:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-186</guid>
		<description>I agree. Not only are &quot;folders&quot; an unnecessary distraction but I also think the paradigm of &quot;files&quot; is also holding us back. More about this in a post I wrote a couple of years ago called &quot;I Hate Files&quot;: http://enterprise2blog.com/2007/10/enterprise2blog_266/</description>
		<content:encoded><![CDATA[<p>I agree. Not only are &#8220;folders&#8221; an unnecessary distraction but I also think the paradigm of &#8220;files&#8221; is also holding us back. More about this in a post I wrote a couple of years ago called &#8220;I Hate Files&#8221;: <a href="http://enterprise2blog.com/2007/10/enterprise2blog_266/" rel="nofollow">http://enterprise2blog.com/2007/10/enterprise2blog_266/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Future of ECM by Lee Smith</title>
		<link>http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-185</link>
		<dc:creator>Lee Smith</dc:creator>
		<pubDate>Mon, 07 Sep 2009 20:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-185</guid>
		<description>In that case then my apologies, and yes it would appear the visions are closer than I stated. Some of these ideas should be achievable sooner rather than later!</description>
		<content:encoded><![CDATA[<p>In that case then my apologies, and yes it would appear the visions are closer than I stated. Some of these ideas should be achievable sooner rather than later!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Future of ECM by Pie</title>
		<link>http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-184</link>
		<dc:creator>Pie</dc:creator>
		<pubDate>Mon, 07 Sep 2009 20:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2009/09/07/future-of-ecm-2/#comment-184</guid>
		<description>Thanks for the shout out.  I don&#039;t think that the future is one repository.  It will just be invisible to the user.  The search/access points will do the work after you issue your search.  The key central piece in my vision was Identity Management.

Your vision acts in concert with mine.  Yours is probably 5-10 years before mine is realized.  It is a great vision that our kids will deliver.

-Pie</description>
		<content:encoded><![CDATA[<p>Thanks for the shout out.  I don&#8217;t think that the future is one repository.  It will just be invisible to the user.  The search/access points will do the work after you issue your search.  The key central piece in my vision was Identity Management.</p>
<p>Your vision acts in concert with mine.  Yours is probably 5-10 years before mine is realized.  It is a great vision that our kids will deliver.</p>
<p>-Pie</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SaaS and ECM by Lee Smith</title>
		<link>http://ecmobservations.wordpress.com/2007/11/20/saas-and-ecm/#comment-178</link>
		<dc:creator>Lee Smith</dc:creator>
		<pubDate>Tue, 30 Jun 2009 20:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2007/11/20/saas-and-ecm/#comment-178</guid>
		<description>Interesting to get a response to this now; especially given the advent of CMIS. I think CMIS will be a big influence on these scenarios, but as you say the ECM vendors will also need to change their pricing models. I know of other people who have have looked at establishing a Cloud for the ECM Infrastructure service and with some imaginative thinking they believe that this can be profitable.</description>
		<content:encoded><![CDATA[<p>Interesting to get a response to this now; especially given the advent of CMIS. I think CMIS will be a big influence on these scenarios, but as you say the ECM vendors will also need to change their pricing models. I know of other people who have have looked at establishing a Cloud for the ECM Infrastructure service and with some imaginative thinking they believe that this can be profitable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SaaS and ECM by Andrew Smith @onedegree</title>
		<link>http://ecmobservations.wordpress.com/2007/11/20/saas-and-ecm/#comment-177</link>
		<dc:creator>Andrew Smith @onedegree</dc:creator>
		<pubDate>Tue, 30 Jun 2009 11:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/2007/11/20/saas-and-ecm/#comment-177</guid>
		<description>Of course this can work. If your ECM platform provides a full XML Web Services API then there is no reason why you cant integrate a SaaS ECM platform with your applications installed locally......

The real question is here, is there any benefit? Especially when many ECM vendors provide concurrent licensing models in any case....After spending quite sometime looking at savings SaaS can provide, if youre storing a lot of content in the cloud, the savings just arent there, if anything your costs will probably increase....</description>
		<content:encoded><![CDATA[<p>Of course this can work. If your ECM platform provides a full XML Web Services API then there is no reason why you cant integrate a SaaS ECM platform with your applications installed locally&#8230;&#8230;</p>
<p>The real question is here, is there any benefit? Especially when many ECM vendors provide concurrent licensing models in any case&#8230;.After spending quite sometime looking at savings SaaS can provide, if youre storing a lot of content in the cloud, the savings just arent there, if anything your costs will probably increase&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Documentum Composer by paulcwarren</title>
		<link>http://ecmobservations.wordpress.com/2009/05/14/documentum-composer/#comment-174</link>
		<dc:creator>paulcwarren</dc:creator>
		<pubDate>Tue, 26 May 2009 11:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://ecmobservations.wordpress.com/?p=104#comment-174</guid>
		<description>Hi Pie,

You know that Composer has basic support for reference projects right?  So you can split a large projects into several smaller ones.  The design-time support for this is ok.  The install-time support sucks at the moment but we are looking into how best to support this; perhaps a DAS; i.e. Documentum Archive Solution - a collection of DARs.  Not sure yet.

FYI we are also investigating smart/selective install were the user can select a subset of artifacts to install or where Composer decides what the subset is.  There are actually some interesting problems rolled up in this one.  But the good news is that there is momentum to solve this particular problem as it is seen as a particular pain point at the moment and it is also an enabler for other use cases; i.e. synchronization.</description>
		<content:encoded><![CDATA[<p>Hi Pie,</p>
<p>You know that Composer has basic support for reference projects right?  So you can split a large projects into several smaller ones.  The design-time support for this is ok.  The install-time support sucks at the moment but we are looking into how best to support this; perhaps a DAS; i.e. Documentum Archive Solution &#8211; a collection of DARs.  Not sure yet.</p>
<p>FYI we are also investigating smart/selective install were the user can select a subset of artifacts to install or where Composer decides what the subset is.  There are actually some interesting problems rolled up in this one.  But the good news is that there is momentum to solve this particular problem as it is seen as a particular pain point at the moment and it is also an enabler for other use cases; i.e. synchronization.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
