In April last year, I published a post on what I considered to be the 5 principles for Govt 2.0, one of which was open source government. This week, some academics form Princeton University have published a paper, still in draft, with the wonderful – if only slightly melodramatic – title, Government Data and the Invisible Hand, that considers this very issue.
To recap, the concept of open sourcing government is essentially about allowing third parties (citizens, companies, non-profits, etc.,) direct access via APIs to government data, so:
that individuals, communities and businesses are able to interact with government web applications in ways that are useful to them.
5 principles for Govt 2.0
The UK Cabinet Office released a report in June last year that looked at what this would mean for their public management system. The economic impact alone, as the report makes clear, had the potential to make a significant contribution:
2006 figures from the Office of Fair Trading that estimate that improved availability of information to re-users could double the direct market value of public sector information to £1.1 billion per year.
The value of government information
The Princeton paper authors, however, seem to be going some way further, calling for the US federal government to reduce the role it plays in presenting online information to citizens. The authors argue that the key role for federal agencies should be opening up their data, rather than building websites that provide a platform (and by inference, not a particularly good one) and a filter for people to access the information.
Their premise is an attractive one. That government
should focus on creating a simple, reliable and publicly accessible infrastructure that “exposes” the underlying data. [... The Government should] require that federal websites themselves use the same open systems for accessing the underlying data as they make available to the public at large.
Government Data and the Invisible Hand, p1.
Effectively, this means that government agencies could focus their attention (and taxpayer dollars) on the quality and accessibility of the information, and not on the presentation level. It’s a compelling proposition, particularly when you consider the current state of the namespace (in any jurisdiction, really).
The authors argue that the market, in the form of these third parties developing applications that reuse the government data, will drive economies of innovation and accessibility that are beyond anything that government itself could hope to provide. They list some of these advanced features:
- advanced search
- RSS feeds
- links to information sources
- mashups with other data sources
- discussion forums and wikis
- data visualization
- automated content and topic analysis
- collaborative filtering and crowdsourcing analysis
It is worth pointing out that some of these advanced features are already part of the namespace here; albeit with mixed success. Advanced search, RSS feeds, and wikis are all essential elements of the .govt.nz space.
There are a couple of concerns that I have. The authors acknowledge that in some case there will be no private actor willing to step forward and create a compelling website based on the data
. The notion that government makes all information accessible, irrespective of it’s apparent value, is a fundamental one. Abrogating that responsibility to third parties seems fraught with potential to disadvantage some sections of the community. Mike W leaves a comprehensive comment to this effect on Ed Felten’s blog (one of the authors of the paper).
As an aside, ensuring that people can access a government data set via a visualization (like EveryBlock, for example) using a screenreader can be done, but it is hard work…
More of a concern, however, is the notion that we can either continue to try to build usable websites or simply outsource innovation in the namespace. I don’t see, as the authors apparently do, that the two are mutually exclusive. Indeed, there is an argument that government should retain and build more capability for innovation, rather than adopt practices that would encourage this sort of activity to atrophy.
Those concerns aside, however, what the authors of the paper are proposing is both an effective and efficient approach to transformed government. We should be seriously considering the same here in New Zealand.
Photo: kool_skatcat









