<?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:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Media coverage for public relations-driven round tables and white papers</title>
	<atom:link href="http://craigpearce.info/public-relations/media-coverage-and-involvement-in-public-relations-round-tables-and-white-papers/feed/" rel="self" type="application/rss+xml" />
	<link>http://craigpearce.info/public-relations/media-coverage-and-involvement-in-public-relations-round-tables-and-white-papers/</link>
	<description>Short-term pain for long-term gain</description>
	<lastBuildDate>Sun, 05 Feb 2012 18:28:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Round tables and white papers: corporate communication best practice &#124; Bluegrass Consulting: Grassroots Public Affairs</title>
		<link>http://craigpearce.info/public-relations/media-coverage-and-involvement-in-public-relations-round-tables-and-white-papers/comment-page-1/#comment-3101</link>
		<dc:creator>Round tables and white papers: corporate communication best practice &#124; Bluegrass Consulting: Grassroots Public Affairs</dc:creator>
		<pubDate>Wed, 12 May 2010 07:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://craigpearce.info/?p=352#comment-3101</guid>
		<description>[...] Related posts on this topic include tips on getting participants to attend a round table and the media relations dimension of a round table and white paper. [...]</description>
		<content:encoded><![CDATA[<p>[...] Related posts on this topic include tips on getting participants to attend a round table and the media relations dimension of a round table and white paper. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

