<?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: Bill Versioning: Unintended consequences of data openness</title>
	<atom:link href="http://www.theopenhouseproject.com/2007/02/14/bill-versioning-unintended-consequences-of-data-openness/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theopenhouseproject.com/2007/02/14/bill-versioning-unintended-consequences-of-data-openness/</link>
	<description>Recommendations, Resources, and Reform</description>
	<lastBuildDate>Mon, 14 Feb 2011 15:53:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joshua Tauberer</title>
		<link>http://www.theopenhouseproject.com/2007/02/14/bill-versioning-unintended-consequences-of-data-openness/comment-page-1/#comment-20</link>
		<dc:creator>Joshua Tauberer</dc:creator>
		<pubDate>Sat, 17 Feb 2007 22:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/02/14/bill-versioning-unintended-consequences-of-data-openness/#comment-20</guid>
		<description>I would be very interested to hear about any headway they make on that.  It would certainly be a very useful tool.</description>
		<content:encoded><![CDATA[<p>I would be very interested to hear about any headway they make on that.  It would certainly be a very useful tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lewisb</title>
		<link>http://www.theopenhouseproject.com/2007/02/14/bill-versioning-unintended-consequences-of-data-openness/comment-page-1/#comment-17</link>
		<dc:creator>lewisb</dc:creator>
		<pubDate>Thu, 15 Feb 2007 13:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/02/14/bill-versioning-unintended-consequences-of-data-openness/#comment-17</guid>
		<description>I noticed GovTrack a while back and have been pleased with the format.

The students in one of my classes are working on taking this idea one step further.  Instead of showing the changes to a bill itself, they are building a system for showing the changes to the US Code that are *caused* by a bill.  The reasoning is very similar to what you describe above -- the &quot;inserts&quot; and &quot;strikes&quot; language makes it very difficult to understand what the changes to the law will be, since the bill text by itself is not presented in context with the rest of the law.</description>
		<content:encoded><![CDATA[<p>I noticed GovTrack a while back and have been pleased with the format.</p>
<p>The students in one of my classes are working on taking this idea one step further.  Instead of showing the changes to a bill itself, they are building a system for showing the changes to the US Code that are *caused* by a bill.  The reasoning is very similar to what you describe above &#8212; the &#8220;inserts&#8221; and &#8220;strikes&#8221; language makes it very difficult to understand what the changes to the law will be, since the bill text by itself is not presented in context with the rest of the law.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

