<?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; jurisdiction</title>
	<atom:link href="http://www.theopenhouseproject.com/category/jurisdiction/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>Government Commitment to Open Standards</title>
		<link>http://www.theopenhouseproject.com/2008/02/07/250/</link>
		<comments>http://www.theopenhouseproject.com/2008/02/07/250/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 17:39:28 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[OMB]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[executive]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[open standards]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/02/07/250/</guid>
		<description><![CDATA[I&#8217;m wondering to what degree federal government entities have formally committed to using open standards.  The closest I can find is language from the OMB Circular A-130, which, as far as I can see, doesn&#8217;t explicitly mention proprietary vs open standards.
There are several passages, however, which could be taken to add up to as [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m wondering to what degree federal government entities have formally committed to using open standards.  The closest I can find is language from the OMB Circular A-130, which, as far as I can see, doesn&#8217;t explicitly mention proprietary vs open standards.</p>
<p>There are <a href="http://www.whitehouse.gov/omb/circulars/a130/a130trans4.html#7">several passages</a>, however, which could be taken to add up to as much:</p>
<blockquote><p>
The free flow of information between the government and the public is essential to a democratic society. It is also essential that the government minimize the Federal paperwork burden on the public, minimize the cost of its information activities, and maximize the usefulness of government information.</p>
<p>Because the public disclosure of government information is essential to the operation of a democracy, the management of Federal information resources should protect the public&#8217;s right of access to government information.</p>
<p>Systematic attention to the management of government records is an essential component of sound public resources management which ensures public accountability. Together with records preservation, it protects the government&#8217;s historical record and guards the legal and financial rights of the government and the public.</p>
<p>The open and efficient exchange of scientific and technical government information, subject to applicable national security controls and the proprietary rights of others, fosters excellence in scientific research and effective use of Federal research and development funds.</p>
<p>Federal Government information resources management policies and activities can affect, and be affected by, the information policies and activities of other nations.</p>
<p>The availability of government information in diverse media, including electronic formats, permits agencies and the public greater flexibility in using the information.</p>
<p>The Chief Information Officers Council and the Information Technology Resources Board will help in the development and operation of interagency and interoperable shared information resources to support the performance of government missions.</p>
<p>(d) In determining whether and how to disseminate information to the public, agencies will: (i) Disseminate information in a manner that achieves the best balance between the goals of maximizing the usefulness of the information and minimizing the cost to the government and the public;</p>
<p>(ii) Disseminate information dissemination products on equitable and timely terms;</p>
<p>(iii) Take advantage of all dissemination channels, Federal and nonfederal, including State and local governments, libraries and private sector entities, in discharging agency information dissemination responsibilities;<br />
(iv) Help the public locate government information maintained by or for the agency.</p>
<p>How must agencies avoid improperly restrictive practices?</p>
<p>Agencies will:</p>
<p>(a) Avoid establishing, or permitting others to establish on their behalf, exclusive, restricted, or other distribution arrangements that interfere with the availability of information dissemination products on a timely and equitable basis; </p></blockquote>
<p>There&#8217;s a lot there, but they never seem to fully address the problems that come along with the use of proprietary data formats.  I&#8217;m wondering how helpful it would be to have this addressed more formally, and perhaps in a way that applies to both Congress and the executive (since this is an OMB circular).</p>
<p>Also, notably, this circular directs each agency to appoint a CIO, and outlines accountability mechanisms for them, and also mentions the Council of CIOs.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/02/07/250/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>GAO Document on Electronic Dissemination of Government Publications</title>
		<link>http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/#comments</comments>
		<pubDate>Thu, 31 Jan 2008 21:34:40 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[FDLP]]></category>
		<category><![CDATA[GAO]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/</guid>
		<description><![CDATA[In 2001, the GAO published a document entitled &#8220;Information Management; Electronic Dissemination of Government Publications&#8221; (pdf).
The GAO is responding to a congressional request for information on electronic documents dissemination, and ends up discussing the GPO, LOC, and FDLP in great detail.  Apparently they considered transferring the FDLP from the GPO to the LOC.
Also, the [...]]]></description>
			<content:encoded><![CDATA[<p>In 2001, the GAO published a document entitled &#8220;Information Management; Electronic Dissemination of Government Publications&#8221; (<a href="http://www.gao.gov/new.items/d01428.pdf">pdf</a>).</p>
<p>The GAO is responding to a congressional request for information on electronic documents dissemination, and ends up discussing the GPO, LOC, and FDLP in great detail.  Apparently they considered transferring the FDLP from the GPO to the LOC.</p>
<p>Also, the report lists the essential documents which must continue to be printed, regardless of how digitized we become.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/feed/</wfw:commentRss>
		<slash:comments>0</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>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>S.Pub 102-20</title>
		<link>http://www.theopenhouseproject.com/2007/12/19/spub-102-20/</link>
		<comments>http://www.theopenhouseproject.com/2007/12/19/spub-102-20/#comments</comments>
		<pubDate>Wed, 19 Dec 2007 22:30:36 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[CLA]]></category>
		<category><![CDATA[CONAN]]></category>
		<category><![CDATA[NARA]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[lobbying disclosure]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/12/19/spub-102-20/</guid>
		<description><![CDATA[I&#8217;ve been on a mission, since November 14th, to find a digital copy of S.Pub 102-20, a reference document from 1990 giving a very comprehensive analysis of all public congressional information, from an archival perspective.Ã‚Â  I&#8217;ve finally managed to digitize a copy (after some quality time at the scanner).Ã‚Â  It is a large file.Ã‚Â  (Click [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been on a mission, since <a id="eadb" title="November 14th" href="http://groups.google.com/group/openhouseproject/browse_thread/thread/7b0802cd2767a16e/7add37ad7e0e15a2?lnk=gst&#038;q=ohp+update+s.pub#7add37ad7e0e15a2">November 14th</a>, to find a digital copy of S.Pub 102-20, a reference document from 1990 giving a <span style="font-style: italic">very</span> comprehensive analysis of all public congressional information, from an archival perspective.Ã‚Â  I&#8217;ve finally managed to digitize a copy (after some quality time at the scanner).Ã‚Â  It is a large file.Ã‚Â  (Click <a id="kzg1" title="here" href="http://openhouseproject.s3.amazonaws.com/documentation-of-congress_1992.pdf">here</a> to download a PDF.)</p>
<p>The preface describes it as a &#8220;study of the archival sources that document the operations of Congress.&#8221;Ã‚Â  The &#8220;archival sources&#8221; described in this document comprise the entire body of public congressional information, the substance of both administrative minutiae, and legislative substance.Ã‚Â  Just as we are interested in the capacity of the public to be conscious of its legislature, we should be interested in the legislature&#8217;s capacity to take stock of itself, to engage in constructive introspection.</p>
<p>I came across this document being repeatedly cited while reading the <a id="m8k8" title="yearly reports" href="http://www.archives.gov/legislative/cla/advisory-committee/">yearly reports</a> of the Advisory Committee on the Preservation of the Records of Congress, and still find rich irony in the fact that the document itself wasn&#8217;t available in a digital form.Ã‚Â  That&#8217;s not to say anything against the Advisory Committee, which seems to be an outgrowth or a result of the task force that wrote S.Pub 102-20, and also inspired H.R. 5241 from the 101st Congress, a bill reorganizing the National Archives, among other things.Ã‚Â  The Advisory Committee seems to be among the very best of examples of an organization created to meet an emergent need, cutting across jurisdictions and what one of its members recently described to me as &#8220;negotiated terrain&#8221; (a description I very much liked).</p>
<p>The complex problem of coordinating congressional information is difficult, but not for the usual reasons.Ã‚Â  As far as preservation goes, the administrative coordination is already in place, and it seems that the research (and even <a id="x598" title="enforcement" href="http://www.sunlightfoundation.com/the_gaos_unheeded_mandate">enforcement</a> ) about disclosure mechanisms has been in place for quite some time.Ã‚Â  What has been lagging is not administrative will, but the digital culture and popular expectations that make IT investment a real priority.</p>
<p>This is clearly changing, as new staffers expect to represent their members of Congress online without encountering <a id="jakw" title="arcane restrictions" href="http://www.theopenhouseproject.com/the-open-house-project-report/7-member-web-use-restrictions/">arcane restrictions</a>, as citizens expect to encounter government information and services through the same search engines they use for research and shopping, and a new brand of journalism is springing up that depends not on cultivating trusted sources through personal relationships, but on careful consideration of primary sources&#8211;exactly those &#8220;archival sources&#8221; this document so comprehensively describes.</p>
<p>While some disclosure will be resisted for as long as the benefits of secrecy outweigh the outcry over obstruction, and privileged access will always be at odds with the broader public interest, it is good to see that a detailed anatomy of congressional information has already been constructed in great detail.Ã‚Â  The question that remains is how well will Congress adapt to new expectations of information access &#8212; a question that necessarily comes along with a digitally empowered citizenry.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/12/19/spub-102-20/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>OTA comment, US CTO</title>
		<link>http://www.theopenhouseproject.com/2007/12/09/ota-comment-us-cto/</link>
		<comments>http://www.theopenhouseproject.com/2007/12/09/ota-comment-us-cto/#comments</comments>
		<pubDate>Sun, 09 Dec 2007 19:55:06 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[CTO]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[executive]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[lessig]]></category>
		<category><![CDATA[ota]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/12/09/ota-comment-us-cto/</guid>
		<description><![CDATA[From a response I just wrote to a comment on a Lessig blog post about dreaming up a US CTO position:
The OTA was recently reinstated, although in a different form, when Congress passed (and President Bush signed) the most recent legislative branch appropriations bill.  I work for the Sunlight Foundation, and we helped push [...]]]></description>
			<content:encoded><![CDATA[<p>From a response I just wrote to a comment on a <a href="http://lessig.org/blog/2007/12/a_us_cto.html">Lessig blog post</a> about dreaming up a US CTO position:</p>
<blockquote><p>The OTA was recently reinstated, although in a different form, when Congress passed (and President Bush signed) the most recent legislative branch appropriations bill.  I work for the Sunlight Foundation, and we helped push for this measure to be adopted.  (see http://www.theopenhouseproject.com/2007/06/04/ota-endorsement/ or http://www.theopenhouseproject.com/2007/06/07/ota-renewed-gets-25-million/ )</p>
<p>Instead of reinvoking funding for the still-authorized OTA department, the new approps bill adds funding to the GAO&#8217;s budget, letting them venture explicitly into the realm of technological assessment.  This is probably a good thing, given GAO&#8217;s excellent reputation, and that their work is public, as are their evaluative criteria.</p>
<p>Having a congressional support agency with an explicit mandate to provide research on technological issues will go a long way toward giving congressional decisions on technology the background they need to be sound, and re-funding an OTA, whether as a stand-alone agency or as part of the GAO is the right way to go about it.</p>
<p>A separate issue entirely, however, is whether Congress has adequately organized their administrative appendages to address their own technological coordination issues.  Having dedicated researchers available will help lead to better policy, but without clear jurisdiction, proper implementation and foresight get passed over, as agencies and departments struggle to prioritize and act within their budgets.  Complex incentives surround the question of whether or not to take on a problem that is outside your department&#8217;s statutorily authorized responsibilities.  A central non-political body coordinating these responsibilities across Congress would streamline the process of implementing and planning new technological transitions, a very complicated task for such a complex institution.</p></blockquote>
<p>What I didn&#8217;t get into, however, is the main thrust of Lessig&#8217;s post, that is, should the US have a CTO position?  </p>
<p>I don&#8217;t know the answer to that question, but I&#8217;m inclined to suggest that centralizing and institutionalizing technological expertise leads to better policy and decisions.  The issue I have with this suggestion, however, is one of jurisdiction.  How does the complex of fought-over jurisdictions, executive orders, tradition, and expectations come to cough up a new cabinet level position?  The history American choices addressing emergent needs by creating new administrative appendages is probably full of illustrative examples, which might suggest the best way to centralize technological expertise in American executive administration.</p>
<p>Is this best filled by an informal advisory role, a cabinet level position, an Office of Management and Budget office, a separate technological affairs office, a temporary task force?  Consciously considering the choices beforehand makes it less likely that we choose whatever is most expedient when the issue is raised in earnest.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/12/09/ota-comment-us-cto/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

