Thomas

 

House Convenes Second Public Meeting on Legislative Bulk Data

On January 30th, the House of Representatives held a public meeting on its efforts to release more legislative information to the public in ways that facilitate its reuse. This was the second meeting hosted by the Bulk Data Task Force where members of the public were included; it began privately meeting in September 2012. (Sunlight and others made a presentation at a meeting, in October, on providing bulk access to legislative data.) This public meeting, organized by the Clerk's office, is a welcome manifestation of the consensus of political leaders of both parties in the House that now is the time to push Congress' legislative information sharing technology into the 21st century. In other words, it's time to open up Congress.

The meeting featured three presentations on ongoing initiatives, allowed for robust Q&A, and highlighted improvements expected to be rolled out of the next few months. In addition, the House recorded the presentations and has made the video available to the public. The ongoing initiatives are the release of bill text bulk data by GPO, the addition of committee information for docs.house.gov, and the release on floor summary bulk data. It's expected that these public meetings will continue at least as frequently as once per quarter, or more often when prompted by new releases of information.

As part of the introductory remarks, the House's Deputy Clerk explained that a report had been generated by the Task Force at the end of the 112th Congress on bulk access to legislative data and was submitted to the House Legislative Branch Appropriations Subcommittee. It's likely that the report's recommendations will become public as part of the committee's hearings on the FY 2014 Appropriations Bill, at which time the public should have an opportunity to comment.

Read more

Access to Legislation Gets Better, Promise of More to Come

Earlier today, Speaker Boehner and Majority Leader Cantor and the Government Printing Office announced an improvement in how legislation is made publicly available. Starting in the 113th Congress, GPO will make all bills available for bulk download in XML format. While this doesn't change much from a technological perspective, it does mark a significant change from a policy perspective.

Read more

Learning how to navigate Congress.gov

The new and much improved location for Congressional information, beta.congress.gov, has plenty of resources to offer users. Now the Library of Congress (LOC) is offering webinars and in-person training to help users navigate the expanding website. We applaud LOC for providing a variety of training opportunities for those seeking a better understanding of the information available.

Read more

On Legislative Collaboration and Version Control

We often are confronted with the idea of legislation being written and tracked online through new tools, whether it's Clay Shirky's recent TED talk, or a long, long list of experiments and pilot projects (including Sunlight's PublicMarkup.org and Rep. Issa's MADISON) designed to give citizens a new view and voice in the production of legislation.

Proponents of applying version control systems to law have a powerful vision: a bill or law, with its history laid bare and its sections precisely broken out, and real names attached prominently to each one. Why shouldn't we able to have that? And since version control systems are helpful to the point of absolute necessity in any collaborative software effort, why wouldn't Congress employ such an approach?

When people first happen upon this idea, their reaction tends to fall into two camps, which I'll refer to as triumphalist and dismissive.

The Triumphalist Reaction

First, on the triumphalist reaction -- this viewpoint suggests that lawyers just need to act more like coders, and that inserting some common-sense management tools that are commonplace in the technology world will transform how our politics works.

Unfortunately, there are a few points that this vision of transformation overlooks.

Most overly positive prognoses of legislative version control overlook some important details about Congress. The legislative process is itself a version control system, even if it's one that doesn't do as much as we'd like it to. Principals submit duly attributed bills and amendments to a system that controls how they are considered, all attempting to make minor alterations to a canonical code. I'd suggest that most US Code snippets have far more documentation and history that can be attached to them than most contributions to github -- a history of legislation, amendments, hearings, floor speeches, testimony, votes, conference committees, etc, all go into even tiny changes of how the law functions.

Now, anyone saying that Congress should adopt better version control systems thinks that this complex disclosure system is insufficient.  Sunlight would obviously agree, and engages more on that front than probably any other NGO.

