<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: NextPage&#8217;s CEO and President, Darren Lee on Document Management</title>
	<link>http://www.podtech.net/home/215/technology</link>
	<description></description>
	<pubDate>Wed, 23 May 2012 09:03:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: rajbala</title>
		<link>http://www.podtech.net/home/215/technology#comment-115</link>
		<dc:creator>rajbala</dc:creator>
		<pubDate>Fri, 18 Nov 2005 01:17:54 +0000</pubDate>
		<guid>http://www.podtech.net/home/215/technology#comment-115</guid>
		<description>I like their concept, but the real value in NextPage is being integrated into all the ECM platforms.  Google Base shows us that there is potential value in a centralized store.  

The last time I checked it out, NextPage did not have complete support for all objects.  Collaboration is not limited to office documents alone -- it spans many file types that NP does not support.  

Lastly, I question the use of extended attributes to manage documents.  There could be all sorts of hairy issues with this method.</description>
		<content:encoded><![CDATA[<p>I like their concept, but the real value in NextPage is being integrated into all the ECM platforms.  Google Base shows us that there is potential value in a centralized store.  </p>
<p>The last time I checked it out, NextPage did not have complete support for all objects.  Collaboration is not limited to office documents alone &#8212; it spans many file types that NP does not support.  </p>
<p>Lastly, I question the use of extended attributes to manage documents.  There could be all sorts of hairy issues with this method.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

