<?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>Comentários sobre: Artigo &#124; 5 Motivos para ter um blog corporativo</title>
	<atom:link href="http://www.magoweb.com/blog/2010/07/artigo-5-motivos-para-ter-um-blog-corporativo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.magoweb.com/blog/2010/07/artigo-5-motivos-para-ter-um-blog-corporativo/</link>
	<description>Novidades sobre a Magoweb e seus produtos e serviços. Notícias sobre o mercado de Marketing Digital e Soluções para Internet.</description>
	<lastBuildDate>Sat, 24 Dec 2011 16:55:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Por: Tweets that mention Artigo &#124; 5 Motivos para ter um blog corporativo « Magoweb Blog -- Topsy.com</title>
		<link>http://www.magoweb.com/blog/2010/07/artigo-5-motivos-para-ter-um-blog-corporativo/comment-page-1/#comment-41</link>
		<dc:creator>Tweets that mention Artigo &#124; 5 Motivos para ter um blog corporativo « Magoweb Blog -- Topsy.com</dc:creator>
		<pubDate>Tue, 27 Jul 2010 18:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.magoweb.com/blog/?p=1013#comment-41</guid>
		<description>[...] This post was mentioned on Twitter by Riccardo Dorneles, MaykoeYara and Celso Junior, Magoweb - Oficial. Magoweb - Oficial said: Artigo &#124; Cinco motivos para ter um blog corporativo http://migre.me/10lwH [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Riccardo Dorneles, MaykoeYara and Celso Junior, Magoweb &#8211; Oficial. Magoweb &#8211; Oficial said: Artigo | Cinco motivos para ter um blog corporativo <a href="http://migre.me/10lwH" rel="nofollow">http://migre.me/10lwH</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