Congress as it exists now provides a reasonably reliable public electronic view of the official legislative steps. (With a few notable exceptions like amendments being introduced in the Senate.) What we're all after, of course, exists largely below this official, public level.  We want to see lobbyist influence, and any inappropriate tampering, and we want to create a system that elevates substance, rewards merit, and generally improves how representation works. To get to a level below what's already official, however, you face a choice: you either force new specific things to be public through new requirements (Rules could require drafts of amendments become official documents, or a committee chair could hold a long hearing and sit at a laptop and make changes), or you attempt to encourage the use of collaboration systems, like many pilot projects have in the past.  For our part, Sunlight is encouraging both approaches, and also actively trying to build meaningful views of legislation that make both authorship and influence more visible -- obviously important goals.

If the triumphalist reaction overstates the value of simple technical attribution and versioning management systems, the dismissive reaction ignores it altogether.

The Dismissive Reaction

Suggesting that public tools, or even digital tools, can improve representation is often met with condescension. DC culture places naivete as a greater sin than corruption, and suggesting that bills get written online often gets put in the same mental bucket as "direct democracy" and "referenda on everything."

The dismissive reaction is far worse than the triumphalist one. To dismiss new tools for legislative cooperation is to forget that every good thing about Congress that we enjoy comes from constant struggle and confrontation. Having a legislature in the first place comes from centuries of Kings' power being degraded into an empowered class of nobles, and we shouldn't take that for granted. When we fight over whether committee votes are public, whether bills are online, whether campaign finances are disclosed, and whether the supercommittee was an undemocratic failure, that's not just reformer idealism, but the front line of defining how our representative institutions function. This fight didn't start in the last decade, as Shirky's talk could imply, but has raged for centuries. The last decade has just reinvigorated it, and given us new tools, inspiration, and new expectations.

Even if politics rule democratic governments, political power still has to flow through the shape of our institutions and democratic norms. The shape of the halls of power affect how its wielded, and no forces should have more clout in a democracy than public attention and the rule of law.

So in new tools for managing and analyzing legislation we have the potential to bring public scrutiny and creativity to the legislative process -- new accountability and new generative capacity both. Of course our politics doesn't shrink away in horror from a few blog posts.

Except when it does. If corporate interests understand enough about political power to spend hundreds of millions of dollars rearranging a few words, the public should care enough to move legislative processes into the open, where they're tilted a little more in our favor.

Public, online tools make public consensus a little more politically valuable, and make it harder to legislate in bad faith.  Our digital lives are already strengthening democratic and cultural norms about openness, and one way or another, those norms and efficiencies are going to get applied to the legislative process. We should make sure that they (as I wrote above) elevate substance, reward merit, and improve representation.

We are going to increasingly see bills drafted and reviewed through public, online interactions, where anyone can point out a deficiency, suggest an edit, or spot check a politician's claims. Whether and how public drafting gets accepted into the drafting systems inside Congress (where expert drafters use private tools to draft new laws), clout and expertise can grow outside that system, and affect it regardless of its ability to adapt.

Sunlight's Path

The Sunlight Foundation's approach can probably be described as qualified triumphalism. We're deeply engaged in Congress releasing more information about bills, the legislative process, and the influence that surrounds it, since these are the necessary parts of a version control system. We're shaping the kinds of version control analysis tools that Congress creates, and insofar as this is all attainable by getting laws to be natively written in a public system, then we're all for it. Since that's a long way off, we're also applying those systems to Congress from the outside, supporting and building tools like Scout, GovTrack, OpenCongress and a number of related sites and services to make legislation as visible and meaningful to the layperson as possible. We're hoping to supplant commercial publishing with public interest publishing of legislation and influence data, to build a more even playing field for government information, and also to change how it works.

Version control, as an idea applied to legislating, means seeing what changes, and who changes it. It means accountability forced very precisely into the processes of representation, and it means gaining a new ability for substantive contributions and oversight from a broadly empowered public. Those goals, ultimately, should be the same goals of the legislature itself -- strong policy, accountable representation, and an empowered public.

Congress launches THOMAS successor Congress.gov

Seventeen years after the creation of THOMAS, Congress today launched a sleeker, more intuitive and user-friendly legislative information website, beta.congress.gov.

