<?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: Office 2.0 News</title>
	<atom:link href="http://itredux.com/2007/02/09/office-20-news/feed/" rel="self" type="application/rss+xml" />
	<link>http://itredux.com/2007/02/09/office-20-news/</link>
	<description>New Rules for a New IT World</description>
	<lastBuildDate>Sat, 10 Dec 2011 03:24:58 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ismael Ghalimi</title>
		<link>http://itredux.com/2007/02/09/office-20-news/comment-page-1/#comment-46374</link>
		<dc:creator>Ismael Ghalimi</dc:creator>
		<pubDate>Wed, 14 Feb 2007 00:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2007/02/09/office-20-news/#comment-46374</guid>
		<description>Bob,

I agree with you, &lt;a href=&quot;http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/&quot; rel=&quot;nofollow&quot;&gt;service cascading&lt;/a&gt; creates many points of failure, and this is precisely an experiment aimed at finding out how to work around the issues such a fragile architecture raises. Part of the solution is in using industry standards. In this particular case, I could get rid of one or two layers in the middle, without losing much functionality, mainly because these services use RSS feeds both in and out.

Best regards
-Ismael</description>
		<content:encoded><![CDATA[<p>Bob,</p>
<p>I agree with you, <a href="http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/" rel="nofollow">service cascading</a> creates many points of failure, and this is precisely an experiment aimed at finding out how to work around the issues such a fragile architecture raises. Part of the solution is in using industry standards. In this particular case, I could get rid of one or two layers in the middle, without losing much functionality, mainly because these services use <span class="caps">RSS</span> feeds both in and&nbsp;out.</p>
<p>Best regards<br />&nbsp;-Ismael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Urry</title>
		<link>http://itredux.com/2007/02/09/office-20-news/comment-page-1/#comment-46164</link>
		<dc:creator>Bob Urry</dc:creator>
		<pubDate>Tue, 13 Feb 2007 11:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2007/02/09/office-20-news/#comment-46164</guid>
		<description>Hi Ismael,

Very innovative use of the services. I think that I would worry that such a layered approach to using such services could break your output should the provider of one of them choose to change their service, or perhaps go out of business.  I think my concern is the level of service continuity, and the notification of changes by the providers.

If you&#039;re creating a system internal to an organization or an outsourcing contract, you can agree on SLAs and so on. Prehaps we need something of a similar arrangement to give confidence that our own creations will continue, or that we have the time to make our own changes.

What do you think?

-Bob</description>
		<content:encoded><![CDATA[<p>Hi&nbsp;Ismael,</p>
<p>Very innovative use of the services. I think that I would worry that such a layered approach to using such services could break your output should the provider of one of them choose to change their service, or perhaps go out of business.  I think my concern is the level of service continuity, and the notification of changes by the&nbsp;providers.</p>
<p>If you&#8217;re creating a system internal to an organization or an outsourcing contract, you can agree on SLAs and so on. Prehaps we need something of a similar arrangement to give confidence that our own creations will continue, or that we have the time to make our own&nbsp;changes.</p>
<p>What do you&nbsp;think?</p>
<p>-Bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ismael Ghalimi</title>
		<link>http://itredux.com/2007/02/09/office-20-news/comment-page-1/#comment-45960</link>
		<dc:creator>Ismael Ghalimi</dc:creator>
		<pubDate>Mon, 12 Feb 2007 20:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2007/02/09/office-20-news/#comment-45960</guid>
		<description>Doron,

I like your idea. I&#039;ll look into it.

Best regards
-Ismael</description>
		<content:encoded><![CDATA[<p>Doron,</p>
<p>I like your idea. I&#8217;ll look into&nbsp;it.</p>
<p>Best regards<br />&nbsp;-Ismael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ismael Ghalimi</title>
		<link>http://itredux.com/2007/02/09/office-20-news/comment-page-1/#comment-45952</link>
		<dc:creator>Ismael Ghalimi</dc:creator>
		<pubDate>Mon, 12 Feb 2007 20:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2007/02/09/office-20-news/#comment-45952</guid>
		<description>Craig,

Thanks for the kind words.

Best regards
-Ismael</description>
		<content:encoded><![CDATA[<p>Craig,</p>
<p>Thanks for the kind&nbsp;words.</p>
<p>Best regards<br />&nbsp;-Ismael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doron</title>
		<link>http://itredux.com/2007/02/09/office-20-news/comment-page-1/#comment-45773</link>
		<dc:creator>Doron</dc:creator>
		<pubDate>Mon, 12 Feb 2007 10:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2007/02/09/office-20-news/#comment-45773</guid>
		<description>That is cool. I have been trying to do something like that in pipes, but wasn&#039;t able to. I think a pipe with updates from all the blogs of the Office 2.0 services would also be cool, and much easier to do. Maybe use the content analyzer to see if they used words such as Update or New or Feature to only show these posts.</description>
		<content:encoded><![CDATA[<p>That is cool. I have been trying to do something like that in pipes, but wasn&#8217;t able to. I think a pipe with updates from all the blogs of the Office 2.0 services would also be cool, and much easier to do. Maybe use the content analyzer to see if they used words such as Update or New or Feature to only show these&nbsp;posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Cmehil</title>
		<link>http://itredux.com/2007/02/09/office-20-news/comment-page-1/#comment-45718</link>
		<dc:creator>Craig Cmehil</dc:creator>
		<pubDate>Mon, 12 Feb 2007 08:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2007/02/09/office-20-news/#comment-45718</guid>
		<description>Quite a bit more sophisticated than my own attempts, but impressive use of the tool.</description>
		<content:encoded><![CDATA[<p>Quite a bit more sophisticated than my own attempts, but impressive use of the&nbsp;tool.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

