<?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: Introducing the CAOS Research Service</title>
	<atom:link href="http://blogs.the451group.com/opensource/2006/08/22/introducing-the-caos-research-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.the451group.com/opensource/2006/08/22/introducing-the-caos-research-service/</link>
	<description>A blog for the enterprise open source community</description>
	<pubDate>Mon, 08 Sep 2008 00:55:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: 451 CAOS Theory &#187; CAOS Research Service: Email Update</title>
		<link>http://blogs.the451group.com/opensource/2006/08/22/introducing-the-caos-research-service/#comment-4461</link>
		<dc:creator>451 CAOS Theory &#187; CAOS Research Service: Email Update</dc:creator>
		<pubDate>Wed, 30 Aug 2006 20:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.the451group.com/opensource/2006/08/22/introducing-the-caos-research-service/#comment-4461</guid>
		<description>[...] CAOS Research Service: Email Update Raven Zachary, August 30, 2006 @ 3:37 pm ET  As I mentioned in a prior blog posting, &#8220;Introducting the CAOS Research Service,&#8221; I will be blogging about the various components of the recently announced CAOS Research Service. Last week, I blogged about the CAOS Research Reports. This week, the topic is the CAOS email update. [...]</description>
		<content:encoded><![CDATA[<p>[...] CAOS Research Service: Email Update Raven Zachary, August 30, 2006 @ 3:37 pm ET  As I mentioned in a prior blog posting, &#8220;Introducting the CAOS Research Service,&#8221; I will be blogging about the various components of the recently announced CAOS Research Service. Last week, I blogged about the CAOS Research Reports. This week, the topic is the CAOS email update. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
