<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Direction of the social media release?</title>
	<link>http://www.sosaidthe.org/2007/03/26/direction-of-the-smr/</link>
	<description>How Government Organizations Communicate and Integrate Social Media</description>
	<pubDate>Mon, 08 Sep 2008 05:01:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Shannon Whitley</title>
		<link>http://www.sosaidthe.org/2007/03/26/direction-of-the-smr/#comment-30</link>
		<author>Shannon Whitley</author>
		<pubDate>Wed, 28 Mar 2007 15:04:59 +0000</pubDate>
		<guid>http://www.sosaidthe.org/2007/03/26/direction-of-the-smr/#comment-30</guid>
					<description>Great points.  Too many of the SMR discussions have been dragged down by the "press vs. new media" debates.  There will always be a need to announce news, no matter which label you use.  The SMR is just the latest incarnation of the ancient herald.

People are being bombarded by today's glut of information.  I hope the SMR will deliver news in a way that will be more digestible.

I'll be the first to admit that my solution, &lt;a href="http://www.prxbuilder.com" rel="nofollow"&gt;PRX Builder&lt;/a&gt;, doesn't contain perfect XHTML-compliant releases.  The original templates were reproductions of other use cases.  The beauty of PRX Builder is that you can swap templates instantaneously.  That's the power of the PRX RSS Extension.  I see this flexibility as an advantage over microformats.

The real point here, however, is that we have an obligation to explore these different options and try to see what works and what doesn't.  We &lt;i&gt;can&lt;/i&gt; make it easier for people to consume our news.  We just need to experiment with the various options until we develop the right approach.</description>
		<content:encoded><![CDATA[<p>Great points.  Too many of the SMR discussions have been dragged down by the &#8220;press vs. new media&#8221; debates.  There will always be a need to announce news, no matter which label you use.  The SMR is just the latest incarnation of the ancient herald.</p>
<p>People are being bombarded by today&#8217;s glut of information.  I hope the SMR will deliver news in a way that will be more digestible.</p>
<p>I&#8217;ll be the first to admit that my solution, <a href="http://www.prxbuilder.com" rel="nofollow">PRX Builder</a>, doesn&#8217;t contain perfect XHTML-compliant releases.  The original templates were reproductions of other use cases.  The beauty of PRX Builder is that you can swap templates instantaneously.  That&#8217;s the power of the PRX RSS Extension.  I see this flexibility as an advantage over microformats.</p>
<p>The real point here, however, is that we have an obligation to explore these different options and try to see what works and what doesn&#8217;t.  We <i>can</i> make it easier for people to consume our news.  We just need to experiment with the various options until we develop the right approach.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jason Ryan</title>
		<link>http://www.sosaidthe.org/2007/03/26/direction-of-the-smr/#comment-44</link>
		<author>Jason Ryan</author>
		<pubDate>Wed, 28 Mar 2007 23:14:16 +0000</pubDate>
		<guid>http://www.sosaidthe.org/2007/03/26/direction-of-the-smr/#comment-44</guid>
					<description>Thanks for commenting Shannon. I had a quick look at PRX Builder and it certainly appears to be a useful tool - well done.
 I also agree that there needs to be more experimentation (and discussion) in order for us to progress this. Bottom line for government, however, is accessibility - so we need to develop standards-based solutions.</description>
		<content:encoded><![CDATA[<p>Thanks for commenting Shannon. I had a quick look at PRX Builder and it certainly appears to be a useful tool - well done.<br />
 I also agree that there needs to be more experimentation (and discussion) in order for us to progress this. Bottom line for government, however, is accessibility - so we need to develop standards-based solutions.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
