<?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: SAP&#8217;s Vision on the Changing Role of CIO&#8217;s</title>
	<atom:link href="http://www.zoliblog.com/2006/05/21/saps-vision-on-the-changing-role-of-cios/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zoliblog.com/2006/05/21/saps-vision-on-the-changing-role-of-cios/</link>
	<description>Connecting the dots ...</description>
	<lastBuildDate>Sat, 21 Nov 2009 06:03:39 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.zoliblog.com/2006/05/21/saps-vision-on-the-changing-role-of-cios/#comment-501</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 24 May 2006 02:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2006/05/21/saps-vision-on-the-changing-role-of-cios/#comment-501</guid>
		<description>This is a very interesting development -- I just wrote a white paper of separation of process and technology in content management.  If you isolate the development to this space, content management itself is being handled on the departmental level, where all the need from the technology group are process suggestions; the tech group then works on content delivery.  This paradigm also seems to work well with other horizontal solutions.

</description>
		<content:encoded><![CDATA[<p>This is a very interesting development &#8212; I just wrote a white paper of separation of process and technology in content management.  If you isolate the development to this space, content management itself is being handled on the departmental level, where all the need from the technology group are process suggestions; the tech group then works on content delivery.  This paradigm also seems to work well with other horizontal solutions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
