<?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: Leveraging the Government 2.0 Platform</title>
	<atom:link href="http://www.voiceingov.org/blog/?feed=rss2&#038;p=1136" rel="self" type="application/rss+xml" />
	<link>http://www.voiceingov.org/blog/?p=1136</link>
	<description>"Ministers... cannot in any country be uninfluenced by the voice of the people."</description>
	<pubDate>Mon, 06 Sep 2010 23:10:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#8230;.::: VOX POPULI :::&#8230;. &#187; Blog Archive &#187; Lots of Gov 2.0 Potential in Twitter Geolocation</title>
		<link>http://www.voiceingov.org/blog/?p=1136&cpage=1#comment-780</link>
		<dc:creator>&#8230;.::: VOX POPULI :::&#8230;. &#187; Blog Archive &#187; Lots of Gov 2.0 Potential in Twitter Geolocation</dc:creator>
		<pubDate>Thu, 24 Sep 2009 12:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiceingov.org/blog/?p=1136#comment-780</guid>
		<description>[...] Twitter currently has some limited geolocation support that utilizes the account-level location field, but there is no validation on what is entered, so it is not terribly reliable.  The imminent support for &#8220;geo-Tweets&#8221; holds enormous potential for governments if you think of Twitter as another communications channel that citizens can use to interact with government. (Clearly, I do.) [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter currently has some limited geolocation support that utilizes the account-level location field, but there is no validation on what is entered, so it is not terribly reliable.  The imminent support for &#8220;geo-Tweets&#8221; holds enormous potential for governments if you think of Twitter as another communications channel that citizens can use to interact with government. (Clearly, I do.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Headd</title>
		<link>http://www.voiceingov.org/blog/?p=1136&cpage=1#comment-753</link>
		<dc:creator>Mark Headd</dc:creator>
		<pubDate>Tue, 08 Sep 2009 17:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiceingov.org/blog/?p=1136#comment-753</guid>
		<description>Cool - so the RSS feed includes bills that have been acted upon within a specific period, correct? Would this include a bill that was just introduced (and referred to its initial committee for consideration)?

I had some of the same thoughts that you did, about being able to proactively notify someone when an action is taken on a bill. I was thinking it would be neat to allow someone to "subscribe" to a bill through one of the channels listed above. So, for example, when someone sends a tweet to @opensenate to get the current status of a bill, they could then send a follow up like "#notify S1234" to be notified of future changes in the status of a bill.

These notification requests would need to be persisted somewhere - probably just require the addition of a database backend to the app.  If the OpenLeg RSS feed includes changes for a specific time period, it should be pretty straightforward to use it to find out which bills have seen a status change, query the database to see if the bills have any "subscribers" and then send out a notice to the end user on the same channel they used to subscribed.

Just thinking out loud here, but I think its a viable approach.

I like the idea of weaving bills into the conversations on social networks - I see you have Facebook and Twitter integration in the discussion section of the bill summaries.  I need to try that and add a comment to a bill or two.</description>
		<content:encoded><![CDATA[<p>Cool - so the RSS feed includes bills that have been acted upon within a specific period, correct? Would this include a bill that was just introduced (and referred to its initial committee for consideration)?</p>
<p>I had some of the same thoughts that you did, about being able to proactively notify someone when an action is taken on a bill. I was thinking it would be neat to allow someone to &#8220;subscribe&#8221; to a bill through one of the channels listed above. So, for example, when someone sends a tweet to @opensenate to get the current status of a bill, they could then send a follow up like &#8220;#notify S1234&#8243; to be notified of future changes in the status of a bill.</p>
<p>These notification requests would need to be persisted somewhere - probably just require the addition of a database backend to the app.  If the OpenLeg RSS feed includes changes for a specific time period, it should be pretty straightforward to use it to find out which bills have seen a status change, query the database to see if the bills have any &#8220;subscribers&#8221; and then send out a notice to the end user on the same channel they used to subscribed.</p>
<p>Just thinking out loud here, but I think its a viable approach.</p>
<p>I like the idea of weaving bills into the conversations on social networks - I see you have Facebook and Twitter integration in the discussion section of the bill summaries.  I need to try that and add a comment to a bill or two.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Freitas (NY Senate)</title>
		<link>http://www.voiceingov.org/blog/?p=1136&cpage=1#comment-752</link>
		<dc:creator>Nathan Freitas (NY Senate)</dc:creator>
		<pubDate>Tue, 08 Sep 2009 16:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiceingov.org/blog/?p=1136#comment-752</guid>
		<description>This is fantastic work, Mark. I'm flattered and relieved to have a developer of your quality and vision to be utilizing our OpenLeg API. I am working on a big update to the open.nysenate.gov home page and will plan to include your work in a showcase section. Voxeo/IMified is a neat platform to build on, especially with their support for XMPP.

As a side note, have you noticed the RSS feeds we now have available? That is what is powering: http://twitter.com/nysenateopenleg 

I am really interested in getting data proactively pushed out and indexed, where citizens don't have to go and seek out information, but it is instead weaved into the conversation throughout the web, social networks and more.</description>
		<content:encoded><![CDATA[<p>This is fantastic work, Mark. I&#8217;m flattered and relieved to have a developer of your quality and vision to be utilizing our OpenLeg API. I am working on a big update to the open.nysenate.gov home page and will plan to include your work in a showcase section. Voxeo/IMified is a neat platform to build on, especially with their support for XMPP.</p>
<p>As a side note, have you noticed the RSS feeds we now have available? That is what is powering: <a href="http://twitter.com/nysenateopenleg" rel="nofollow">http://twitter.com/nysenateopenleg</a> </p>
<p>I am really interested in getting data proactively pushed out and indexed, where citizens don&#8217;t have to go and seek out information, but it is instead weaved into the conversation throughout the web, social networks and more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
