<?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: Alfresco 1.4, Podcast, Commoditization of ECM</title>
	<atom:link href="http://www.openparenthesis.org/2006/09/11/alfresco-14-podcast-commoditization-of-ecm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.openparenthesis.org/2006/09/11/alfresco-14-podcast-commoditization-of-ecm</link>
	<description>Because these are the early days of a long revolution . . .</description>
	<lastBuildDate>Fri, 03 Feb 2012 06:07:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John</title>
		<link>http://www.openparenthesis.org/2006/09/11/alfresco-14-podcast-commoditization-of-ecm#comment-74</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 11 Sep 2006 21:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.openparenthesis.org/2006/09/11/alfresco-14-podcast-commoditization-of-ecm/#comment-74</guid>
		<description>Hey Sal - good to hear from you. 

(Sal is one of the authors at &lt;a href=&quot;http://www.digitalbusinessstrategy.com/&quot; rel=&quot;nofollow&quot;&gt;Digital Business Strategy&lt;/a&gt; which is well worth checking out.)  

The &quot;overlapping functionality between ECM and other network software&quot; comment is spot-on: from one perspective, Enterprise Content Management is really just Enterprise Data Management or Information Management. In other words, ECM is really just IT. Of course, you&#039;ve got to squint your eyes just right to see it that way, and I&#039;m not sure what it ultimately gets you. ;)

I think of ECM as the core repository, plus the various means for getting content (documents, but also other content types) into it and out of it. That means (federated) search, access controls (authentication and authorization), publishing mechanisms (for multiple formats, to multiple audiences), and workflow tools which control who can submit, revise, and publish bits into the repository or out of it. 

Not sure if that makes for a less complicated  Venn diagram or not, but basically ECM to me is the combination of a core repository plus various applications for accessing content that lives in that repository. (Those applications are sometimes highly structured, sometimes loosely structured or barely-at-all structured in terms of their workflow, of course). 

In terms of Microsoft&#039;s impact on ECM, I see the real core of their offering as being Sharepoint 2007 rather than Vista or the Office Suite. (Office applications might submit content to or get content from repositories via a workflow, but in my ideal architecture they are one client among many).  

I don&#039;t think Sharepoint is a compelling enough story to create a monoculture. 

ECM, to be effective, requires deep and broad integration points - lots of open standards and cross-platform, cross-architecture interaction. Sharepoint may enable MS to play in that world but I certainly don&#039;t think it will dominate in it.</description>
		<content:encoded><![CDATA[<p>Hey Sal &#8211; good to hear from you. </p>
<p>(Sal is one of the authors at <a href="http://www.digitalbusinessstrategy.com/" rel="nofollow">Digital Business Strategy</a> which is well worth checking out.)  </p>
<p>The &#8220;overlapping functionality between ECM and other network software&#8221; comment is spot-on: from one perspective, Enterprise Content Management is really just Enterprise Data Management or Information Management. In other words, ECM is really just IT. Of course, you&#8217;ve got to squint your eyes just right to see it that way, and I&#8217;m not sure what it ultimately gets you. ;)</p>
<p>I think of ECM as the core repository, plus the various means for getting content (documents, but also other content types) into it and out of it. That means (federated) search, access controls (authentication and authorization), publishing mechanisms (for multiple formats, to multiple audiences), and workflow tools which control who can submit, revise, and publish bits into the repository or out of it. </p>
<p>Not sure if that makes for a less complicated  Venn diagram or not, but basically ECM to me is the combination of a core repository plus various applications for accessing content that lives in that repository. (Those applications are sometimes highly structured, sometimes loosely structured or barely-at-all structured in terms of their workflow, of course). </p>
<p>In terms of Microsoft&#8217;s impact on ECM, I see the real core of their offering as being Sharepoint 2007 rather than Vista or the Office Suite. (Office applications might submit content to or get content from repositories via a workflow, but in my ideal architecture they are one client among many).  </p>
<p>I don&#8217;t think Sharepoint is a compelling enough story to create a monoculture. </p>
<p>ECM, to be effective, requires deep and broad integration points &#8211; lots of open standards and cross-platform, cross-architecture interaction. Sharepoint may enable MS to play in that world but I certainly don&#8217;t think it will dominate in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sal Darji</title>
		<link>http://www.openparenthesis.org/2006/09/11/alfresco-14-podcast-commoditization-of-ecm#comment-73</link>
		<dc:creator>Sal Darji</dc:creator>
		<pubDate>Mon, 11 Sep 2006 18:55:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.openparenthesis.org/2006/09/11/alfresco-14-podcast-commoditization-of-ecm/#comment-73</guid>
		<description>John, 

Thanks for the post/links.  I would love to get your opinion on ECM and its role within an organization.  It seems to me that there is a ton of overlapping functionality between ECM and other network software functionality.  Everything that the demo shows can be done using file system tools and workflow software.  This makes for a very confusing Venn diagram.  

In addition, Vista and the new Office suite (presumably with Groove functionality) will be released soon.  Do you think that that open source ECM will stay competitive with Microsoft&#039;s offerings?  Or is this arena doomed to be a monoculture in the next few years?

Sal Darji</description>
		<content:encoded><![CDATA[<p>John, </p>
<p>Thanks for the post/links.  I would love to get your opinion on ECM and its role within an organization.  It seems to me that there is a ton of overlapping functionality between ECM and other network software functionality.  Everything that the demo shows can be done using file system tools and workflow software.  This makes for a very confusing Venn diagram.  </p>
<p>In addition, Vista and the new Office suite (presumably with Groove functionality) will be released soon.  Do you think that that open source ECM will stay competitive with Microsoft&#8217;s offerings?  Or is this arena doomed to be a monoculture in the next few years?</p>
<p>Sal Darji</p>
]]></content:encoded>
	</item>
</channel>
</rss>

