<?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; legislation</title>
	<atom:link href="http://www.theopenhouseproject.com/category/legislation/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>What happens after a bill becomes a law</title>
		<link>http://www.theopenhouseproject.com/2009/05/14/what-happens-after-a-bill-becomes-a-law/</link>
		<comments>http://www.theopenhouseproject.com/2009/05/14/what-happens-after-a-bill-becomes-a-law/#comments</comments>
		<pubDate>Thu, 14 May 2009 18:49:04 +0000</pubDate>
		<dc:creator>Daniel Schuman</dc:creator>
				<category><![CDATA[Congress]]></category>
		<category><![CDATA[legal research]]></category>
		<category><![CDATA[legalresearch]]></category>
		<category><![CDATA[legislation]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[Office of Law Revision Counsel]]></category>
		<category><![CDATA[OLRC]]></category>
		<category><![CDATA[statutes at large]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/?p=482</guid>
		<description><![CDATA[Many people remember from middle school the movie on how a bill becomes a law, but few civics courses teach about what happens afterward. On Monday, John, Josh, and I sat down with members of the Office of the Law Revision Counsel. Their job, in short, is to consolidate and codify laws passed by Congress [...]]]></description>
			<content:encoded><![CDATA[<p>Many people remember from middle school the movie on how a bill becomes a law, but few civics courses teach about what happens afterward. On Monday, <a href="http://sunlightfoundation.com/people/jwonderlich/">John</a>, <a href="http://sunlightfoundation.com/people/jruihley/">Josh</a>, and I sat down with members of the <a href="http://uscode.house.gov/">Office of the Law Revision Counsel</a>. Their <a href="http://uscode.house.gov/about/info.shtml">job</a>, in short, is to consolidate and codify laws passed by Congress based upon their subject matter &#8212; without making any substantive changes to the law &#8212; and to prepare the revised code for enactment into &#8220;positive law.&#8221;</p>
<p>U.S. <a href="http://www.llsdc.org/attachments/wysiwyg/544/Federal-Laws.pdf">statutory law</a> is organized into 50 books, known as titles. Each title should contain only those laws that have to do with a discrete subject area. In addition, it should only contain general and permanent laws &#8212; excluding provisions that apply only for a limited time (e.g., an annual appropriations law) or to a small number of people (e.g., a private law). For example, Title 7 should only contain permanent laws having to do with agriculture. Title 28 should only concern the judiciary and judicial procedure.</p>
<p>However, the last time that all law was organized in this way (or &#8220;codified&#8221;) was in 1926. Since then, entirely new areas of law have emerged that weren&#8217;t part of the original structure. Those laws have been placed into the code wherever was convenient, without Congress necessarily considering where would make the most sense.</p>
<p>Over time, this has <a href="http://www.llsdc.org/attachments/wysiwyg/544/usc-mysteries.pdf">created a mess</a>. Laws that are related to one another often are placed in completely different places. Occasionally, Congress enacts laws that contain technical errors. And, the passage of time and future legislation render certain provisions obsolete.</p>
<p>In response to these issues, the Office of Law Revision Counsel recodifies the laws: it reorganizes and rewords them. However, without legislative action, the office&#8217;s recodification does not have full legal force. In those instances, to see the actual text of the law, you have to look up the original bill passed by Congress and compare it against any additional laws that modify that original law.</p>
<p>Unless Congress enacts and the president signs the OLRC&#8217;s suggested revisions into law, the recodified text serves as a guide to how the law should be organized; it is <em>prima facie</em> (i.e., facial) <a href="http://uscode.house.gov/uscode-cgi/fastweb.exe?getdoc+uscview+t01t04+10112+0++()%20%20AND%20((1)%20ADJ%20USC)%3ACITE%20AND%20(USC%20w%2F10%20(204))%3ACITE">evidence</a> of what the law is. When Congress enacts the OLRC&#8217;s codification, it transforms the code into &#8220;<a href="http://www.llsdc.org/attachments/wysiwyg/544/usc-pos-law-codification.pdf">positive law</a>,&#8221; and repeals the statutes that originally created the laws. The only statutory law left is that newly-passed U.S. Code title.</p>
<p>As things currently stand, 24 titles have been revised and enacted into law. The other titles remain only <em>prima facie</em> evidence of the law.</p>
<p>The process of turning proposed codifications of the law into positive law can take a lot of time. After the OLRC proposes revisions to the code, it invites comments from federal agencies and non-governmental stakeholders in a process that can take more than a year. Currently, the OLRC has proposed <a href="http://uscode.house.gov/codification/legislation.shtml">six revisions</a> to U.S. law, including the addition of four new titles to the code.</p>
<p>Congress, however, isn&#8217;t always so quick to act. For example, legislation to codify Title 41, concerning public contracts, was first introduced in the House of Representatives in May 2004.  It has been reintroduced each subsequent Congress since then, and was finally <a href="http://www.govtrack.us/congress/bill.xpd?bill=h111-1107">passed</a> by the House of Representatives on May 6, 2009. The ball is now in the Senate&#8217;s court.</p>
<p>The OLRC has been taking steps to update its services. It recently started a <a href="http://twitter.com/uscode">twitter feed</a>, and it is interesting to watch as the OLRC announces where newly enacted legislation should be classified. In addition, OLRC recently updated its &#8220;<a href="http://uscode.house.gov/popularnames/popularnames.htm ">popular name tool</a>,&#8221; which allows users to find legislation by its popularly known name. Another useful resource from the office is its online <a href="http://uscode.house.gov/search/criteria.shtml">search engine</a>, which returns the most recently published version of the code plus a page containing any subsequent amendments or notes, and Public Law citation information. I can&#8217;t wait to see what other improvements the office will make to their web site.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2009/05/14/what-happens-after-a-bill-becomes-a-law/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bulk data downloads approved in the omnibus spending bill (success!)</title>
		<link>http://www.theopenhouseproject.com/2009/03/11/bulk-data-downloads-approved-in-the-omnibus-spending-bill-success/</link>
		<comments>http://www.theopenhouseproject.com/2009/03/11/bulk-data-downloads-approved-in-the-omnibus-spending-bill-success/#comments</comments>
		<pubDate>Wed, 11 Mar 2009 14:08:13 +0000</pubDate>
		<dc:creator>Joshua Tauberer</dc:creator>
				<category><![CDATA[Congress]]></category>
		<category><![CDATA[GPO]]></category>
		<category><![CDATA[Structured Data]]></category>
		<category><![CDATA[appropriations]]></category>
		<category><![CDATA[approps]]></category>
		<category><![CDATA[clerk of the house]]></category>
		<category><![CDATA[govtrack]]></category>
		<category><![CDATA[legislation]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[maplight]]></category>
		<category><![CDATA[openhouseproject]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/?p=462</guid>
		<description><![CDATA[Two recommendations of our report have been moved forward in the FY09 omnibus appropriations bill (H.R. 1105) which cleared the Senate yesterday and the House last month. The first recommendation in our chapter on legislative databases was that the Library of Congress make its bill status database directly available to the public and that the [...]]]></description>
			<content:encoded><![CDATA[<p>Two recommendations of our report have been moved forward in the <a href="http://www.govtrack.us/congress/bill.xpd?bill=h111-1105">FY09 omnibus appropriations bill (H.R. 1105)</a> which cleared the Senate yesterday and the House last month. The first recommendation in our chapter on <a href="http://http//www.theopenhouseproject.com/the-open-house-project-report/3-legislation-database/">legislative databases</a> was that the Library of Congress make its bill status database directly available to the public and that the GPO not sell legislative documents to the public. These have been the two issues I&#8217;ve had my sights on over the last three years (probably starting <a href="http://groups.yahoo.com/group/committeewatch/message/153">here</a>). The second recommendation was about <a href="http://www.theopenhouseproject.com/the-open-house-project-report/12-coordinating-web-standards/">coordinating web standards</a> across Congress. These recommendations are addressed in two paragraphs the <a href="http://appropriations.house.gov/FY2009_consolidated.shtml">House statement accompanying the bill</a> for Division G &#8211; Legislative Branch, which is almost like being law itself.</p>
<p>The two paragraphs were added by <a href="http://honda.house.gov/">Congressman Mike Honda</a> of California, one of our champions of the use of technology to further transparency and civic engagement. John Wonderlich of Sunlight Foundation, Rob Pierson in Honda&#8217;s office, and I collaborated on this over a long period of time. Honda got involved in 2007 <a href="http://www.theopenhouseproject.com/2008/02/01/congressman-honda-on-the-open-house-cause/">asking the Library to look into this</a> and then in 2008 <a href="http://www.theopenhouseproject.com/2008/07/14/legislative-databases-recommendation-makes-it-to-house-leg-branch-appropriations-markup/">getting the paragraphs added to the bill markup</a>.</p>
<p><span id="more-462"></span></p>
<p>So here they are:</p>
<blockquote><p>
Congressional Technology Coordination.-The House of Representatives needs a strategic and coordinated plan that will prepare for the future technology needs of the institution. A 2006 report commissioned by the Chief Administrative Officer and the Committee on House Administration, entitled Strategic Technology Road Map for the Ten Year Vision of Technology in the House of Representatives, provided a suggested structure for Information Technology evaluation and decision making. The Chief Administrative Officer, the Clerk, and the Sergeant at Arms are asked to prepare a report by June 30, 2009 on their efforts or plans to develop House-wide data-sharing standards; implement standard legislative document formats; address the increasing resource challenges of Member offices; and identify disparate systems throughout the institution that prevent it from taking advantage of economies of scale.  [page 2]</p></blockquote>
<p>and</p>
<blockquote><p>Public Access to Legislative Data. There is support for enhancing public access to legislative documents, bill status, summary information, and other legislative data through more direct methods such as bulk data downloads and other means of no-charge digital access to legislative databases. The Library of Congress, Congressional Research Service, and Government Printing Office and the appropriate entities of the House of Representatives are directed to prepare a report on the feasibility of providing advanced search capabilities. This report is to be provided to the Committees on Appropriations of the House and Senate within 120 days of the release of Legislative Information System 2.0. [page 11]</p></blockquote>
<p>According to an article in <a href="http://blog.wired.com/27bstroke6/2009/03/federal-bill-wo.html">Wired</a>: â€œIn our web 2.0 world, we can empower the public by providing them with raw data that they can remix and reuse in new and innovative ways,&#8221; says Honda, who is vice chairman of the Appropriations Subcommittee on the Legislative Branch. &#8220;With these tools, the public can collaborate on projects that can help legislators to create better policies to address the pressing challenges facing our nation.â€ There&#8217;s also a good <a href="http://www.motherjones.com/politics/2009/03/congressional-data-mining-coming-soon">article at Mother Jones</a> and a nice <a href="http://radar.oreilly.com/2009/03/bulk-data-downloads-government-transparency-breakthrough.html">post by Tim O&#8217;Reilly</a>.</p>
<p>The concept of bulk data downloads hasn&#8217;t been missed by many parts of the government. The Census Bureau and the Federal Elections Commission, for instance, are fantastic at sharing with the public as much as they can. In the latter case it is electronic versions of campaign contribution filings, which is obviously very important for preventing corruption. But, there are significant gaps in other areas of the government where a little legislating is necessary.  Here we&#8217;re talking about information on bills in congress going back around two decades, and the information going forward.</p>
<p>The Library of Congress has a database of this information but they don&#8217;t share it with the public. Sharing it would mean that creating sites like GovTrack &#8212; and the various other sites that use data from GovTrack including OpenCongress and MAPLight.org &#8212; would be a little easier, but also a little more accurate. Right now GovTrack goes through a roundabout process to reverse-engineer the same information we are seeking from this database. Basically, we already have the information by scraping it off of thomas.loc.gov &#8212; we&#8217;d just rather get it directly rather than the way it is assembled now. So because I go through so much trouble to reverse-engineer the data I want, not so many things will change in an obvious way on GovTrack &#8212; it&#8217;ll just be that my life will be a little easier and the information will be a little more complete and up to date. But, you can expect to see other sites spring up doing new and interesting things with the information &#8212; ways of visualizing the congressional process that we couldn&#8217;t yet imagine. </p>
<p>The Government Printing Office is mentioned because of how they make legislative documents like the text of bills available to the public. PDFs and text-only versions are made available for free already. No problem there. But they have other files that would be useful to sites like GovTrack which they sell at ridiculously high subscription prices. Those files would make comparisons of bill text easier to produce (although GovTrack already has this feature, again by essentially going about it the hard way). If you think about it from the perspective that some bills go through Congress so fast no one has time to read them through, being able to apply technology to the process is so important, like to detect changes in the text of bills between versions to make it easier for people to get through it. This is what GPO is preventing by selling some of its files, rather than providing them to the public for free (which it is essentially mandated to do for most documents &#8212; why they exempt certain documents is not known). </p>
<p>Now, it&#8217;s not that the Library doesn&#8217;t necessarily *want* to share its database. It&#8217;s just that sharing it wasn&#8217;t a part of their mandate from Congress and they don&#8217;t want to upset Congress by stepping out of their mandate. The omnibus bill is an indication from the House to the Library that this would be something supported by Congress. (My understanding is that the Library has been seeking permission from Congress to do some of these things, probably in response to a previous push for this, but the omnibus legislation has been in the works concurrently.) </p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2009/03/11/bulk-data-downloads-approved-in-the-omnibus-spending-bill-success/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Disclosure Legislation from Senate Judiciary</title>
		<link>http://www.theopenhouseproject.com/2008/03/07/disclosure-legislation-from-senate-judiciary/</link>
		<comments>http://www.theopenhouseproject.com/2008/03/07/disclosure-legislation-from-senate-judiciary/#comments</comments>
		<pubDate>Fri, 07 Mar 2008 18:20:24 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[disclosure]]></category>
		<category><![CDATA[legislation]]></category>
		<category><![CDATA[senate]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/03/07/disclosure-legislation-from-senate-judiciary/</guid>
		<description><![CDATA[A flurry of new disclosure related legislation from the Senate Judiciary Committee:
The Sunshine in Litigation Act requires that judges consider public health in deciding whether to release the results of litigation.
The bipartisan Ã¢â‚¬Å“Sunshine in Litigation ActÃ¢â‚¬? was prompted by dozens of cases in which hazards and threats to public health were not disclosed during court [...]]]></description>
			<content:encoded><![CDATA[<p>A flurry of new disclosure related legislation from the Senate Judiciary Committee:</p>
<p>The <a href="http://leahy.senate.gov/press/200803/030608f.html">Sunshine in Litigation Act</a> requires that judges consider public health in deciding whether to release the results of litigation.</p>
<blockquote><p>The bipartisan Ã¢â‚¬Å“Sunshine in Litigation ActÃ¢â‚¬? was prompted by dozens of cases in which hazards and threats to public health were not disclosed during court lawsuits or out of court settlements and subsequently resulted in additional fatalities, serious injuries and illnesses. </p></blockquote>
<p>The <a href="http://leahy.senate.gov/press/200803/030608e.html">Free Flow of Information Act</a> deals with media figures&#8217; handling of confidential sources:</p>
<blockquote>
<p>Last month, a former USA Today reporter was held in contempt of court for refusing to reveal confidential sources cited in two articles written in 2002, and she is now facing fines of $500 to $5,000 a day.  In recent years, dozens of reporters have been questioned by federal prosecutors about their sources. </p>
<p>The legislation is supported by a wide array of media organizations including the Newspaper Association of America, the Associated Press, the American Society of Newspaper Editors, The New York Times Company, The Washington Post, the New England Press Association, the Vermont Press Association, and the Pennsylvania Newspaper Association.</p>
</blockquote>
<p>The <a href="http://leahy.senate.gov/press/200803/030608c.html">Sunshine in Courtroom Act</a> deals with cameras in the courts:</p>
<blockquote>
<p>Federal courts lag behind all 50 state judiciaries, which have all allowed some form of audio or video coverage of court proceedings.  Many Americans are unable to travel to witness some of the most important public arguments and actions of our Federal judiciary, including attending proceedings at the nationÃ¢â‚¬â„¢s 13 appellate courts and the Supreme Court.  The Sunshine in the Courtroom Act (S. 352), passed by the Committee today, would help increase public access through emerging technologies.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/03/07/disclosure-legislation-from-senate-judiciary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

