<?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; library of congress</title>
	<atom:link href="http://www.theopenhouseproject.com/category/library-of-congress/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>Update on bulk data from Congress</title>
		<link>http://www.theopenhouseproject.com/2009/04/17/update-on-bulk-data-from-congress/</link>
		<comments>http://www.theopenhouseproject.com/2009/04/17/update-on-bulk-data-from-congress/#comments</comments>
		<pubDate>Fri, 17 Apr 2009 10:52:24 +0000</pubDate>
		<dc:creator>Joshua Tauberer</dc:creator>
				<category><![CDATA[GPO]]></category>
		<category><![CDATA[bulk data download]]></category>
		<category><![CDATA[clerk of the house]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[senate]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/?p=474</guid>
		<description><![CDATA[One of the Open House Project&#8217;s recommendations was that Congress share its legislative data with the public in bulk and I&#8217;ve had a long history of posts on the subject. Over at the Free Gov info blog (link), Bob Tapella, Public Printer at the Government Printing Office, tells us that they are responding to this [...]]]></description>
			<content:encoded><![CDATA[<p>One of the Open House Project&#8217;s recommendations was that Congress share its legislative data with the public <i>in bulk</i> and I&#8217;ve had a long history of posts on the subject. Over at the Free Gov info blog (<a href="http://freegovinfo.info/node/2509#comment-26452">link</a>), Bob Tapella, Public Printer at the Government Printing Office, tells us that they are responding to this recommendation. He writes in a comment (presumably it is really him):</p>
<blockquote><p>We have recently been called upon by Congress in the joint explanatory statement on the H.R. 1105, to work with the Library of Congress, including the Congressional Research Service, and the Law Library of Congress, to discuss access to bulk data. Specifically, the language is as follows:</p>
<p>[JT: omitted --- I've posted it before <a href="http://www.theopenhouseproject.com/2009/03/11/bulk-data-downloads-approved-in-the-omnibus-spending-bill-success/">here</a>]</p>
<p>To address this request, a Legislative branch task force has been assembled consisting of representatives from the offices of the Secretary of the Senate, the Clerk of the House, the Library of Congress, Congressional Research Service, the Law Library of Congress, and GPO. This task force has already met and is working to develop a position on access to bulk data. We will look to this work and the review by Congress to help guide our work on making bulk data accessible.</p></blockquote>
<p>Grin.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2009/04/17/update-on-bulk-data-from-congress/feed/</wfw:commentRss>
		<slash:comments>1</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>Legislative Databases recommendation makes it to House Leg Branch Appropriations markup</title>
		<link>http://www.theopenhouseproject.com/2008/07/14/legislative-databases-recommendation-makes-it-to-house-leg-branch-appropriations-markup/</link>
		<comments>http://www.theopenhouseproject.com/2008/07/14/legislative-databases-recommendation-makes-it-to-house-leg-branch-appropriations-markup/#comments</comments>
		<pubDate>Mon, 14 Jul 2008 17:42:28 +0000</pubDate>
		<dc:creator>Joshua Tauberer</dc:creator>
				<category><![CDATA[GPO]]></category>
		<category><![CDATA[House of Representatives]]></category>
		<category><![CDATA[LoC]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[Structured Data]]></category>
		<category><![CDATA[appropriations]]></category>
		<category><![CDATA[cha]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[ohp]]></category>
		<category><![CDATA[openhouseproject]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/?p=375</guid>
		<description><![CDATA[I&#8217;m ecstatic. All right, so this all goes back to late 2006, a bunch of people sitting at their computers writing some emails about what Congress should do with data. I distinctly remember Dan Newman and I both thinking that the Library of Congress should make its raw legislative database (that powers THOMAS) available directly [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m ecstatic. All right, so this all goes back to late 2006, a bunch of people sitting at their computers writing some emails about what Congress <em>should</em> do with data. I distinctly remember Dan Newman and I both thinking that the Library of Congress should make its raw legislative database (that powers THOMAS) available directly to us to build applications off of, rather than the screen-scraping that I was doing. One thing leads to another, the Open House Project, <a href="http://http://www.theopenhouseproject.com/the-open-house-project-report/3-legislation-database/">the legislative databases section of the OHP report</a> in May 2007 (which I principally wrote), then later that year with the support of Rep. Mike Honda, in November <a href="http://www.govexec.com/story_page.cfm?filepath=/dailyfed/0108/012308tdpm1.htm">CHA asked the LOC to look into the issue</a> (<a href="http://www.theopenhouseproject.com/2008/02/01/congressman-honda-on-the-open-house-cause/">more</a>), and then in the last month his office submitted text for the House Legislative Branch Appropriations Report, which made it through subcommittee markup of the bill, to give this request a little more teeth (like, ehm, the force of law).</p>
<p>His office also submitted a second paragraph which I&#8217;ll get to below.<br />
<span id="more-375"></span><br />
Rob Pierson in Honda&#8217;s office writes on the OHP mail list:</p>
<blockquote><p>I&#8217;ve mentioned on the list some of the steps my boss (Congressman Honda) has been taking, with counsel from many folks on this list, to guide Congressional policies on the path towards effectively leveraging technology to open up access to the public. There are actually quite a few other staffers who also follow this list, and we&#8217;ve certainly learned quite a bit from the conversations posted here, so I wanted to throw out a quick note of appreciation to everyone who has been contributing to the discussions.</p>
<p>With guidance from the conversations on this list (and the OHP report), Congressman Honda recently submitted the following sections into the House Legislative Branch Appropriations Report. The following (or possibly very similar versions) were included in the Leg Branch Subcommittee markup of the bill:</p>
<p>*Public Access to Legislative Data (as submitted)*</p>
<p>The Committee believes that the public should have improved access to legislative information through more advanced search capabilities such as those available through the Library of Congress&#8217; Legislative<br />
Information System. The Committee also supports 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 Committee requests that the Library and Government Printing Office report on the progress towards these goals within 90 days of enactment of this Act.
</p></blockquote>
<p>Note that the GPO has also been stuck in there. More more on that, <a href="http://www.theopenhouseproject.com/2007/11/14/better-late-than-never-gpo-responds-to-my-question-1-year-later/">see this post</a>.</p>
<p>The second paragraph that Honda&#8217;s office submitted John noted was parallel to the final chapter of our report, <a href="http://www.theopenhouseproject.com/the-open-house-project-report/12-coordinating-web-standards/">Coordinating Web Standards</a>. (Hmm, I principally wrote that chapter too&#8230;.)</p>
<blockquote><p>*Congressional Technology Coordination (as submitted)*</p>
<p>The Committee recognizes the need for the House of Representatives to develop 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 an IT evaluation and decision-making process.<br />
No later than 90 days after the enactment of this Act, the Committee requests that the Chief Administrative Officer, the Clerk, and the Sergeant at Arms report to the Committee of their efforts 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, which prevent it from taking advantage of economies of scale.</p></blockquote>
<p>This is of course fantastic news for anyone that supports transparency, which is, well, everyone in their right mind, I think. So thanks to Congressman Honda for taking the initiative on this!</p>
<p>(Other links: <a href="http://www.theopenhouseproject.com/2007/06/27/house-leg-branch-appropriations-review/">last year&#8217;s leg branch appropriations blog post</a>, <a href="http://www.theopenhouseproject.com/2007/01/25/mash-ups-for-government-transparency/">my first or one of my first posts here about structured data</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/07/14/legislative-databases-recommendation-makes-it-to-house-leg-branch-appropriations-markup/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Reading Notes on The Documentation of Congress</title>
		<link>http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/#comments</comments>
		<pubDate>Sun, 27 Jan 2008 22:45:23 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[CLA]]></category>
		<category><![CDATA[Member Web Sites]]></category>
		<category><![CDATA[NARA]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[legal research]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[lobbying]]></category>
		<category><![CDATA[lobbying disclosure]]></category>
		<category><![CDATA[ota]]></category>
		<category><![CDATA[preservation]]></category>
		<category><![CDATA[senate]]></category>
		<category><![CDATA[spub 102-20]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/</guid>
		<description><![CDATA[After going through the trouble of obtaining and digitizing the 1992 report on congressional documentation, I&#8217;ve started going systematically through the document, and, in an attempt to read more closely, have been taking notes.Ã‚Â  This is a long post, but the parallels with the Open House Project are startling to me, as are the contrasts: [...]]]></description>
			<content:encoded><![CDATA[<p>After going through the trouble of obtaining and digitizing the 1992 report on congressional documentation, I&#8217;ve started going systematically through the document, and, in an attempt to read more closely, have been taking notes.Ã‚Â  This is a long post, but the parallels with the Open House Project are startling to me, as are the contrasts: since 1992 the consumer of public information has undergone a fundamental transformation, leading what was once considered relevant for archivists or researchers to become essential to practitioners of a new online breed of civic engagement.</p>
<p>For more background on the document, see <a href="http://www.theopenhouseproject.com/2007/12/19/spub-102-20/">this post</a>, and for updates, I&#8217;m keeping notes on <a href="http://docs.google.com/Doc?id=ddj3rw4t_2276k773kfc">this page</a>, from which future updates will likely be pulled.</p>
<p>-JohnÃ‚Â  (start review)</p>
<p><span id="more-242"></span></p>
<p>foreword:<br />
compiled by the Task Force on the Documentation of Congress of the Society of American Archivists Congressional Archivists Roundtable, coming from 1989&#8217;s &#8220;Understanding Congress: A Bicentennial Research Conference&#8221;.Ã‚Â  &#8220;the fragmented nature of congressional primary source documentation&#8221; is partly responsible for the lack of scholarly writing on the legislative branch.Ã‚Â  Report is a &#8220;study of the archival sources that document the operations of Congress.&#8221;</p>
<p>Preface:<br />
&#8220;Because the documentation of Congress, in particular, most directly reveals the will of the people as expressed through their elected representatives, it is especially crucial to preserve evidence and information about the legislative process and make it accessible to the public.&#8221;Ã‚Â  (gives great detail on problems with public access: &#8220;fragmented and geographically scattered; collections are often voluminous, of complex arrangement, inadequately indexed, and in poor physical condition; contents of many collections are uneven, with unexplained gaps in information; and repositories that receive these collections frequently lack the resources to provide state-of-the-art arrangement, description, and archival preservation.&#8221;Ã‚Â  Project undertaken by the Task Force on Congressional Documentation of the Society of American Archivists&#8217; Congressional Archivists Roundtable (that&#8217;s correctly transcribed).Ã‚Â  &#8220;many of its suggestions will take years to be carried out; others can be effected immediately.&#8221;Ã‚Â  &#8220;Among the most pressing needs are actions to improve the documentation of legislation, representation, congressional leadership, political activities, and programs of congressional support agencies.Ã‚Â  Other recommendations are aimed at better documenting Congress&#8217; relations and interaction with media, the executive and the judicial branches, lobbyists, and think tanks.Ã‚Â  Finally, steps are suggested to improve documentation of the administration of Congress&#8217; to fill gaps in the historical record through structured, coordinated oral history interview programs; and to improve the preservation of congressional sources.</p>
<p>Intro:<br />
Report organized into congressional &#8220;functions&#8221;, &#8220;documentation&#8221;, and &#8220;recommendations&#8221;.Ã‚Â  (apparently there&#8217;s a 1978 report from the National Study Commission on the Records and Documents of Federal Officials, which &#8220;recommended that office files and personal papers of members of Congress be legally designated as federal records with guaranteed public access after fifteen years&#8221; (this wasn&#8217;t implemented, but that report would be useful to find).Ã‚Â  This report led to a 2 day conference, where they decided to publish a handbook on member records management.Ã‚Â  1985 then saw a 2 day conference on documenting Congress, put on by the &#8220;Dirksen Congressional Center and the national Historical Publications and Records Commission&#8221; (another great report to find)Ã‚Â  This conference led to the creation of the Congressional Archivists Roundtable of the Society of American Archivists (which, in turn, led to the current day 2008 Advisory Committee on the Records of Congress (<a id="u05t" title="link" href="http://www.archives.gov/legislative/cla/advisory-committee/">link</a>).Ã‚Â  (The Congressional Archivists Roundtable appears to be defunct, perhaps being defunded in the mid 90&#8217;s?)Ã‚Â  &#8220;the &#8220;importance&#8221; [of congressional material] had not led to a determined effort to systematically appraise and preserve a documentary record of Congress.&#8221; (page vi)Ã‚Â  Problems archivists face: &#8220;the information explosion, the computer and telecommunications revolutions, insufficient resources for archival work as government and repository budgets tighten, and the lack of clearly defined long-term strategies and action plans to accomplish overall documentary objectives.&#8221;Ã‚Â  The response to this is a strategy, which matches the organization of this document (functions, documentation, and recommendations).Ã‚Â Ã‚Â Ã‚Â  The report then lists participants.</p>
<p>Page ix lists contents, listing the major topics to be examined: Institutional Setting, the Legislative Process, Representation, Political Activities, External Relations, Administration and Support, Research Use of Congressional Collections, Appendices, and Notes.</p>
<p>Summary Report and Recommendations<br />
Repeats problem.Ã‚Â  &#8220;Historical records do not simply materialize.&#8221;Ã‚Â  They&#8217;re trying to balance the needs of three authorities: members and officials of Congress &#8220;individually responsible for the on-site management of the information that is collected and maintained in their offices&#8221;, NARA&#8217;s CLA, and the &#8220;literally hundreds of archival repositories across the country [that] preserve and provide access to the personal papers that are deposited in them by the members&#8221;.Ã‚Â  This listing seems to me to be a result of their institutional setting, my take on the jurisdictions at work in congressional information access can be found <a id="g9b0" title="here" href="http://www.theopenhouseproject.com/2008/01/23/governmental-support-entities-with-a-role-in-transparency-statutory-basis-for-negotiated-terrain/">here</a>.</p>
<p>Major Findings:<br />
1. &#8220;Congressional committees are relatively, although not uniformly, well documented, [but] there is great variation in the documentary quality of individual members&#8217; collections&#8221;Ã‚Â  This conclusion strikes me as a result of writing in the mid 1990s, when paying meaningful attention to legislative affairs through the Internet was rather impossible.Ã‚Â  There was little difference then between &#8220;well documented&#8221; and &#8220;publicly available (online)&#8221;, where now that difference is quite clear.Ã‚Â  What is &#8220;well documented&#8221;, like committee hearing transcripts, or the upcoming schedules for committee hearings, in the archival sense, can also be useless for those hoping to actually watch Congress in action, even in time for upcoming elections, which is a much lower bar than the near-real time awareness lobbyists need in order to be legislatively relevant.Ã‚Â  Thus the report&#8217;s focus on member records, which were managed in a much less standard manner then.</p>
<p>2. The need for a &#8220;coordinated retention plan that meets the long-term needs of Congress&#8221; as applied to congressional support agencies.Ã‚Â  The GAO was doing well, the (now defunct) Office of Technology Assessment and Government Printing Office had partial programs, and the CRS and CBO had none.Ã‚Â  Again, no real mention of OTA and GAO providing public documentation while CRS does not.Ã‚Â  Our expectations of finding things online has led to a new set of expectations.Ã‚Â  (well, that and the expectation of equal access to publicly funded documents, since CRS reports are sold through private companies.)</p>
<p>3. Executive Branch and Judicial Branches are doing a rather good job, but are relevant here nevertheless.</p>
<p>4. Other sources they feel have been thitherto overlooked: nat&#8217;l, congressional, and individual campaign committees, political party organizations; and congressional member organizations and caucuses.Ã‚Â  (still true, 16 years later)</p>
<p>5. Member documentary repositories are hard to use, recommend better practices here.</p>
<p>6. Member materials will be better processed if offices hire and train archivists, and keep up with documents processing.</p>
<p>The Report then launches into specific recommendations, lining up with the table of contents, but in summary form.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Governmental Support Entities with a Role in Transparency: Statutory Basis for Negotiated Terrain</title>
		<link>http://www.theopenhouseproject.com/2008/01/23/governmental-support-entities-with-a-role-in-transparency-statutory-basis-for-negotiated-terrain/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/23/governmental-support-entities-with-a-role-in-transparency-statutory-basis-for-negotiated-terrain/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 21:15:33 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[House of Representatives]]></category>
		<category><![CDATA[Open Senate Project]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[ota]]></category>
		<category><![CDATA[senate]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/23/governmental-support-entities-with-a-role-in-transparency-statutory-basis-for-negotiated-terrain/</guid>
		<description><![CDATA[In order to clarify this post, I wanted to organize some of the governmental support agencies and bodies with responsibility or jurisdiction over congressional information access.Ã‚Â  This list is still probably partial, as any such list would be, since jurisdiction and responsibility are ultimately a matter of habit and practice as much as they are [...]]]></description>
			<content:encoded><![CDATA[<p>In order to clarify <a id="g57a" title="this post" href="http://www.theopenhouseproject.com/2008/01/11/fdsys-gpos-vision-fdlp/">this post</a>, I wanted to organize some of the governmental support agencies and bodies with responsibility or jurisdiction over congressional information access.Ã‚Â  This list is still probably partial, as any such list would be, since jurisdiction and responsibility are ultimately a matter of habit and practice as much as they are statutory mandate, appropriations, or formal jurisdiction.</p>
<p>More background discussion can be found <a href="http://groups.google.com/group/openhouseproject/browse_thread/thread/941d1d36d85d7f9e">here</a>.</p>
<p>Congressional Budget Office (<a id="dkd." title="CBO" href="http://www.cbo.gov/">CBO</a>): CBO <a id="kv36" title="intro PDF" href="http://www.cbo.gov/aboutcbo/introCBO.pdf">intro PDF</a> from their website, see also Congressional Budget Act of 1974</p>
<p>General Accountability Office (<a id="qxoh" title="GAO" href="http://www.gao.gov/">GAO</a>):</p>
<div style="margin-left: 40px">Office of Technological Assessment (defunct, then <a id="ujiz" title="reinstated" href="http://www.theopenhouseproject.com/2008/01/04/ota-update/">reinstated</a>, in limited way)</div>
<p>Library of Congress (<a id="q12o" title="LOC" href="http://www.loc.gov/">LOC</a>):</p>
<div style="margin-left: 40px">THOMAS, Congressional Research Service (CRS) running LIS on LIMS, DLR</div>
<p>Government Printing Office (GPO)</p>
<div style="margin-left: 40px">Federal Depository Library Program (FDLP) (<a id="aed9" title="jurisdiction" href="http://freegovinfo.info/node/483.">jurisdiction</a> viaÃ‚Â  Free Government Information)</div>
<p>National Archives and Records Administration (<a id="ve0f" title="NARA" href="http://www.dailykos.com/comments/2008/1/14/12636/5764/7#c7">NARA</a>)</p>
<div style="margin-left: 40px">Center for Legislative Archives (<a id="rwsh" title="CLA" href="http://www.archives.gov/legislative/">CLA</a>)</div>
<p>Chief Administrative Officer (of the House) (<a id="u88m" title="CAO" href="http://cao.house.gov/">CAO</a>)</p>
<p>Speaker of the House (<a id="ngr9" title="link" href="http://speaker.house.gov/">link</a>)</p>
<div style="margin-left: 40px">
House Historian (<a id="pyz2" title="link" href="http://en.wikipedia.org/wiki/Historian_of_the_United_States_House_of_Representatives">link</a>)Ã‚Â  (under the speaker&#8217;s jurisdiction)</p>
<p>Clerk of the House (<a id="dwgl" title="link" href="http://clerk.house.gov/">link</a>)</p>
<div style="margin-left: 40px">Office of History and Preservation (<a id="d0xd" title="OHP" href="http://en.wikipedia.org/wiki/Clerk_of_the_United_States_House_of_Representatives#Office_of_History_and_Preservation_.28OHP.29">OHP</a>)</div>
</div>
<p>Secretary of the Senate (<a id="zmnx" title="link" href="http://www.senate.gov/reference/office/secretary_of_senate.htm">link</a>)</p>
<div style="margin-left: 40px">Senate Historical Office (<a id="f1lm" title="link" href="http://www.senate.gov/artandhistory/history/common/generic/Senate_Historical_Office.htm">link</a>)</p>
<p>Senate Office of Public Records (<a id="bwrj" title="SOPR" href="http://sopr.senate.gov/">SOPR</a>)</div>
<p>Senate Rules Committee (<a id="dwfx" title="link" href="http://rules.senate.gov/purpose/">link</a>)</p>
<p>Senate Sergeant at Arms (<a id="id-b" title="link" href="http://www.senate.gov/reference/office/sergeant_at_arms.htm">link</a>)</p>
<p>Committee on House Administration (<a id="t9-6" title="CHA" href="http://cha.house.gov/">CHA</a>)</p>
<p>Joint Committee on Printing (<a id="odo-" title="JCP" href="http://www.house.gov/jcp/">JCP</a>)</p>
<p>Senate Homeland Security and Government Affairs Committee (<a id="wd3-" title="HSGA" href="http://hsgac.senate.gov/">HSGA</a>)</p>
<p>House Committee on Oversight and Government Reform (<a id="lwc4" title="link" href="http://oversight.house.gov/">link</a>)</p>
<p>Advisory Committee on the Records of Congress (<a id="u-eh" title="link" href="http://www.archives.gov/about/laws/advisory-committee.html">link</a>)</p>
<p>Senate Historical Office (<a id="f1lm" title="link" href="http://www.senate.gov/artandhistory/history/common/generic/Senate_Historical_Office.htm">link</a>)</p>
<p>Legislative Resource Center (<a id="a28b" title="LRC" href="http://clerk.house.gov/about/offices_lrc.html">LRC</a> )<br />
<br style="font-weight: bold" /><strong>Executive Branch</strong></p>
<p>General Services Administration (<a id="kzfs" title="GSA" href="http://www.gsa.gov/Portal/gsa/ep/home.do?tabId=0">GSA</a>), (executive branch)</p>
<div style="margin-left: 40px">CIO Counsel (<a id="udik" title="link" href="http://www.cio.gov/index.cfm?function=aboutthecouncil">link</a>)Ã‚Â  (also see federal indexes: usa.gov, info.gov, (fedworld.gov by us commerce dept)</div>
<p>Office of Management and Budget (<a id="yz9j" title="OMB" href="http://www.whitehouse.gov/omb/">OMB</a>)</p>
<p><strong>Judicial Branch</strong></p>
<p>Federal Judicial Center (<a id="jz2w" title="FJC" href="http://www.fjc.gov/">FJC</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/23/governmental-support-entities-with-a-role-in-transparency-statutory-basis-for-negotiated-terrain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recent Passed and Pending Transparency Reform Legislation</title>
		<link>http://www.theopenhouseproject.com/2008/01/23/recent-passed-and-pending-transparency-reform-legislation/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/23/recent-passed-and-pending-transparency-reform-legislation/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 21:01:27 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[Congress]]></category>
		<category><![CDATA[House of Representatives]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[library of congress]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/23/recent-passed-and-pending-transparency-reform-legislation/</guid>
		<description><![CDATA[From the Open House Project Google Group discussion, here&#8217;s a partial list of recent transparency reform legislation, passed or pending.
Transparency bills that passed in 110th Congress, 1st session:
1. S.1 Honest Leadership and Open Government Act of 2007:



Requires online posting of committee hearing transcripts/audio/video (Senate only)
Expands lobbyist disclosure to require quarterly filing, disclosure of bundled contributions, [...]]]></description>
			<content:encoded><![CDATA[<p>From the Open House Project Google Group <a href="http://groups.google.com/group/openhouseproject/browse_thread/thread/a4a3d4a84e3825e4">discussion</a>, here&#8217;s a partial list of recent transparency reform legislation, passed or pending.</p>
<p>Transparency bills that passed in 110th Congress, 1st session:</p>
<p>1. S.1 Honest Leadership and Open Government Act of 2007:</p>
<div style="margin-left: 40px">
<div class="Ih2E3d">
<ul>
<li>Requires online posting of committee hearing transcripts/audio/video (Senate only)</li>
<li>Expands lobbyist disclosure to require quarterly filing, disclosure of bundled contributions, mandatory electronic filing and maintenance of online databases, disclosure of past executive branch and congressional experience, mandatory electronic filing and maintenance of online databases for foreign lobbyists</li>
<li>Disclosure of employment negotiations for Members and staff</li>
<li>Creation of online databases for travel reports (House and Senate) and personal financial disclosure (House only)</li>
<li>Disclosure of earmarks in bills online (loopholes, of course, exist)</li>
</ul>
</div>
</div>
<p>2. S.2488 OPEN Government Act of 2007:</p>
<div class="Ih2E3d">
<div style="margin-left: 40px"></div>
<ul style="margin-left: 40px">
<li>Encourages faster FOIA response time in agencies</li>
<li>Enables FOIA requesters to track the status of their requests</li>
<li>Brings contractors under FOIA</li>
<li>Expands the basis to waive fees for FOIA duplication</li>
<li>Creates an Office of Government Information within NARA</li>
</ul>
</div>
<p>3. OTA funding <a target="_blank" title="implemented" href="http://www.theopenhouseproject.com/2008/01/04/ota-update/">implemented</a> as part of GAO:</p>
<p>Other developments during 110th Congress, 1st session:</p>
<ol>
<li>C-SPAN changed its copyright policy to allow reproduction on the Web</li>
<li>Seven Members of Congress posted daily schedules to their official Web sites</li>
<li>Two Members of Congress posted their personal financial disclosures to their official Web sites</li>
<li>The number of Members blogging and posting their earmarks increased dramatically</li>
<li>Launch of OMB spending and earmark online database</li>
<li>Launch of FARA online database</li>
<li>Redesign of SOPR lobbyist disclosure online database</li>
</ol>
<p>Pending for 110th Congress, 2nd session:Ã‚Â  (see also <a target="_blank" title="here" href="http://www.theopenhouseproject.com/resources/pendingbills">here</a> )</p>
<ol>
<li>S.2321 E-Government Reauthorization Act of 2007 (Hearings held in the Senate)</li>
<li>Review of Franking Regulations for Member Web sites</li>
<li>H.R.1362 Accountability in Contracting Act of 2007 (Passed the House)</li>
<li>S. Res. 401 A resolution to provide Internet access to certain Congressional Research Service publications</li>
<li>Lieberman&#8217;s statement that Senate votes should be in XML, in support of THOMAS upgrades</li>
</ol>
<p><span class="WQ9l9c" id="q_11746a8b307b08cb_5" />Two more pieces of transparency reform legislation underway for 2008:<br />
First, the Presidential Library Donation Reform Act of 2007, (HR<br />
1254<<a rel="nofollow" target="_blank" href="http://www.govtrack.us/congress/bill.xpd?bill=h110-1254">http://www.govtrack.us/congress/bill.xpd?bill=h110-1254</a>>)<br />
saying <<a rel="nofollow" target="_blank" href="http://www.govtrack.us/congress/billtext.xpd?bill=h110-1254">http://www.govtrack.us/congress/billtext.xpd?bill=h110-1254</a>>&#8230; *&#8221;Any<br />
Presidential library fundraising organization shall submit on a quarterly<br />
basis, in accordance with paragraph (2), information with respect to&#8230;&#8221;<br />
*Second, here&#8217;s the Presidential Records Acts Amendments of 2007, (HR<br />
1255<<a rel="nofollow" target="_blank" href="http://www.govtrack.us/congress/bill.xpd?bill=h110-1255">http://www.govtrack.us/congress/bill.xpd?bill=h110-1255</a>>)<br />
saying <<a rel="nofollow" target="_blank" href="http://www.govtrack.us/congress/billtext.xpd?bill=h110-1255">http://www.govtrack.us/congress/billtext.xpd?bill=h110-1255</a>>&#8230;<br />
&#8220;`(a)(1) When the Archivist determines under this chapter to make available<br />
to the public any Presidential record that has not previously been made<br />
available to the public, the Archivist shall&#8230;&#8221; and &#8220;Executive Order No.<br />
13233, dated November 1, 2001 (66 Fed. Reg. 56025), shall have no force or<br />
effect.&#8221; among other things. Ã‚Â (link to executive<br />
order<<a rel="nofollow" target="_blank" href="http://www.whitehouse.gov/news/releases/2001/11/20011101-12.html">http://www.whitehouse.gov/news/releases/2001/11/20011101-12.html</a>><br />
)<br />
Again, the OHP page<<a rel="nofollow" target="_blank" href="http://www.theopenhouseproject.com/resources/pendingbills">http://www.theopenhouseproject.com/resources/pendingbills</a>>also<br />
has legislation on Congress relevant to the report as well.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/23/recent-passed-and-pending-transparency-reform-legislation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Library of Congress on Flickr</title>
		<link>http://www.theopenhouseproject.com/2008/01/16/library-of-congress-on-flickr/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/16/library-of-congress-on-flickr/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 20:31:57 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[flickr]]></category>
		<category><![CDATA[library of congress]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/16/library-of-congress-on-flickr/</guid>
		<description><![CDATA[You should proceed as soon as possible to check out the Library of Congress&#8217;s page on flickr, as announced this morning.
It&#8217;s an awesome collection of about 3,000 images, of the quality you&#8217;d expect from the world&#8217;s largest library.Ã‚Â  It&#8217;s wonderful to see them available the same way we expect to share images with each other, [...]]]></description>
			<content:encoded><![CDATA[<p>You should proceed as soon as possible to check out the <a href="http://www.flickr.com/photos/library_of_congress/">Library of Congress&#8217;s page on flickr</a>, as announced <a href="http://www.loc.gov/blog/?p=233">this morning</a>.</p>
<p>It&#8217;s an awesome collection of about 3,000 images, of the quality you&#8217;d expect from the world&#8217;s largest library.Ã‚Â  It&#8217;s wonderful to see them available the same way we expect to share images with each other, sort of making history less of something living in a museum, and more of something available, relevant, and even sorted through tags.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/16/library-of-congress-on-flickr/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<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>CRS Tuesday: Lobbying, and Iraq</title>
		<link>http://www.theopenhouseproject.com/2007/09/11/crs-tuesday-lobbying-and-iraq/</link>
		<comments>http://www.theopenhouseproject.com/2007/09/11/crs-tuesday-lobbying-and-iraq/#comments</comments>
		<pubDate>Tue, 11 Sep 2007 19:06:14 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[CRS reports]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[lobbying]]></category>
		<category><![CDATA[lobbying disclosure]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/09/11/crs-tuesday-lobbying-and-iraq/</guid>
		<description><![CDATA[Two particularly relevant new CRS reports this week:
First, a report summarizing lobbying reform measures:
Significant changes were made by Congress to the current lobbying laws, and to internal House and Senate rules on ethics and procedures, by the passage of S. 1, 110th Congress, and the adoption of H.Res. 6, 110th Congress. In the face of [...]]]></description>
			<content:encoded><![CDATA[<p>Two particularly relevant new CRS reports this week:</p>
<p>First, <a href="http://opencrs.com/document/rl34166">a report</a> summarizing lobbying reform measures:</p>
<blockquote><p>Significant changes were made by Congress to the current lobbying laws, and to internal House and Senate rules on ethics and procedures, by the passage of S. 1, 110th Congress, and the adoption of H.Res. 6, 110th Congress. In the face of mounting public and congressional concern over allegations and convictions of certain lobbyists and public officials in a burgeoning &#8220;lobbying and gift&#8221; scandal, and with a recognition of legitimate concerns over undue influence and access of certain special interests to public officials, Congress has adopted stricter rules, regulations, and laws attempting to address these issues. This report examines the changes made to law and congressional rule in S. 1, 110th Congress, and changes adopted to internal House rules earlier in the Congress in H.Res. 6.</p></blockquote>
<p>The other report is a brand new analysis of Iraq: <em><a href="http://opencrs.cdt.org/document/RL31339/">Iraq: Post-Saddam Governance and Security</a>.</em>:</p>
<blockquote><p>Operation Iraqi Freedom overthrew Saddam Hussein&#8217;s regime, but much of Iraq remains violent because of Sunni Arab resentment and a related insurgency, compounded by Sunni-Shiite sectarian violence that, in the judgment of many, constitutes a &#8220;civil war.&#8221; Mounting U.S. casualties and financial costs &#8212; without dramatic improvements in levels of violence or clear movement toward national political reconciliation among Iraq&#8217;s major communities &#8212; have intensified a debate within the United States over whether to reduce U.S. involvement without completely accomplishing initial U.S. goals. President Bush announced a new strategy on January 10, 2007 (&#8220;New Way Forward&#8221;) consisting of deployment of an additional 28,500 U.S. forces (&#8220;troop surge&#8221;) to help stabilize Baghdad and restive Anbar Province. The strategy is intended to provide security conditions conducive to Iraqi government action on a series of key reconciliation initiatives that are viewed as &#8220;benchmarks&#8221; of political progress.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/09/11/crs-tuesday-lobbying-and-iraq/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Statements of Administrative Policy</title>
		<link>http://www.theopenhouseproject.com/2007/09/09/statements-of-administrative-policy/</link>
		<comments>http://www.theopenhouseproject.com/2007/09/09/statements-of-administrative-policy/#comments</comments>
		<pubDate>Mon, 10 Sep 2007 03:22:13 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[LIV]]></category>
		<category><![CDATA[OMB]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[appropriations]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[library of congress]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/09/09/statements-of-administrative-policy/</guid>
		<description><![CDATA[The Office of Management and Budget offers tons of information publicly, and does a great job of archiving and indexing pdfs relating to their reports, budgets, and testimony.
I find the Statements of Administrative Policy to be particularly helpful, since the administration&#8217;s official policy positions on various legislative initiatives are all available as they&#8217;re available.
Now if [...]]]></description>
			<content:encoded><![CDATA[<p>The Office of Management and Budget offers tons of information publicly, and does a great job of archiving and indexing pdfs relating to their <a href="http://www.whitehouse.gov/omb/legislative/index.html">reports</a>, <a href="http://www.whitehouse.gov/omb/budget/fy2008/">budgets</a>, and <a href="http://www.whitehouse.gov/omb/legislative/testimony/index.html">testimony</a>.</p>
<p>I find the <a href="http://www.whitehouse.gov/omb/legislative/sap/110-1/index-date.html">Statements of Administrative Policy</a> to be particularly helpful, since the administration&#8217;s official policy positions on various legislative initiatives are all available as they&#8217;re available.</p>
<p>Now if bills as they&#8217;re reported out of committee and considered on the floor were to get assigned a URI and everyone used a standardized version of LOC&#8217;s Legislative Indexing Vocabulary, then these disparate data sets could all be more easily linked for centralized tracking.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/09/09/statements-of-administrative-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

