<?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: Presentation: &#8216;How did we all get here?&#8217;</title>
	<atom:link href="http://www.richardingram.co.uk/2011/10/presentation-how-did-we-all-get-here/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardingram.co.uk/2011/10/presentation-how-did-we-all-get-here/</link>
	<description>Richard Ingram&#039;s blog about content strategy, information design, and web accessibility</description>
	<lastBuildDate>Tue, 04 Jun 2013 11:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>By: Planning Your Enterprise Content Strategy for 2013? Here Are 2 Industry Reports You Don&#8217;t Want to Miss! &#124; The Discontented Company</title>
		<link>http://www.richardingram.co.uk/2011/10/presentation-how-did-we-all-get-here/comment-page-1/#comment-11681</link>
		<dc:creator><![CDATA[Planning Your Enterprise Content Strategy for 2013? Here Are 2 Industry Reports You Don&#8217;t Want to Miss! &#124; The Discontented Company]]></dc:creator>
		<pubDate>Mon, 26 Nov 2012 19:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=2094#comment-11681</guid>
		<description><![CDATA[[...] content strategy was popularized in 2009, the core competencies of the discipline have yet to be defined, leaving many HR professionals wondering how, when, where and why to hire a Content Strategist. Do [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] content strategy was popularized in 2009, the core competencies of the discipline have yet to be defined, leaving many HR professionals wondering how, when, where and why to hire a Content Strategist. Do [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
