<?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: The Embargo Conundrum</title>
	<atom:link href="http://www.stagetwoconsulting.com/wordpress/the-embargo-conundrum-194/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stagetwoconsulting.com/wordpress/the-embargo-conundrum-194/</link>
	<description>Open Marketing</description>
	<lastBuildDate>Tue, 02 Mar 2010 14:41:34 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: WinExtra - Self Imposed Embargoes The Next Blogger Trick?</title>
		<link>http://www.stagetwoconsulting.com/wordpress/the-embargo-conundrum-194/comment-page-1/#comment-484</link>
		<dc:creator>WinExtra - Self Imposed Embargoes The Next Blogger Trick?</dc:creator>
		<pubDate>Mon, 25 Aug 2008 21:18:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.stagetwoconsulting.com/wordpress/?p=194#comment-484</guid>
		<description>[...] much free publicity and marketing juice as possible for their client. If a company has developed a personal relationship with a journalist or blogger, then I could see doing someone a favour by respecting an embargo. But [...]</description>
		<content:encoded><![CDATA[<p>[...] much free publicity and marketing juice as possible for their client. If a company has developed a personal relationship with a journalist or blogger, then I could see doing someone a favour by respecting an embargo. But [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Embargoes: Thanks but no thanks &#187; mathewingram.com/work &#124;</title>
		<link>http://www.stagetwoconsulting.com/wordpress/the-embargo-conundrum-194/comment-page-1/#comment-472</link>
		<dc:creator>Embargoes: Thanks but no thanks &#187; mathewingram.com/work &#124;</dc:creator>
		<pubDate>Thu, 21 Aug 2008 21:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.stagetwoconsulting.com/wordpress/?p=194#comment-472</guid>
		<description>[...] much free publicity and marketing juice as possible for their client. If a company has developed a personal relationship with a journalist or blogger, then I could see doing someone a favour by respecting an embargo. But [...]</description>
		<content:encoded><![CDATA[<p>[...] much free publicity and marketing juice as possible for their client. If a company has developed a personal relationship with a journalist or blogger, then I could see doing someone a favour by respecting an embargo. But [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Svetlana Gladkova</title>
		<link>http://www.stagetwoconsulting.com/wordpress/the-embargo-conundrum-194/comment-page-1/#comment-471</link>
		<dc:creator>Svetlana Gladkova</dc:creator>
		<pubDate>Thu, 21 Aug 2008 12:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.stagetwoconsulting.com/wordpress/?p=194#comment-471</guid>
		<description>Very reasonable post, especially the part about asking if an embargo will be accepted initially. I have seen this done by a lot of PR firms myself as a blogger but unfortunately startups that choose the do-it-yourself approach often send unwanted embargoed information without asking - simply because they have no idea that when they ask for coverage on the launch date they have no idea bloggers would want to do it earlier.</description>
		<content:encoded><![CDATA[<p>Very reasonable post, especially the part about asking if an embargo will be accepted initially. I have seen this done by a lot of PR firms myself as a blogger but unfortunately startups that choose the do-it-yourself approach often send unwanted embargoed information without asking &#8211; simply because they have no idea that when they ask for coverage on the launch date they have no idea bloggers would want to do it earlier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
