<?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: Fostering Citizenship with Transparency and Active Listening</title>
	<atom:link href="http://codeforamerica.org/2010/02/10/fostering-citizenship-with-transparency-and-active-listening/feed/" rel="self" type="application/rss+xml" />
	<link>http://codeforamerica.org/2010/02/10/fostering-citizenship-with-transparency-and-active-listening/</link>
	<description>Connecting city governments and Web 2.0 talent.</description>
	<lastBuildDate>Tue, 07 Sep 2010 18:37:52 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: On Government Big and Small. And Weeding. » Code for America</title>
		<link>http://codeforamerica.org/2010/02/10/fostering-citizenship-with-transparency-and-active-listening/comment-page-1/#comment-267</link>
		<dc:creator>On Government Big and Small. And Weeding. » Code for America</dc:creator>
		<pubDate>Thu, 01 Jul 2010 01:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://codeforamerica.org/?p=241#comment-267</guid>
		<description>[...] our lofty ambitions and the thoughtful service of our every day needs, and most importantly, our part as citizens in both.  At this point in the evolution of our society, neither big government nor small government is [...]</description>
		<content:encoded><![CDATA[<p>[...] our lofty ambitions and the thoughtful service of our every day needs, and most importantly, our part as citizens in both.  At this point in the evolution of our society, neither big government nor small government is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy</title>
		<link>http://codeforamerica.org/2010/02/10/fostering-citizenship-with-transparency-and-active-listening/comment-page-1/#comment-183</link>
		<dc:creator>Amy</dc:creator>
		<pubDate>Fri, 04 Jun 2010 15:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://codeforamerica.org/?p=241#comment-183</guid>
		<description>Great post,

I&#039;m curious where SeeClickFix fits into your thinking on this and how we might improve the tools we have in place?</description>
		<content:encoded><![CDATA[<p>Great post,</p>
<p>I&#8217;m curious where SeeClickFix fits into your thinking on this and how we might improve the tools we have in place?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Massa</title>
		<link>http://codeforamerica.org/2010/02/10/fostering-citizenship-with-transparency-and-active-listening/comment-page-1/#comment-16</link>
		<dc:creator>Justin Massa</dc:creator>
		<pubDate>Fri, 12 Feb 2010 20:52:38 +0000</pubDate>
		<guid isPermaLink="false">http://codeforamerica.org/?p=241#comment-16</guid>
		<description>Awesome post, but I think that software design / code is only 1/2 the challenge. Data is just as important. 

In the example that you cite, being able to correspond broken street lights to crime assumes not only that crime data is transparent (not always the case but increasingly so), but also that the data is reliable and contains the kinds of information necessary to draw those types of conclusions. Just this week, the NYTimes pointed out how crime stats are not always super reliable: http://www.nytimes.com/2010/02/07/nyregion/07crime.html 

Discerning the difference between correlation and causation, and other limits of the data itself, is vital. We need to get the code right, but the greatest code in the world will not overcome the challenges of messy, incomplete, or otherwise flawed tables. Civic applications require high quality data and a deep understanding of what the data does a does not &#039;say&#039; in order to be effective.</description>
		<content:encoded><![CDATA[<p>Awesome post, but I think that software design / code is only 1/2 the challenge. Data is just as important. </p>
<p>In the example that you cite, being able to correspond broken street lights to crime assumes not only that crime data is transparent (not always the case but increasingly so), but also that the data is reliable and contains the kinds of information necessary to draw those types of conclusions. Just this week, the NYTimes pointed out how crime stats are not always super reliable: <a href="http://www.nytimes.com/2010/02/07/nyregion/07crime.html" rel="nofollow">http://www.nytimes.com/2010/02/07/nyregion/07crime.html</a> </p>
<p>Discerning the difference between correlation and causation, and other limits of the data itself, is vital. We need to get the code right, but the greatest code in the world will not overcome the challenges of messy, incomplete, or otherwise flawed tables. Civic applications require high quality data and a deep understanding of what the data does a does not &#8217;say&#8217; in order to be effective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://codeforamerica.org/2010/02/10/fostering-citizenship-with-transparency-and-active-listening/comment-page-1/#comment-14</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 12 Feb 2010 05:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://codeforamerica.org/?p=241#comment-14</guid>
		<description>Great post,

I&#039;m curious where SeeClickFix fits into your thinking on this and how we might improve the tools we have in place?</description>
		<content:encoded><![CDATA[<p>Great post,</p>
<p>I&#8217;m curious where SeeClickFix fits into your thinking on this and how we might improve the tools we have in place?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