9 Comments
Oh hell yes we “should be seriously considering the same here in New Zealand”. It seems a no-brainer to me that opening up Government data via APIs (and I agree with you there’s good reasons for Government to present the data too) is going to bear all sorts of fruit.
This is going to happen - look at all the grass-roots stuff starting up anyway. Why can’t NZ lead the world here?
A question back to you Jason - what are the barriers? Technical? Philosophical? Ignorance? …
Thanks Mike. You are right, it is happening in a (very) limited fashion. Statistics New Zealand, for example, are making public some of their data sets; while it is a long way from an API that developers can directly interact with to create public value, it is a start.
I’m not sure what the barriers are, probably a combination of factors. I suspect that somewhere in there is the fact that for most CIOs, creating that public value is not seen as one of their outcomes. But I’m open to correction…
Hi Jason
Gerry McGovern has picked up on the ‘Invisible Hand’ article also and concludes “It’s a great idea to supply well-structured data to private enterprises so that they can develop simple, fast web services. However, the government still has a vital role on the Web. Not everything can be privatized. For the government to truly serve its customers on the Web it needs to address the following issues:
1. Get away from a technology obsession
2. Manage customer top tasks, not government websites
3. Get politicians off government websites
4. Stop government vanity publishing
5. Develop a government archive”
That seems like reasonable advice to pursue…
Cheers
Fergus
Thanks Fergus. I think McGovern has got the wrong end of the stick. The authors aren’t proposing that government stop publishing to the web, they are just saying that the process should be standardized (literally, using RSS, XML & so on) so that third parties can access and utilize the data in the same manner those agencies do.
Yes, McGovern’s points are reasonable advice, but I think overall the advice misses the broader strategic vision that the authors are proposing. The five points may be a useful way of looking at government namespaces, but they are constrained by a particular narrowness of focus…
Hans Rosling spoke about this during his GOVIS 2007 presentation. View his presentation here (http://tinyurl.com/4dks29), the discussion about open data starts at about 50:00.
Jason - this paper and your comments apply especially to govt departments that are housing spatial data - making public data available via standardized (OGC) web services for ingest into mashups using google maps etc, is where I would love to see our department head - there are numerous licensing issues preventing this currently but this is something that needs to change as well. Its still amazing to me that publicly funded data is not free to the public…. that said I believe there are enormous wins for everyone involved if we can get out data out and open it to scrutiny/validation/user generation.
Jase,
I think you’re right about the outcomes focus of public sector management being the blockage. Sadly, that’s inherent in the structural design of the State Sector Act 1998. Each agency has a specific area of operation and must conduct themselves in a business-like manner. And giving away stuff is not seen as a step in achieving those outcomes. CEs may chatter about working together and transparency in their regular talkfests but, when the rubber hits the road the first question is “how much will this cost us?” followed by “why should we pay for it?”. As I argued with Web Standards compliance, this sort of stuff needs to be in the CE’s performance agreements before they’ll give it their full attention. And it needs to be driven politically as well, as part of the whole of government approach. Perhaps the current project re-looking at the Framework for Government-Held Information is a good place to get some traction.
I also think you’re right about McGovern - I’ve long had a bag of salt within reach when reading his stuff. He seems to talk a good line, but his analysis is often superficial.
Hi Jason - great insights as ever. You might be interested to check out the recently hatched “Recommendation of the OECD Council for enhanced access and more effective use of public sector information” released in June 2008. “This Recommendation is designed as a general framework for Member countries to foster wider and more effective use of public sector information and content, as well as the generation of new uses from it. It lays out principles for openness and transparent conditions for re-use, quality and integrity, new technologies and long-term preservation, copyright, pricing, competition and redress, and international access.” Although OECD Council Recommendations are as about as soft as international soft law can get, they are not without interest for those of us with a passion for comparative public policy. Especially with the Recommendation, the OECD Council instructs the Secretariat to report back on OECD member countries’ performance in applying the principles every 3 years…..Watch this space for some longitudinal comparative data folks!
Joanne Caddy
It would be good if New Zealand (or any other nation, for that matter) could demonstrate leadership in documenting its governmental agency strategic plans in StratML format in support of the purposes outlined at xml.gov/stratml/index.htm#DefinitionPurposes Under the auspices of AIIM, we aim to establish StratML as an international voluntary consensus standard for potential use by all organzations worldwide. AIIM’s StratML Committee site is at http://www.aiim.org/standards/.....x?ID=34121 Participation is welcomed and encouraged.
3 Trackbacks
[...] reporting on this can be found here, here, here and [...]
[...] discuss it. Many blogs have simply ignored the draft’s pagely imperative (see, e.g., here, here, here, and here). One sheepishly declared: “it kindly asks us not to cite the draft, but - since it’s out [...]
[...] Open sourcing government | NPSC Blog - To recap, the concept of open sourcing government is essentially about allowing third parties (citizens, companies, non-profits, etc.,) direct access via APIs to government data, so: that individuals, communities and businesses are able to interact with government web applications in ways that are useful to them. [...]