<?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: Thinking of ways on how to integrate Google Wave with Digital Signage</title>
	<atom:link href="http://www.digitalsignageblog.com/2009/10/30/thinking-of-ways-on-how-to-integrate-google-wave-with-digital-signage/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalsignageblog.com/2009/10/30/thinking-of-ways-on-how-to-integrate-google-wave-with-digital-signage/</link>
	<description>Digital signage blog - the blog of digital signage</description>
	<lastBuildDate>Wed, 10 Mar 2010 08:55:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Munix</title>
		<link>http://www.digitalsignageblog.com/2009/10/30/thinking-of-ways-on-how-to-integrate-google-wave-with-digital-signage/comment-page-1/#comment-19568</link>
		<dc:creator>Munix</dc:creator>
		<pubDate>Fri, 06 Nov 2009 08:10:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalsignageblog.com/?p=1749#comment-19568</guid>
		<description>I don&#039;t think what google wave provides is a good match to the requirements of digital signage.  Providing a CMS
capability can be done with google docs already and free if 7gb or so is enough and can stage content in chunks if need be. Access the content is quite easy if using a language like Ruby via their REST&#039;full api.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think what google wave provides is a good match to the requirements of <span class='bm_keywordlink'><a href="http://www.advertiseme.com.au" target="_blank">digital signage</a></span>.  Providing a CMS<br />
capability can be done with google docs already and free if 7gb or so is enough and can stage content in chunks if need be. Access the content is quite easy if using a language like Ruby via their REST&#8217;full api.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
