<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: [CSG Spring 2006] Sheila Mooney &#8211; Chandler Update</title>
	<atom:link href="http://blog.orenblog.org/2006/05/11/csg_spring_2006_10/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.orenblog.org/2006/05/11/csg_spring_2006_10/</link>
	<description>This is where you say something clever</description>
	<lastBuildDate>Wed, 15 Feb 2012 06:16:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jim Phelps</title>
		<link>http://blog.orenblog.org/2006/05/11/csg_spring_2006_10/#comment-488</link>
		<dc:creator><![CDATA[Jim Phelps]]></dc:creator>
		<pubDate>Mon, 15 May 2006 19:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://orensr.wordpress.com/2006/05/11/csg_spring_2006_10/#comment-488</guid>
		<description><![CDATA[On the Chandler update: I have two responses to what I saw and have seen. The first is based on the current client-server products and the second is based on Mimi Yin&#039;s presentations about the future.


Another client for calendar? eh. Maybe it will be so much better than my current client (Oracle - which isn&#039;t that great) and maybe it will work with our current infrastructure. Maybe not. For peer-2-peer, I would use iCal on my Mac. It has lots of features that I would use except it doesn&#039;t fit our infrastructure.


The Oracle client leaves lots to be desired (see my blog )


But I am very excited about what I see and hear from Mimi Yin. Check out her BayCHI presentation. The ability to flow collaboration artifacts (emails, chats, documents, events) around seamlessly, to link them together, tag them and mark them as DONE, NOW, FUTURE is awesome. This is what a collaboration tool should look like.
]]></description>
		<content:encoded><![CDATA[<p>On the Chandler update: I have two responses to what I saw and have seen. The first is based on the current client-server products and the second is based on Mimi Yin&#8217;s presentations about the future.</p>
<p>Another client for calendar? eh. Maybe it will be so much better than my current client (Oracle &#8211; which isn&#8217;t that great) and maybe it will work with our current infrastructure. Maybe not. For peer-2-peer, I would use iCal on my Mac. It has lots of features that I would use except it doesn&#8217;t fit our infrastructure.</p>
<p>The Oracle client leaves lots to be desired (see my blog )</p>
<p>But I am very excited about what I see and hear from Mimi Yin. Check out her BayCHI presentation. The ability to flow collaboration artifacts (emails, chats, documents, events) around seamlessly, to link them together, tag them and mark them as DONE, NOW, FUTURE is awesome. This is what a collaboration tool should look like.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