What's noticeable about this evolving beta website, besides the major improvements in how people can search and understand legislative developments, is what's still missing: public comment on the design process and computer-friendly bulk access to the underlying data.

We hope that Congress will now deeply engage with the public on the design and specifications process and make sure that legislative information is available in ways that most encourage analysis and reuse.

It's also worth remembering what the Library of Congress said in 1996 as it considered what should be included in its legislative information system:

To be most useful to Members of Congress, the legislative information system must provide access to a wide range of current and historical information, including existing statutes, support agency analyses, academic studies, court decisions, budget and financial data, regulations and executive branch policies, public and private sector analyses, lobby group position papers, and newspaper reports from local, national, and international sources.

We will have more to say as we dig deeper into the website. The Library of Congress' news release is below.

LOC News Announcement on Beta.Congress.gov

Looking Forward to the THOMAS Beta Website

In the near future, Congress is expected to release a major upgrade to its aging legislative information website THOMAS. The long-overdue update is part of a much larger effort to "enhance the effectiveness of mission-critical systems," a response to significant public and internal pressure to improve congressional efficiency and transparency. The launch of "THOMAS Beta" is the first step towards developing what the Library of Congress describes as a completely "modern legislative information system" that will replace THOMAS and Congress' more sophisticated internal legislative tracking website "LIS" in FY 2014. Both THOMAS and LIS will stay online alongside the beta website for several years.

While THOMAS Beta has been shown to stakeholders inside Congress, as far as I am aware there has been no formal engagement process with the public to identify specifications, discuss wireframes, or generally make sure the site meets the public's needs. It is expected that such conversations will occur after the launch as the site is built out. My understanding is that the majority of the work on THOMAS Beta thus far has been to modernize the underlying information architecture, with many of the new bells and whistles and apps to be rolled out over time.

Two years ago, the Sunlight Foundation gathered ideas from the community for upgrading THOMAS, and in July 2010 we highlighted three additional ideas, but the primary recommendation continues to be requiring all of the underlying information behind THOMAS to be made available to the public "in bulk."  In other words, all of the legislative information behind THOMAS and LIS should be made available in a way that's easy for machines to understand so that developers can more easy and reliably build tools like OpenCongress, GovTrack, the Congress Android App, and Scout that re-use information in clever new ways.

The House leadership has endorsed the idea of bulk access and established a nascent bulk data task force, but not everyone inside Congress is fully on board with the effort. From an external perspective, we have requested that public stakeholders be included on the bulk data task force, which is being coordinated by the House Clerk's office. Along similar lines, for several years we and others have asked the Library of Congress to form an advisory group on THOMAS (as it is responsible for overseeing THOMAS), and we hope the impending launch of THOMAS Beta will make this a reality.

It's important to understand the context in which the THOMAS Beta rolls out. In the last year, the House of Representatives released an innovative legislative information portal, docs.house.gov, which provides bulk access to House data in a way that is more timely than THOMAS, and will soon provide materials from House committees in addition to documents concerning floor proceedings. The House also held three conferences on legislative transparency and created the bulk data task force. In addition, more than 85 organizations will release a declaration on parliamentary openness in Rome this Saturday at the World e-Parliament Conference that endorses providing information in open and structured formats. And the free, open-source parliamentary information system-in-a-box Bungeni is continuing to gain steam around the world.

We are eagerly looking forward to the launch of THOMAS Beta, and will pay particularly close attention to whether the Library of Congress, which has general responsibility for the project, has built a system that uses modern techniques -- such as bulk access and APIs -- to make information available to the public.

Stay in the loop! Legislative Hill briefing on Scout TODAY

Are you a Hill staffer working on health care? The Farm Bill? DISCLOSE?

Or do you track legislation for your member?

If so, Sunlight is doing a briefing on our latest legislative alert tool, Scout, for Capitol Hill staff today, Friday July 13th at 2pm in Rayburn room 2203. (You can RSVP online here)

