<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Open House Project &#187; procedure</title>
	<atom:link href="http://www.theopenhouseproject.com/category/procedure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theopenhouseproject.com</link>
	<description>Recommendations, Resources, and Reform</description>
	<lastBuildDate>Wed, 23 Feb 2011 16:24:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Procedural Uncertainty &amp; Normalization</title>
		<link>http://www.theopenhouseproject.com/2008/01/09/procedural-uncertainty-normalization/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/09/procedural-uncertainty-normalization/#comments</comments>
		<pubDate>Thu, 10 Jan 2008 02:41:23 +0000</pubDate>
		<dc:creator>Joshua Tauberer</dc:creator>
				<category><![CDATA[House of Representatives]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[Structured Data]]></category>
		<category><![CDATA[executive]]></category>
		<category><![CDATA[govtrack]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[procedure]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/09/procedural-uncertainty-normalization/</guid>
		<description><![CDATA[I always find it interesting how although our government is run by fairly strict procedural rules that have been written out in various places, starting with the constitution and ending somewhere past the horizon, sometimes it&#8217;s just impossible to locate exactly at what point in the procedural game &#8220;reality&#8221; is. For instance, the constitution outlines [...]]]></description>
			<content:encoded><![CDATA[<p>I always find it interesting how although our government is run by fairly strict procedural rules that have been written out in various places, starting with the constitution and ending somewhere past the horizon, sometimes it&#8217;s just impossible to locate exactly at what point in the procedural game &#8220;reality&#8221; is. For instance, the constitution outlines how a bill can become a law. But, at what point is a bill considered vetoed? If the president is signing the veto signature but misspells &#8220;veto&#8221; (or whatever he writes in this case, I have no idea), or is taken to the hospital before he writes the &#8220;o&#8221;, is the bill vetoed, or is it still awaiting a signature?</p>
<p>The reason this is interesting to me is that we like to capture reality in data. The Library of Congress and GovTrack both systematize (or in computer jargon &#8220;normalize&#8221;) the bill-becomes-a-law process. At every point in the game, a bill, in our data formats, is either in-progress, enacted, dead, etc. It must be in one of these states. After all, the constitution outlines exactly what states a bill can be in, so any bill *must* be in one of these states.</p>
<p><span id="more-231"></span></p>
<p>But if we&#8217;re not sure what state a bill is in, what state do we put it in in our data? There&#8217;s also the more important question- What do the lawmakers do if they disagree about what state a bill is in? (Actually, I would prefer to phrase it as &#8220;what state <b>they</b> are in&#8221;, but that&#8217;s another story.) Wikipedia <a href="http://en.wikipedia.org/wiki/Pocket_veto">describes</a> (what the editors of the page claim is) a current debacle over <a href="http://www.govtrack.us/congress/bill.xpd?bill=h110-1585">H.R. 1585: National Defense Authorization Act FY 2008</a>:</p>
<blockquote><p>In December of 2007, President George W. Bush pushed the pocket veto into murky waters by claiming that he had pocket vetoed H.R. 1585, the &#8220;National Defense Authorization Act for Fiscal Year 2008,&#8221; even though the House of Representatives had designated agents to receive presidential messages before adjourning. The bill had been previously passed by veto-proof majorities in both the House and the Senate [JT: and thus a traditional veto would have been futile].</p></blockquote>
<p>So was the bill (pocket) vetoed or not? Is the bill still in-progress? Assuming it was not pocket vetoed, after 10 legislative days without a traditional veto it becomes law, and us citizens would hate to be on that 11th day without either resolution on the pocket veto matter or a traditional veto, because then we as a country will not know whether this bill has become law. (Another question: How might the Supreme Court assert jurisdiction over this question.)</p>
<p>But back to the data. At one point, some time after Dec. 28, someone in the House responsible for updating the bill status information shown on THOMAS entered a new status line:</p>
<blockquote><p>Dec 28, 2007: Pocket Vetoed by President.</p></blockquote>
<p>GovTrack picked up on the change and shows that status currently, much to the confusion of several people emailing me about it. Looking back at THOMAS, it seems like someone realized that that was apparently quite a constitutional (if not political) claim and retracted that update, because <a href="http://thomas.loc.gov/cgi-bin/bdquery/z?d110:HR01585:@@@X">it not longer says that</a>. </p>
<p>In many cases citizens complain when the government takes things back, hiding information previously made public. That&#8217;s definitely not what I am getting at here. THOMAS is forced to show *something*, and when it doubt&#8230; well, what can you do but roll back history until we figure out what the next legislative step actually *was*.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/09/procedural-uncertainty-normalization/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Steve King introduces a new bill with a bit of Internet-transparency thrown in</title>
		<link>http://www.theopenhouseproject.com/2007/10/26/steve-king-introduces-a-new-bill-with-a-bit-of-internet-transparency-thrown-in/</link>
		<comments>http://www.theopenhouseproject.com/2007/10/26/steve-king-introduces-a-new-bill-with-a-bit-of-internet-transparency-thrown-in/#comments</comments>
		<pubDate>Fri, 26 Oct 2007 15:43:46 +0000</pubDate>
		<dc:creator>Joshua Tauberer</dc:creator>
				<category><![CDATA[Congress]]></category>
		<category><![CDATA[House of Representatives]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[appropriations]]></category>
		<category><![CDATA[procedure]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/10/26/steve-king-introduces-a-new-bill-with-a-bit-of-internet-transparency-thrown-in/</guid>
		<description><![CDATA[Steve King, a Republican from Iowa, has introduced a new bill that has a clause specifically about Internet-based transparency. (We know King from his bill H.R. 170: Sunlight Act of 2007, parts of which I think were integrated into the passed ethics reform bill. One part that wasn&#8217;t integrated was a provision to have bills [...]]]></description>
			<content:encoded><![CDATA[<p>Steve King, a Republican from Iowa, has introduced a new bill that has a clause specifically about Internet-based transparency. (We know King from his bill H.R. 170: Sunlight Act of 2007, parts of which I think were integrated into the passed ethics reform bill. One part that wasn&#8217;t integrated was a provision to have bills posted online for 48 hours before their consideration.) His new bill is <a href="http://www.govtrack.us/congress/bill.xpd?bill=hr110-776">H. Res. 776: Amending the Rules of the House of Representatives to require that rescission bills always be considered under open rules every year, and for other purposes.</a></p>
<p>This bill, like most of the 12 others he has introduced this year, takes a classical conservative position, here trying to reduce government spending. The real point of the bill is expressed best in one of its findings clauses:</p>
<blockquote><p>Whereas a rescissions bill, which would cut Federal spending, should be brought to the House floor at the beginning of every fiscal quarter to give Congress the opportunity to cut and cancel unnecessary, wasteful, and bloated government spending to eliminate the deficit;</p></blockquote>
<p>But the interesting part for us is:</p>
<blockquote><p>Whereas the process of cutting spending should be open to the public, by posting this spending cutting bill and its amendments on the Internet, so that Americans can exercise their right to contact their Members of Congress and make their views known</p></blockquote>
<p>It has a variant of the 48-hours language from his other bill applied specifically to rescission bills.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/10/26/steve-king-introduces-a-new-bill-with-a-bit-of-internet-transparency-thrown-in/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

