If the American public wants to see meaningful progress on transparency, accountability or ethics in U.S. government, it should call on Congress to act, not the Trump White House. With little fanfare or notice, the United States of America has … Continue reading
Livestreaming is not new to American politics in 2019. presidential candidates started using uStream in 2008. But it is much easier than ever before. Recent advances in smartphones and wirelesss Internet access have radically improved the capacity of politicians and … Continue reading
On December 21, 2018, the United States House of Representatives voted to enact H.R. 4174, the Foundations for Evidence-Based Policymaking Act of 2017, in a historic win for open government in the United States of America.
The Open, Public, Electronic, and Necessary Government Data Act (AKA the OPEN Government Data Act) is about to become law as a result. This codifies two canonical principles for democracy in the 21st century:
- public information should be open by default to the public in a machine-readable format, where such publication doesn’t harm privacy or security
- federal agencies should use evidence when they make public policy
For the full backstory on what’s in the bill and how it came to pass, read yesterday’s feature.
It’s worth noting that last minute objection did result in two amendments that the Senate had to act upon. Thankfully, on Saturday, December 22nd, the Senate acted, passing the resolution required to send the bill onwards to the president’s desk.
Here’s what changed: First, the text of Title I was amended so that it only applied to CFO Act agencies, not the Federal Reserve or smaller agencies. Title II (the Open Government Act) still applies to all federal agencies.
Second, there was a carve out in Title I “for data that does not concern monetary policy,” which relates to the Federal Reserve, among others.
While the shift weakened the first title of the bill a bit, this was still a historic moment: Congress has passed a law to make open data part of of the US Code.
While the United States is not the first or even the second democracy to pass an open data law – France and Germany have that distinction – this is a welcome advance, codifying the open government data policies, practices, roles and websites (looking at you, Data.gov) that the federal government had adopted over the past decade.
Open government activists, advocates and champions continue to celebrate, online and off.
Victory! Last night the @DataCoalition got the #OPENGovData Act through the Senate, as part of H.R. 4174. Expected to sail through the House TODAY. Sets a presumption, in law, that govt info ought to be published as #opendata, using data standards. https://t.co/jTdM1rIVTW
— Hudson Hollister (@hudsonhollister) December 20, 2018
#Opendata will soon be the way our government publishes information by default!! What a great day for #opendata #opengov #transparency! This would not have been possible w/o @SpeakerRyan @PattyMurray @SenBrianSchatz @SenSasse @RepDerekKilmer. Thank you! #OPENGovDataAct (HR 4174)
— Data Coalition (@DataCoalition) December 21, 2018
Merry Christmas to me! The U.S. Congress has passed an open data law. pic.twitter.com/tDwo8j8UCB
— Rebecca Williams (@internetrebecca) December 21, 2018
Excited to see the Open Government Data Act pass the House today! H.R. 4174 will enable libraries to provide businesses, researchers and students with valuable data that fuels innovation and economic growth. #OPENGovData #opendata
— Gavin Baker (@OpenGavin) December 21, 2018
“The bipartisan passage of the Foundations for Evidence-Based Policymaking Act is a significant step toward a more efficient, more effective government that uses evidence and data to improve results for the American people,” said Michele Jolin, CEO and co-founder of Results for America, in a statement. “We commend Speaker Ryan, Senator Murray and their bipartisan colleagues in both chambers for advancing legislation that will help build evidence about the federally-funded practices, policies and programs that deliver the best outcomes. By ensuring that each federal agency has an evaluation officer, an evaluation policy and evidence-building plans, we can maximize the impact of public investments.”
“The OPEN Government Data Act will ensure that the federal government releases valuable data sets, follows best practices in data management, and commits to making data available to the public in a non-proprietary and electronic format,” said Daniel Castro, in a statement. “Today’s vote marks a major bipartisan victory for open data. This legislation will generate substantial returns for the public and private sectors alike in the years to come.”
“The passage of the OPEN Government Data Act is a win for the open data community”, said Sarah Joy Hays, Acting Executive Director of the Data Coalition, in a statement. “The Data Coalition has proudly supported this legislation for over three years, along with dozens of other organizations. The bill sets a presumption that all government information should be open data by default: machine-readable and freely-reusable. Ultimately, it will improve the way our government runs and serves its citizens. This would not have been possible without the support of Speaker Paul Ryan (WI-1-R), Senators Patty Murray (WA-D), Brian Schatz (HI-D), Ben Sasse (NE-R), and Rep. Derek Kilmer (WA-6-D). Our Coalition urges the President to promptly sign this open data bill into law.”
Congratulations to everyone who has pushed for this outcome for years.
[Image Credit: Sunlight Foundation]
This post has been updated, and corrected: France was ahead of Germany in enacting an open data law.
The arc of open government in United States is long, but perhaps it will bend towards transparency and accountability as 2018 comes to a close, in an unlikely moment in our history. After years of dedicated effort by advocates and bipartisan leadership in both houses of Congress, the Open, Public, Electronic, and Necessary Government Data Act (AKA the OPEN Government Data Act) is about to become law after the United States Senate passed the bill as part of H.R. 4174 on December 19.
Senator Brian Schatz (D-HI) shared the news in a tweet last night:
We just passed a bill that requires all data the govt collects (that isn’t secret or private) to be machine readable and interoperable. It’s data that taxpayers paid for and they deserve access – weather, traffic, census, budget numbers – it’s your info and you should have it.
— Brian Schatz (@brianschatz) December 19, 2018
…followed by Representative Derek Killmer (D-
Last night the Senate passed a bill I introduced in the House called the Open Government Data Act! There are so many possibilities for our economy when folks can access data they paid to develop and fund through the nation’s largest angel investor, Unce Sam. https://t.co/BvMX54mcCY
— Rep. Derek Kilmer (@RepDerekKilmer) December 20, 2018
Here’s Schatz speaking about the bill at a Data Coalition event last winter:
Two steps remain: passage of the bill in the House and President Donald J. Trump signing it into law. Barring a scheduling issue or unexpected change (keep an eye out for shenanigans on the House floor today), the nation is close to a historic codification of two powerful principles:
- public information should be open by default to the public in a machine-readable format, where such publication doesn’t harm privacy or security
- federal agencies should use evidence to make public policy
Along with making open government data the default in U.S. government and requiring the White House Office of Management and Budget to oversee enterprise data inventories for every agency, the bill would require federal agencies to do the following, as listed in the summary from the Law Library of Congress:
This bill requires departments and agencies identified in the Chief Financial Officers Act to submit annually to the Office of Management and Budget (OMB) and Congress a plan for identifying and addressing policy questions relevant to the programs, policies, and regulations of such departments and agencies.
The plan must include: (1) a list of policy-relevant questions for developing evidence to support policymaking, and (2) a list of data for facilitating the use of evidence in policymaking.
The OMB shall consolidate such plans into a unified evidence building plan.
The bill establishes an Interagency Council on Evaluation Policy to assist the OMB in supporting government-wide evaluation activities and policies. The bill defines “evaluation” to mean an assessment using systematic data collection and analysis of one or more programs, policies, and organizations intended to assess their effectiveness and efficiency.
Each department or agency shall designate a Chief Evaluation Officer to coordinate evidence-building activities and an official with statistical expertise to advise on statistical policy, techniques, and procedures.
The OMB shall establish an Advisory Committee on Data for Evidence Building to advise on expanding access to and use of federal data for evidence building.
Open, Public, Electronic, and Necessary Government Data Act or the OPEN Government Data Act
This bill requires open government data assets to be published as machine-readable data.
Each agency shall: (1) develop and maintain a comprehensive data inventory for all data assets created by or collected by the agency, and (2) designate a Chief Data Officer who shall be responsible for lifecycle data management and other specified functions.
The bill establishes in the OMB a Chief Data Officer Council for establishing government-wide best practices for the use, protection, dissemination, and generation of data and for promoting data sharing agreements among agencies.
While the United States would not be not the first democracy to pass such a law, it would be a welcome advance, codifying many aspects of the open government data policies that have been developed and promulgated in the federal government over the past decade.
How did open government data get into the US Code?
This was no accident of fate or circumstance: This bill, which was previously passed by the House last month, was sponsored by the Speaker of the House, Paul Ryan. It’s an important element of his legislative legacy, and one that can and should earn praise – unlike other aspects of his time with the gavel.
It’s taken years of advocacy and activism by a broad coalition to get here, including the Sunlight Foundation, the EFF, Business Software Alliance, Center for Data Innovation, the Scholarly Publishing and Academic Resources Coalition, American Library Association, the R Street Institute, among many others, and bipartisan efforts on both sides of the aisle. Senator Ben Sasse (R-NE) co-sponsored the OGDA in the Senate, with 5 others, and former Representative Blake Farenthold (R-TX) cosponsored it in House, with 12 others.
That original bill almost made it into law in 2016, when the Senate passed OGDA by unanimous consent, but the House didn’t move it before the end of the 115th Congress. In September 2017, when it was poised to pass Congress as part of the National Defense Authorization Act., before it was stripped from the final version.
In October 2017, the text of the Open Government Data Act, however, was incorporated into H.R. 4174, the Foundations for Evidence-Based Policymaking Act of 2017,
The new bipartisan, bicameral companion legislation was introduced on October 31, 2017 by Speaker of the House Paul Ryan (R-WI) and Senator Patty Murray (D-WA) to enact the recommendations contained in the final report from the Commission of Evidenced-Based Policy.
While it has been watered down a bit, what I argued then is still true today: the bill “offers a genuine opportunity to not only improve how the nation makes decisions but embed more openness into how the federal government conducts the public’s business.”
The addition of OGDA into that bill was “an important endorsement of open government data by one of the most powerful politicians in the world” and “a milestone for the open movement, an important validation of this way of making public policy, and the fundamental principles of data-driven 21st century governance.”
The OGDA was one of the primary legislative priorities for me during my years as a senior analyst and then deputy director at the Sunlight Foundation, along with Freedom of Information Act Reform and Honest Ads Act.
I picked up the transparency baton on OGDA from former Sunlight analyst Matt Rumsey, Sunlight federal policy manager Sean Vitka, OpenGov Foundation founder Seamus Kraft, and Data Coalition founder Hudson Hollister, who drafted the original open data bill, working to make the principle that “public data created with taxpayer dollars should be available to the public in open, machine-readable forms when doing so does not damage privacy or national security” the law.
This is a huge win for public access to public information that every American can and should celebrate today. Special thanks for this victory are due to Christian Hoehner, policy director for the Data Coalition, who did extraordinary yeoman’s work getting this through Congress, Sasha Moss of the R Street Institute, Hollister, Daniel Schuman of Demand Progress, Daniel Castro and Joshua New at the Center for Data Innovation, and Gavin Baker from the American Library Association, some with whom I went to Congress with me to meet with staff over the years and advocated for the bill on and offline.
The passage of this bill won’t mean that the scanned images of spreadsheets that agencies still send in response to FOIA requests will magically go away tomorrow, but journalists, watchdogs and the public can now tell civil servants that they’re now behind the times: open government data is now the default in the USA! Please publish our data on the agency website in a structured format and let the public know.
[Image Credit: Sunlight Foundation]
This morning, James Grimaldi reported that Ajit Pai, chairman of the Federal Communications Commission, has told two U.S. Senators that he has proposed “to rebuild and re-engineer” the agency’s online electronic comment system “to institute appropriate safeguards against abusive conduct.” … Continue reading
When I asked whether when or if it is acceptable for the United States government to charge companies, journalists and the public for government data, citing the example of paywalled immigration data, the chief information officer of the United States told me that “it’s part of the commercial equation” and that it was “actually a discussion point for the strategy” in her office in the White House Office of Management and Budget.
“I don’t have a specific answer,” Suzette Kent went on. “That is something that we’re looking at because there’s many tenets of it. There’s some data the government collects & document on behalf of the american public that may have the mode. There’s other types of data, that people are asking for. It’s a broad spectrum and one we are going to continue to explore.” Kent was speaking at the Data Coalition’s Data Demo Day on June 6 in Washington, DC. Video of the keynote speech she gave on data is embedded below:
When asked about the continued disclosure of data in PDFs and non-machine readable forms by federal agencies, despite President Barack Obama’s 2013 executive order, Kent said simply that she advocates compliance with every executive order and law and cited a Cross-Agency Priority goal to remove paper from agency systems.
Charging for public data is not a new topic or debate, but it has continued to be relevant during the Trump administration, when new concerns have grown about government data access, collection, and quality.
As I wrote back in 2014, local, state and national governments across the United States and around the world can and do charge for access to government data.
While some developers in Europe advocate charging for public sector information (PSI) as a way to ensure higher service levels and quality, adding fees does effectively charge the public for public access and has frequently been used as a barrier to press requests:
A city hall, state house or government agency charging the press or general public to access or download data that they have already paid for with their tax revenues, however, remains problematic.
It may make more sense for policy makers to pursue a course where they always make bulk government data available for free to the general public and look to third parties to stand up and maintain high quality APIs, based upon those datasets, with service level agreements for uptime for high-volume commercial customers.
Instead of exploring a well-trodden path, the United States government should follow the money and determine which data is agencies are currently charging for under public records requests or other means, using FOIA demand to drive open data disclosure.
The Bot Wars, begun they have. Over the past two years, automated social media accounts and fraudulent regulatory filings have been used by anonymous parties to obscure public opinion, distort public discourse, and corrupt the integrity of rulemaking in the … Continue reading
On September 23, 2014, the White House announced that the United States would create an official policy for open source software. Today, the nation took a big step towards making more software built for the people available to the people.
“We believe the policies released for public comment today will fuel innovation, lower costs, and better serve the public,” wrote U.S. chief information officer Tony Scott in a blog post at WhiteHouse.gov, announcing that the Obama administration had published a draft open source policy and would now take public comments on it online.
This policy will require new software developed specifically for or by the Federal Government to be made available for sharing and re-use across Federal agencies. It also includes a pilot program that will result in a portion of that new federally-funded custom code being released to the public.
Through this policy and pilot program, we can save taxpayer dollars by avoiding duplicative custom software purchases and promote innovation and collaboration across Federal agencies. We will also enable the brightest minds inside and outside of government to review and improve our code, and work together to ensure that the code is secure, reliable, and effective in furthering our national objectives. This policy is consistent with the Federal Government’s long-standing policy of technology neutrality through which we seek to ensure that Federal investments in IT are merit-based, improve the performance of our Government, and create value for the American people.
Scott highlighted several open source software projects that the federal government has deployed in recent years, including a tool to find nearby housing counselors, NotAlone.gov, the College Scorecard, data.gov, and an online traffic dashboard. platform, and the work of 18F, which publishes all of its work as free and open software by default.
The draft policy is more limited than it might be: as noted by Greg Otto at Fedscoop, federal agencies will be required to release 20 percent of newly developed code as open source.
As Jack Moore reports at NextGov, the policy won’t apply to software developed for national security systems, a development that might prove disappointing to members of the military open source community that has pioneered policy and deployment in this area.
The draft policy sensibly instructs federal agencies to prioritize releasing of code that could have broader use outside of government.
The federal government is now soliciting feedback to the following considerations regarding its use of open source software.
Considerations Regarding Releasing Custom Code as Open Source Software
- To what extent is the proposed pilot an effective means to fuel innovation, lower costs, benefit the public, and meet the operational and mission needs of covered agencies?
- Would a different minimum percentage be more or less effective in achieving the goals above?
- Would an “open source by default” approach that required all new Federal custom code to be released as OSS, subject to exceptions for things like national security, be more or less effective in achieving the goals above?
- Is there an alternative approach that OMB should consider?
- What are the advantages and disadvantages associated with implementing this type of pilot program? To what extent could this policy have an effect on the software development market? For example, could such a policy increase or decrease competition among vendors, dollar amounts bid on Federal contracts, or total life-cycle cost to the Federal Government? How could it impact new products developed or transparency in quality of vendor-produced code?
- What metrics should be used to determine the impact and effectiveness of the pilot proposed in this draft policy, and of an open source policy more generally?
- What opportunities and challenges exist in Government-wide adoption of an open source policy?
- How broadly should an open source policy apply across the Government? Would a focus on particular agencies be more or less effective?
- This policy addresses custom code that is created by Federal Government employees as well as custom code that is Federally-procured. To what extent would it be appropriate and desirable for aspects of this draft policy to be applied in the context of Federal grants and cooperative agreements?
- How can the policy achieve its objectives for code that is developed with Government funds while at the same time enabling Federal agencies to select suitable software solutions on a case-by-case basis to meet the particular operational and mission needs of the agency? How should agencies consider factors such as performance, total life-cycle cost of ownership, security and privacy protections, interoperability, ability to share or reuse, resources required to later switch vendors, and availability of support?
If you have thoughts on any of these questions, you can email firstname.lastname@example.org,
participate in discussions on existing issues on Github, start a new one, or make a pull request to the draft policy on Github. You can see existing pull requests here and view all comments received here.
With this policy, the White House has fulfilled one of the commitments added to the second National Action Plan for open government in the fall of 2014. While there has been limited progress (or worse) on of the dozens of other new and old commitments made in the three action plans published to date, this draft open source policy is a historic recognition of the principle that the source code for software developed by government agencies or contractors working for them can and should be released to other agencies and the general public for use or re-use.
This is the week for seeking feedback on open government in the United States. 4 days ago, the White House published a collaborative online document that digitized the notes from an open government workshop held during Sunshine Week in March. Today, Abby Paulson from OpenTheGovernment.org uploaded a final draft of a Model National Action Plan to the Internet, as a .doc. I’ve uploaded it to Scribd and embedded it below for easy browsing.
Thank you so much for contributing to the civil society model National Action Plan. The Plan has made its way from Google Site to Word doc (attached)! We will share these recommendations with the White House, and I encourage you to share your commitments with any government contacts you have. If you notice any errors made in the transition from web to document, please let me know. If there are any other organizations that should be named as contributors, we will certainly add them as well. The White House’s consultation for their plan will continue throughout the summer, so there are still opportunities to weigh in. Additional recommendations on surveillance transparency and beneficial ownership are in development. We will work to secure meetings with the relevant agencies and officials to discuss these recommendations and make a push for their inclusion in the official government plan. So, expect to hear from us in the coming weeks!
In a followup post, the White House shared a link to a collaborative online document where the notes from an open government workshop held during Sunlight Week were posted online for comment. In doing so, they moves from sticky notes to a wiki.
— Nathaniel Heller (@Integrilicious) March 17, 2015
What will come of asking the broader public for feedback on the ideas that a workshop of advocates and policy wonks in DC suggested? Stay tuned.