We built Scout to help everyone -- including busy Capitol Hill staffers -- better monitor the issues and policies important to them. The tool combines a variety of sources including the Congressional Record, THOMAS, GovTrack, the Federal Register and Sunlight’s Open States project to create legislative  searches about issues you care about. From federal legislation, speeches, regulations, to bills across all fifty states, Scout lets you search and create alerts all in one place.

The briefing will also include an overview on Sunlight’s other legislative and governmental tools such as Capitol Words and our Congress mobile app.

We hope you can join us today Friday the 13th in Rayburn 2203 (just avoid stepping on cracks or walking under ladders).

Rabbit foot optional.

Rep. Honda Speaks on Bulk Access on the House Floor

This morning the House is debating passage of the Legislative Branch Appropriations Bill. Rep. Honda, the ranking member of the Legislative Branch Appropriations Subcommittee and a longtime champion for better access to legislative information, spoke on the importance of improved access as part of his broader comments. Here's that excerpt:

I am privileged to represent Silicon Valley, the center of technological innovation in this country. Since I joined this subcommittee, I have tried to push the House and other agencies to explore technological solutions to issues such as transparency, evacuation management, and data storage.

As you probably know, Federal agencies, including our own in the legislative branch, can be slow to change and adopt new technologies. This is mentioned in the report, which includes language on the issue of bulk data downloads of legislative information, something I requested and secured language about in this bill in fiscal year 2009.

This effort is now also being championed by leadership on both sides of the aisle, as it is a way to increase transparency by allowing the public to easily download and analyze government data.

There are some concerns about cost and the ability to authenticate the data that the language in the report tries to address.

I think, however, that these are relatively simple matters to overcome, as data is already being compiled in a format that can easily be distributed and technology support staff has indicated that only a simple procedure is needed to make the bulk data available.

Furthermore, the GPO already employs an authentication standard for its own accessible bulk data through its FDSys website that we could also utilize.

The House Majority recently announced that it will immediately create a task force, as described in this bill, to expedite a report and implementation of public access to bulk legislative data. While I believe the time to implement this is now, I expect to be included in these efforts as Ranking Member of the Subcommittee and longtime advocate.

Major Transparency Milestone in Bulk Access Statement

It may feel like an ordinary Wednesday, but today is a milestone for legislative transparency. The House's leadership has issued a statement adopting the goal of "provid[ing] bulk access to legislative information to the American people without further delay." They have stated that bulk access "ranks among our top priorities in the 112th Congress" and directed a task force "to begin its important work immediately."

The statement was made by many of the key players on this issue in the House: Speaker Boehner, Majority Leader Cantor, Legislative Branch Appropriations Subcommittee Chairman Crenshaw, and Oversight and Government Reform Committee Chairman Issa. It was prompted in part by a measure in the legislative branch appropriations report that, as initially formulated, may have frozen efforts to move in this direction, followed by a partial fix to the report and ultimately a proposed amendment to the bill. (The amendment was apparently rejected by the House Rules Committee.) Of course, all of the letters to Congress and news coverage helped reinforce this as a higher priority.

The debate over whether there should be bulk access to legislative data is over. Because bulk access is a top priority of the 112th Congress, we expect to see tangible progress in the upcoming months. The remaining questions largely concern how bulk access should be implemented to meet the needs of the public while respecting the legitimate concerns of Congress and its support agencies.

While we are disappointed that the task force will not include members of the public, we hope that the public will be consulted. After all, the American people are the intended end-users. Sunlight and our friends in the transparency community stand ready to be of assistance as the technical, policy, and scope issues are addressed.

We have reached this turning point for a number of reasons. Rep. Honda has pushed to make bulk access happen over the last half-decade. Rep. Boehner made legislative transparency a priority when he was elected speaker. Reps. Cantor and Hoyer co-hosted the Congressional Facebook Hackathon, which declared bulk access to be an important goal. Rep. Lungren and the Committee on House Administration held hearings and issued directives establishing the important transparency portal docs.house.gov as well as hosted the Legislative Data and Transparency Conference. And there's many staff and members of Congress who have labored for years to bring this to fruition.

While this is clearly progress, there's still much more to do. We will be monitoring this issue closely.