<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0" xmlns:s="http://resources.bnet.com/">
<channel>
	<title><![CDATA[work-in-progress Resources | BNET]]></title>
	<link><![CDATA[http://resources.bnet.com/topic/work-in-progress.html]]></link>
	<description><![CDATA[White papers, case studies, business articles, and blog posts relating to work-in-progress]]></description>
	<s:counts start="0" returned="1" found="1" />
	<language>en-us</language>
	<item>
		<title><![CDATA[The Social Media Release Is Still A Work In Progress]]></title>
		<link><![CDATA[http://www.bnet.com/5208-13543-0.html?forumID=1&threadID=1820&messageID=8282&start=0]]></link>
		<description><![CDATA[The Social Media Release Is Still A Work In ProgressAgreed...but the benefit of the SMR for me is the way that it enables distribution of the elements of the story rather than a story "block". A traditional press release is split up into its elements according to the editorial decisions...]]></description>
		<s:doctype><![CDATA[Discussion threads]]></s:doctype>
		<pubDate>Wed, 05 Mar 2008 00:39:00 -0800</pubDate>
		<category domain="http://resources.bnet.com/topic/smr.html"><![CDATA[SMR]]></category>
		<category domain="http://resources.bnet.com/topic/social+media.html"><![CDATA[social media]]></category>
		<category domain="http://resources.bnet.com/topic/social+media+release.html"><![CDATA[Social Media Release]]></category>
		<category domain="http://resources.bnet.com/topic/work-in-progress.html"><![CDATA[Work-in-Progress]]></category>
	</item>
</channel>
</rss>
