<?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 Storyline Syndicator</title>
	<atom:link href="http://www.pr-squared.com/index.php/2007/02/the_storyline_syndicator/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pr-squared.com/index.php/2007/02/the_storyline_syndicator</link>
	<description>Social Media and Public Relations Consulting � PR Squared</description>
	<lastBuildDate>Fri, 19 Mar 2010 15:46:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dee Rambeau</title>
		<link>http://www.pr-squared.com/index.php/2007/02/the_storyline_syndicator/comment-page-1#comment-506</link>
		<dc:creator>Dee Rambeau</dc:creator>
		<pubDate>Mon, 12 Feb 2007 18:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://pr-squared.com/pr2wp/?p=309#comment-506</guid>
		<description>I&#039;d agree with John in that I&#039;m still getting questions about RSS in general. That will change. The way we handle it with our several hundred MediaRoom clients currently is that they:
1. Build a section of content related to that specific topic using the MediaRoom CMS.
2. Password-protect that page or section.
3. Offer a feed or even a simple &quot;form&quot; subscription that allows journos to sign up.
4. Change and/or manage that content regularly.

Whether it&#039;s a &quot;micro-blog&quot; or a page within their existing CMS, the concept is the same...and the issues are the same. Do they see themselves as content creators offering up second-day story ideas behind breaking stories, or &quot;storylines&quot; as you call them? The good ones do.
</description>
		<content:encoded><![CDATA[<p>I&#8217;d agree with John in that I&#8217;m still getting questions about RSS in general. That will change. The way we handle it with our several hundred MediaRoom clients currently is that they:<br />
1. Build a section of content related to that specific topic using the MediaRoom CMS.<br />
2. Password-protect that page or section.<br />
3. Offer a feed or even a simple &#8220;form&#8221; subscription that allows journos to sign up.<br />
4. Change and/or manage that content regularly.</p>
<p>Whether it&#8217;s a &#8220;micro-blog&#8221; or a page within their existing CMS, the concept is the same&#8230;and the issues are the same. Do they see themselves as content creators offering up second-day story ideas behind breaking stories, or &#8220;storylines&#8221; as you call them? The good ones do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Wagner</title>
		<link>http://www.pr-squared.com/index.php/2007/02/the_storyline_syndicator/comment-page-1#comment-505</link>
		<dc:creator>John Wagner</dc:creator>
		<pubDate>Fri, 09 Feb 2007 17:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://pr-squared.com/pr2wp/?p=309#comment-505</guid>
		<description>Todd:

I&#039;ve had discussions with a number of different organizations about something very similar for top customers.

The obstacles that derail the idea are always the same:

1) It&#039;s a struggle explaining RSS, and even when they do understand it, people don&#039;t distinguish a difference between the feed and an e-mail blast.
2) Most companies don&#039;t see themselves as content creators, especially in some industries.

Having said that, I firmly believe that somebody, somewhere, will take this idea and really make hay with it.
</description>
		<content:encoded><![CDATA[<p>Todd:</p>
<p>I&#8217;ve had discussions with a number of different organizations about something very similar for top customers.</p>
<p>The obstacles that derail the idea are always the same:</p>
<p>1) It&#8217;s a struggle explaining RSS, and even when they do understand it, people don&#8217;t distinguish a difference between the feed and an e-mail blast.<br />
2) Most companies don&#8217;t see themselves as content creators, especially in some industries.</p>
<p>Having said that, I firmly believe that somebody, somewhere, will take this idea and really make hay with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Defren</title>
		<link>http://www.pr-squared.com/index.php/2007/02/the_storyline_syndicator/comment-page-1#comment-504</link>
		<dc:creator>Todd Defren</dc:creator>
		<pubDate>Fri, 09 Feb 2007 14:51:51 +0000</pubDate>
		<guid isPermaLink="false">http://pr-squared.com/pr2wp/?p=309#comment-504</guid>
		<description>Very interesting perspective, Tim, thanks for sharing your specific experiences.

Your point is well taken - once anything is posted, whether &quot;protected&quot; or not, it does find a way into the public ether.  Again, that&#039;s why the company who used a Storyline Syndicator would need to post fairly generic concepts, especially at first, as the system got vetted.
</description>
		<content:encoded><![CDATA[<p>Very interesting perspective, Tim, thanks for sharing your specific experiences.</p>
<p>Your point is well taken &#8211; once anything is posted, whether &#8220;protected&#8221; or not, it does find a way into the public ether.  Again, that&#8217;s why the company who used a Storyline Syndicator would need to post fairly generic concepts, especially at first, as the system got vetted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Verras</title>
		<link>http://www.pr-squared.com/index.php/2007/02/the_storyline_syndicator/comment-page-1#comment-3090</link>
		<dc:creator>Tim Verras</dc:creator>
		<pubDate>Fri, 09 Feb 2007 13:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://pr-squared.com/pr2wp/?p=309#comment-3090</guid>
		<description>I think the idea has some legs but I do see one flaw. I think we are perhaps being a little bit idealistic in assuming that a password protected blog given to x-number of journalists will stay secure. We’ve been trying to push blogs on some of our clients and they usually have concerns about ‘show their hand’ or saying something they’ll regret only to have it forever cached in the annals of Google. If a company has secrets worth protecting in a locked-down blog, I doubt they’d give them to &lt;i&gt;any&lt;/i&gt; journalist. The web has pretty much destroyed story embargos and ‘privileged’ information. Look at the Chicago Auto Show, for example, where most of the vehicles that were ‘unveiled’ had been floating around the net for days because Car and Driver or MotorTrend or someone obscure Russian car mag printed photo’s too early or didn&#039;t lock their website down (though this could arguably be a clever marketing tactic on the auto maker’s part, though after working for one of their ad agencies I am wont to credit them with something so slick). That being said, this would probably work for a smaller, niche industry with not a lot of coverage (or audience) but I don’t see it being useful on a wide level. But we’re all experimenting here, right? So lets give it a shot.
</description>
		<content:encoded><![CDATA[<p>I think the idea has some legs but I do see one flaw. I think we are perhaps being a little bit idealistic in assuming that a password protected blog given to x-number of journalists will stay secure. We’ve been trying to push blogs on some of our clients and they usually have concerns about ‘show their hand’ or saying something they’ll regret only to have it forever cached in the annals of Google. If a company has secrets worth protecting in a locked-down blog, I doubt they’d give them to <i>any</i> journalist. The web has pretty much destroyed story embargos and ‘privileged’ information. Look at the Chicago Auto Show, for example, where most of the vehicles that were ‘unveiled’ had been floating around the net for days because Car and Driver or MotorTrend or someone obscure Russian car mag printed photo’s too early or didn&#8217;t lock their website down (though this could arguably be a clever marketing tactic on the auto maker’s part, though after working for one of their ad agencies I am wont to credit them with something so slick). That being said, this would probably work for a smaller, niche industry with not a lot of coverage (or audience) but I don’t see it being useful on a wide level. But we’re all experimenting here, right? So lets give it a shot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
