Indeed. Much of what I see from the UK GDS is bang on; there are clearly some very bright people there. Take a look at their guidance to other government agencies on exposing APIs: https://www.gov.uk/service-manual/making-software/apis.html
It's concise, in plain English and very cleverly avoids using the terms REST or RESTful even though they're basically describing RESTful architectural constraints. It's clever because they avoid getting dragged into religious wars about API technicalities and provide flexibility for situations where fully REST-compliant APIs are not practical.
I wish more public servants (and politicians) understood web APIs and the economic value that would be unleashed if governments exposed more (both data and transactional). But instead, most are obsessed with building 'portals' and 'mobile apps', because those are 'innovative'!
Agreed - and echoes a similar case I read about when the folks behind the Ordnance Survey (government agency and makers of truly exceptional maps for outdoor enthusiasts in the UK) proudly showed how they made their data online for a licensing fee that generated about £10m a year.
The people they were presenting to? A group of European governments that endorse massive, free access to this sort of data - as a means of spurring innovation and economic growth.
Now contrast that with London Mayor Boris Johnson's movie to open up the data for their city bike sharing scheme... released on a Friday, by Monday there were two apps that were slicker and better-developed than the city was planning, plus were now two small businesses.
Yeah the whole 'charging for government data' thing drives me crazy!
In almost all cases, the marginal cost of producing the 'good' (data) is approximately 0. Furthermore, because infinite copies of data can be made, there is no reason for price rationing. And there's no argument for granting monopoly through artificial scarcity (like there might be with patents and copyright) as the government would have produced the data anyway (often as a byproduct of some other activity e.g. income tax reporting).
Government data is a public good, in the strict economic sense (non-excludable, non-rivalrous).
Setting prices above marginal cost (i.e. 0) causes significant dead-weight loss; it is absolutely inexplicable and inexcusable public policy. This isn't complex economic theory. This is economics 101; you'll find this information in any first-year uni economics textbook (in the 'market failure' chapter). I can only conclude that public servants who do this kind of thing either aren't familiar with extremely basic public economic theory (which is a bad sign), or are actually trying to reduce public welfare (making the public service a rather odd career choice).
Conceptually, charging for government data is equivalent to levying a super-narrowly based and highly inefficient sales tax. The most baffling thing is that it's conservative governments that generally approve these kinds of policies, even though the net effect is to increase the size of government at extremely high efficiency costs.
It's concise, in plain English and very cleverly avoids using the terms REST or RESTful even though they're basically describing RESTful architectural constraints. It's clever because they avoid getting dragged into religious wars about API technicalities and provide flexibility for situations where fully REST-compliant APIs are not practical.
I wish more public servants (and politicians) understood web APIs and the economic value that would be unleashed if governments exposed more (both data and transactional). But instead, most are obsessed with building 'portals' and 'mobile apps', because those are 'innovative'!