Earlier this year, Sunlight was issued a challenge: Collect and refute the most common reasons not to release data. As many open access advocates, journalists, and government employees themselves will tell you, there are a variety of "no's" given when the question of data disclosure arises. Many are predictable, some are political, some personal, many practical, and all deserving of attention. Pioneers looking to move their government toward exploring and advancing information release have already come up with rebuttals to many of these refusals, but the collective knowledge is hard to share, usually trapped in email groups, discussion boards, blogs, and the memories and experiences of individuals. So, we're going to meet our challenge with an experiment.
Continue readingSouth Bend, Indiana Signs Open Data Policy
Texas Opens Up Public Officials’ Communications
The 83rd Texas Legislature took steps to open up government at the state and local levels with two new laws that could set a precedent in making legislative communication open by default.
Continue readingA Modern Approach to Open Data
Last year, a group of us who work daily with open government data -- Josh Tauberer of GovTrack.us, Derek Willis at The New York Times, and myself -- decided to stop each building the same basic tools over and over, and start building a foundation we could share.
We set up a small home at github.com/unitedstates, and kicked it off with a couple of projects to gather data on the people and work of Congress. Using a mix of automation and curation, they gather basic information from all over the government -- THOMAS.gov, the House and Senate, the Congressional Bioguide, GPO's FDSys, and others -- that everyone needs to report, analyze, or build nearly anything to do with Congress.
Once we centralized this work and started maintaining it publicly, we began getting contributions nearly immediately. People educated us on identifiers, fixed typos, and gathered new data. Chris Wilson built an impressive interactive visualization of the Senate's budget amendments by extending our collector to find and link the text of amendments.
This is an unusual, and occasionally chaotic, model for an open data project. github.com/unitedstates is a neutral space; GitHub's permissions system allows many of us to share the keys, so no one person or institution controls it. What this means is that while we all benefit from each other's work, no one is dependent or "downstream" from anyone else. It's a shared commons in the public domain.
There are a few principles that have helped make the unitedstates project something that's worth our time, which we've listed below.
(Just Over) One Year Later: Philly’s Open Data Policy
Just over a year ago, Mayor Michael Nutter of Philadelphia, Pennsylvania signed an executive order creating an open data policy... View Article
Continue readingAnnouncing the Open Data Policy Guidelines, Version 2.0
As more communities recognize the power and possibilities of sharing public data online, there is an increasing need to articulate what it means to open data -- and how to create policies that can not only support these efforts, but do so in a sustainable and ambitious way.
To this end, we are releasing the second version of Sunlight’s Open Data Policy Guidelines. Originally authored last summer and informed by the great work of our peers and allies, the Guidelines are a living document created to help define the landscape of what open data policies can and should do. For this latest version, we’ve reordered and slightly rephrased the Guidelines’ 32 provisions for clarity. We’ve also grouped them into three categories as a way of demonstrating that open data policies can define What Data Should Be Public, How to Make Data Public and How to Implement Policy.
Can Electronic Records Save Money, Increase Efficiency, and Benefit Everyone?
The advantages of using electronic records and providing more searchable, accessible records are sometimes overshadowed by one concern: money.
Continue readingElectronic Records Are Already Here to Stay
The benefits of electronic records go far beyond the improved searching and sharing of information with the public. They also help prepare governments for present and future records management.
Continue readingCity Finances Were A Story Before Detroit’s Bankruptcy
The news is indeed big and deserving of attention: As of last week, Detroit is now the largest U.S. municipality to file for bankruptcy.
The news, however, is perhaps not as shocking as some would portray it. While national publications have only recently jumped on the story, Detroit's local media have long been keeping the public informed about the city's finances and the series of events that eventually led to filing for bankruptcy.
Accessing public records -- including details about the city's financial data, contracts, and many other datasets -- has enabled the media to shine a light over the years on the city's fiscal challenges. Outlets like Detroit Free Press, The Detroit News, Fox 2 News, and many others were on this story long before the news of bankruptcy woke up the media giants: capturing critical moments like when the city realized it was close to running out of cash in 2011 and press conferences by Detroit leaders in 2012 that described how allowing state intervention could help prevent bankruptcy. Continued coverage from the local media kept residents informed about what was happening, what events and politics had led Detroit to this situation, and what could come next. The potential of bankruptcy was no surprise to those who followed the process of state intervention in the city's finances.
With a population of more than 700,000 people, Detroit is now the largest U.S. city to file for bankruptcy, but it is by no means the first large city to do so. Cities like Stockton (population: 296,000), Vallejo (population: 117,000), and San Bernardino (population: 213,000) have been there, too, and the stories out of those cities can help show what to watch for in Detroit. (And, if San Bernardino is any example, other cities can show some of the particular challenges to financial information disclosure that may appear during bankruptcy proceedings.)
No two places provide an exact apples to apples comparison, however. Each city has its own history, process, and paper trail -- and each needs an experienced scout to know how to traverse the political landscape and to help the public do the same. That's why it's so important to have access to public records (the key to understanding our political past and present) and to have watchdogs who use them to review the political process and show those in power that they will be held accountable for their actions.
Continue readingThe Sunlight Foundation’s Comments on the FAA’s Proposed Open Data Policy
On May 1, The Federal Aviation Administration published a [Proposed Open Data Policy](https://www.federalregister.gov/articles/2013/05/01/2013-10295/notice-for-data-and-information-distribution-policy) in the Federal Register, and requested public comment by [July 28](https://www.federalregister.gov/articles/2013/06/03/2013-13086/notice-of-proposal-policy-for-distribution-of-faa-data-and-information-extension-of-comment-period). The FAA proposed 10 broad guidelines for its open data policies, among them points about non-exclusivity of access to data, the appropriateness of employing cost recovery from external entities, and the transparency with which they execute on the policy itself.
The Sunlight Foundation had something to say about each of these issues, and so we submitted the public comment below, which we hand-delivered today to the FAA's Docket Office inside the Department of Transportation. Our comment should show up on [Docket Wrench](http://docketwrench.sunlightfoundation.com/docket/FAA-2013-0392) and [Regulations.gov](http://www.regulations.gov/#!docketBrowser;rpp=100;so=DESC;sb=docId;po=0;dct=PS;D=FAA-2013-0392) before long. In the mean time, read what we submitted:
59063
