<?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: Magazine editing: managing information overload</title>
	<atom:link href="http://onlinejournalismblog.com/2011/12/19/magazine-editing-managing-information-overload/feed/" rel="self" type="application/rss+xml" />
	<link>http://onlinejournalismblog.com/2011/12/19/magazine-editing-managing-information-overload/</link>
	<description>A conversation.</description>
	<lastBuildDate>Mon, 21 May 2012 12:30:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: School 2.0 in South Africa - School 2.0 Bookmarks (weekly)</title>
		<link>http://onlinejournalismblog.com/2011/12/19/magazine-editing-managing-information-overload/#comment-269803</link>
		<dc:creator>School 2.0 in South Africa - School 2.0 Bookmarks (weekly)</dc:creator>
		<pubDate>Sun, 01 Jan 2012 00:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://onlinejournalismblog.com/?p=15586#comment-269803</guid>
		<description>[...] Managing information overload [...]</description>
		<content:encoded><![CDATA[<p>[...] Managing information overload [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc</title>
		<link>http://onlinejournalismblog.com/2011/12/19/magazine-editing-managing-information-overload/#comment-250115</link>
		<dc:creator>Doc</dc:creator>
		<pubDate>Mon, 19 Dec 2011 13:47:27 +0000</pubDate>
		<guid isPermaLink="false">http://onlinejournalismblog.com/?p=15586#comment-250115</guid>
		<description>Good Article. I think many companies are trying to solve the information overload problem in a myriad ways and its good to know the different approaches being adopted. This seems to be an activity aggregator of sorts. Another interesting way adopted by cloud services like Zukmo is that the content itself is aggregated, indexed, tagged, synced and can be accessed from any device.</description>
		<content:encoded><![CDATA[<p>Good Article. I think many companies are trying to solve the information overload problem in a myriad ways and its good to know the different approaches being adopted. This seems to be an activity aggregator of sorts. Another interesting way adopted by cloud services like Zukmo is that the content itself is aggregated, indexed, tagged, synced and can be accessed from any device.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

