<?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: Case Study &#8211; Online Video for Funeral &amp; Cemetery Promotion</title>
	<atom:link href="http://www.funeralfuturist.com/case-study-online-video-for-funeral-cemetery-promotion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.funeralfuturist.com/case-study-online-video-for-funeral-cemetery-promotion/</link>
	<description>Helping funeral and cemetery professionals embrace the future!</description>
	<lastBuildDate>Tue, 16 Mar 2010 12:27:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Newsletter - April 2008 &#124; Funeral Futurist &#124; Robin Heppell</title>
		<link>http://www.funeralfuturist.com/case-study-online-video-for-funeral-cemetery-promotion/comment-page-1/#comment-17</link>
		<dc:creator>Newsletter - April 2008 &#124; Funeral Futurist &#124; Robin Heppell</dc:creator>
		<pubDate>Tue, 08 Apr 2008 00:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.funeralfuturist.com/case-study-online-video-for-funeral-cemetery-promotion/#comment-17</guid>
		<description>[...] comment on the website or just reply to the email. Thanks again, Robin Heppell.  Featured Article: Case Study - Online Video for Funeral &amp; Cemetery Promotion In preparation for my presentation at the ICCFA Annual Convention in San Diego, I am conducting a [...]</description>
		<content:encoded><![CDATA[<p>[...] comment on the website or just reply to the email. Thanks again, Robin Heppell.  Featured Article: Case Study &#8211; Online Video for Funeral &amp; Cemetery Promotion In preparation for my presentation at the ICCFA Annual Convention in San Diego, I am conducting a [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
