<?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: CMIS &#8211; Yet another acronym or more than that?</title>
	<atom:link href="http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/</link>
	<description>Random Thoughts</description>
	<lastBuildDate>Fri, 26 Feb 2010 15:12:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Content Integration Platform and Content Interoperability &#171; contentprise</title>
		<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/comment-page-1/#comment-29846</link>
		<dc:creator>Content Integration Platform and Content Interoperability &#171; contentprise</dc:creator>
		<pubDate>Sat, 15 Aug 2009 19:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/#comment-29846</guid>
		<description>[...] there are couple of valid questions which still need to be answered around the concurrent operations across content repositories, but [...]</description>
		<content:encoded><![CDATA[<p>[...] there are couple of valid questions which still need to be answered around the concurrent operations across content repositories, but [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PCM.Blog &#187; Content Repositories - Coexistence, Migration and Consolidation</title>
		<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/comment-page-1/#comment-10218</link>
		<dc:creator>PCM.Blog &#187; Content Repositories - Coexistence, Migration and Consolidation</dc:creator>
		<pubDate>Fri, 27 Mar 2009 08:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/#comment-10218</guid>
		<description>[...] people have said that with something like CMIS (if and when it becomes a standard), there will be an adverse impact on the connector industry. I [...]</description>
		<content:encoded><![CDATA[<p>[...] people have said that with something like CMIS (if and when it becomes a standard), there will be an adverse impact on the connector industry. I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sayen</title>
		<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/comment-page-1/#comment-3656</link>
		<dc:creator>sayen</dc:creator>
		<pubDate>Mon, 19 Jan 2009 15:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/#comment-3656</guid>
		<description>It’s worth noting that Alfresco (who, along with OpenText, Oracle and SAP, also participated in the CMIS standards body) is about to release the first implementation of the CMIS spec.
It will be interesting to see how quickly the traditional vendors are able to surface these capabilities in their offerings.</description>
		<content:encoded><![CDATA[<p>It’s worth noting that Alfresco (who, along with OpenText, Oracle and SAP, also participated in the CMIS standards body) is about to release the first implementation of the CMIS spec.<br />
It will be interesting to see how quickly the traditional vendors are able to surface these capabilities in their offerings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PCM.Blog &#187; Goodbye 2008, Welcome 2009</title>
		<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/comment-page-1/#comment-1893</link>
		<dc:creator>PCM.Blog &#187; Goodbye 2008, Welcome 2009</dc:creator>
		<pubDate>Tue, 30 Dec 2008 13:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/#comment-1893</guid>
		<description>[...] will help customers reuse existing investments. As an example,&#160;many vendors have come up with CMIS. Okay this is not a standard yet but is possibly in that direction. A standard like this is very [...]</description>
		<content:encoded><![CDATA[<p>[...] will help customers reuse existing investments. As an example,&nbsp;many vendors have come up with CMIS. Okay this is not a standard yet but is possibly in that direction. A standard like this is very [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apoorv</title>
		<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/comment-page-1/#comment-207</link>
		<dc:creator>Apoorv</dc:creator>
		<pubDate>Tue, 16 Sep 2008 10:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/#comment-207</guid>
		<description>Lee,
Thanks for dropping by. I think your example is a good one.

Here is a live example where the use case i described will make sense. A client has an ECM &quot;A&quot; that has been implemented across multiple LOBs and user groups. They want to undertake a 3 year initiative to migrate to ECM &quot;B&quot;. Because of various factors, a big bang approach is not that they will follow and will slowly migrate from A to B. During this transition phase, there will be users of B who will need to collaborate with users on A and vice versa. If we have to implement such a scenario, we&#039;ll possibly need much more than what is available in CMIS currently. I will possibly expand this more in a future post.
Best,
/a</description>
		<content:encoded><![CDATA[<p>Lee,<br />
Thanks for dropping by. I think your example is a good one.</p>
<p>Here is a live example where the use case i described will make sense. A client has an ECM &#8220;A&#8221; that has been implemented across multiple LOBs and user groups. They want to undertake a 3 year initiative to migrate to ECM &#8220;B&#8221;. Because of various factors, a big bang approach is not that they will follow and will slowly migrate from A to B. During this transition phase, there will be users of B who will need to collaborate with users on A and vice versa. If we have to implement such a scenario, we&#8217;ll possibly need much more than what is available in CMIS currently. I will possibly expand this more in a future post.<br />
Best,<br />
/a</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/comment-page-1/#comment-206</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Mon, 15 Sep 2008 09:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/09/14/cmis-yet-another-acronym-or-more-than-that/#comment-206</guid>
		<description>I don&#039;t think the Use Case makes sense that content is stored in two repositories. I think the Use Cases which are being focussed on are more here different items of content interact within the context of a Business Process yet the content is stored in different locations, e.g. a Purchase 2 Pay process with Purchase Orders in one system and Contracts in another...perhaps a bad example but hopefully you get the idea.

However I do think we need to do more thinking around this and ensure that this initiative is seen to benefit the business and not just the techies!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think the Use Case makes sense that content is stored in two repositories. I think the Use Cases which are being focussed on are more here different items of content interact within the context of a Business Process yet the content is stored in different locations, e.g. a Purchase 2 Pay process with Purchase Orders in one system and Contracts in another&#8230;perhaps a bad example but hopefully you get the idea.</p>
<p>However I do think we need to do more thinking around this and ensure that this initiative is seen to benefit the business and not just the techies!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
