<?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"
	>
<channel>
	<title>Comments on: More to come with TomorrowNow suit?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/sap-watch/more-to-come-with-tomorrownow-suit/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/sap-watch/more-to-come-with-tomorrownow-suit/</link>
	<description>A SearchSAP.com blog</description>
	<pubDate>Fri, 27 Nov 2009 13:14:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Charlie O'Racles</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/more-to-come-with-tomorrownow-suit/#comment-631</link>
		<dc:creator>Charlie O'Racles</dc:creator>
		<pubDate>Tue, 05 Feb 2008 17:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/02/05/more-to-come-with-tomorrownow-suit/#comment-631</guid>
		<description>If you have ever read SAP documentation, you know they have a problem with the English language.  If the stuff they stole from Oracle was written in English, Oracle has no reason to be concerned that SAP can do anything useful with it.</description>
		<content:encoded><![CDATA[<p>If you have ever read SAP documentation, you know they have a problem with the English language.  If the stuff they stole from Oracle was written in English, Oracle has no reason to be concerned that SAP can do anything useful with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->