Many of you will be familiar with the now ubiquitous Linked Open Data cloud diagram, maintained by Richard Cyganiak. The diagram illustrates efforts to link together many different data sources, from the CIA World Factbook to DBpedia, a structured database of information extracted from Wikipedia. It looks like this:

We’re very pleased that the diagram’s maintainers, Anja Jentzsch, Richard Cyganiak, and Chris Bizer, have decided to use CKAN to maintain a registry of information about the datasets, from which the diagram will be automatically updated. They have put out a call for up to date information about datasets included in the diagram until next Wednesday 8th September.

From their announcement:

We are in the process of drawing the next version of the LOD cloud diagram. This time it is likely to contain around 180 datasets altogether having a size of around 20 billion RDF triples.

For drawing the next version of the LOD cloud, we have started to collect meta-information about the datasets to be included on CKAN, a registry of open data and content packages provided by the Open Knowledge Foundation.

The list of datasets about which we have already collected information is be found here:

In addition to basic meta-information about a dataset such as its size and the number of links pointing at other datasets, we also collect additional meta-information about the license of the dataset, alternative access options like SPARQL endpoints or dataset dumps, and whether there exist a voiD description of the dataset or a Semantic Web Sitemap.

So if your dataset is not listed yet and you want to have it included into the next version of the LOD cloud, please add it to CKAN until next Wednesday (September 8th, 2010).

Also, if we have collected wrong information about your dataset or if your dataset is only partially described up till now, it would be great if you could add the missing information.

Guidelines about how to add datasets to CKAN as well as about the tags that we are using to annotate the datasets are found here:

We thank all contributors in advance for their input and help, which hopefully will allow us to draw the next version of the LOD cloud as accurate as possible.

We’re delighted to see that the data.gov.uk folks have released the code for their CKAN Drupal module. As many will know, the OKF’s CKAN powers data.gov.uk as well as over a dozen other data catalogues around the world.

From the blog post:

As part of the government’s ongoing work around transparency, today we are releasing some of the custom software code we’ve developed – a CKAN module for Drupal. This is available for anyone to review, use, or modify. We’re excited to see how developers and colleagues across the world put this work to good use in their own applications and projects.

The code itself is attached to this blog post as a tar.gz file and contains one main package with two sub-packages within. This code release allows content to be synched from CKAN into Drupal. CKAN is the system we use as our “back end” to store information about all the data government has released. Drupal is a system to publish web content, and serves as our “front end” through which people can use to find our datasets and comment on them.

The main CKANPackage code creates a Drupal custom content type to represent data in the same way as CKAN. The first sub-package is the CKANImporter which imports packages from CKAN into Drupal and allows this to take place as a one-off batch import or as an update to the latest changes since a specified time. The second sub-package is CKANDatagovuk which correlates fields in CKAN with Drupal hooks.

The code release includes comments in the files to assist users with the functionality. You can of course contact us should you have any questions.

The following guest post is from David Eaves who is the founder of datadotgc.ca, an open data portal powered by our CKAN software that crowdsources the location of open data sets in Canada (Canada has no equivalent of data.gov or data.gov.uk). David is also a member of the OKF’s Working Group on Open Government Data. The post originally appeared on eaves.ca.

We didn’t build libraries for a literate citizenry. We built libraries to help citizens become literate. Today we build open data portals not because we have public policy literate citizens, we build them so that citizens may become literate in public policy.

In a brilliant article on The Guardian website, Charles Arthur argued that a global flood of government data is being opened up to the public (sadly, not in Canada) and that we are going to need an army of people to make it understandable.

I agree. We need a data-literate citizenry, not just a small elite of hackers and policy wonks. And the best way to cultivate that broad-based literacy is not to release in small or measured quantities, but to flood us with data. To provide thousands of niches that will interest people in learning, playing and working with open data. But more than this we also need to think about cultivating communities where citizens can exchange ideas as well as involve educators to help provide support and increase people’s ability to move up the learning curve.

Interestingly, this is not new territory. We have a model for how to make this happen – one from which we can draw lessons or foresee problems. What model? Consider a process similar in scale and scope that happened just over a century ago: the library revolution.

In the late 19th and early 20th century, governments and philanthropists across the western world suddenly became obsessed with building libraries – lots of them. Everything from large ones like the New York Main Library to small ones like the thousands of tiny, one-room county libraries that dot the countryside. Big or small, these institutions quickly became treasured and important parts of any city or town. At the core of this project was that literate citizens would be both more productive and more effective citizens.

But like open data, this project was not without controversy. It is worth noting that at the time some people argued libraries were dangerous. Libraries could spread subversive ideas – especially about sexuality and politics – and that giving citizens access to knowledge out of context would render them dangerous to themselves and society at large. Remember, ideas are a dangerous thing. And libraries are full of them.

Cora McAndrews Moellendick, a Masters of Library Studies student who draws on the work of Geller sums up the challenge beautifully:

…for a period of time, censorship was a key responsibility of the librarian, along with trying to persuade the public that reading was not frivolous or harmful… many were concerned that this money could have been used elsewhere to better serve people. Lord Rodenberry claimed that “reading would destroy independent thinking.” Librarians were also coming under attack because they could not prove that libraries were having any impact on reducing crime, improving happiness, or assisting economic growth, areas of keen importance during this period… (Geller, 1984)

Today when I talk to public servants, think tank leaders and others, most grasp the benefit of “open data” – of having the government sharing the data it collects. A few however, talk about the problem of just handing data over to the public. Some questions whether the activity is “frivolous or harmful.” They ask “what will people do with the data?” “They might misunderstand it” or “They might misuse it.” Ultimately they argue we can only release this data “in context”. Data after all, is a dangerous thing. And governments produce a lot of it.

As in the 19th century, these arguments must not prevail. Indeed, we must do the exact opposite. Charges of “frivolousness” or a desire to ensure data is only released “in context” are code to obstruct or shape data portals to ensure that they only support what public institutions or politicians deem “acceptable”. Again, we need a flood of data, not only because it is good for democracy and government, but because it increases the likelihood of more people taking interest and becoming literate.

It is worth remembering: We didn’t build libraries for an already literate citizenry. We built libraries to help citizens become literate. Today we build open data portals not because we have a data or public policy literate citizenry, we build them so that citizens may become literate in data, visualization, coding and public policy.

This is why coders in cities like Vancouver and Ottawa come together for open data hackathons, to share ideas and skills on how to use and engage with open data.

But smart governments should not only rely on small groups of developers to make use of open data. Forward-looking governments – those that want an engaged citizenry, a 21st-century workforce and a creative, knowledge-based economy in their jurisdiction – will reach out to universities, colleges and schools and encourage them to get their students using, visualizing, writing about and generally engaging with open data. Not only to help others understand its significance, but to foster a sense of empowerment and sense of opportunity among a generation that could create the public policy hacks that will save lives, make public resources more efficient and effective and make communities more livable and fun. The recent paper published by the University of British Columbia students who used open data to analyze graffiti trends in Vancouver is a perfect early example of this phenomenon.

When we think of libraries, we often just think of a building with books. But 19th century mattered not only because they had books, but because they offered literacy programs, books clubs, and other resources to help citizens become literate and thus, more engaged and productive. Open data catalogs need to learn the same lesson. While they won’t require the same centralized and costly approach as the 19th century, governments that help foster communities around open data, that encourage their school system to use it as a basis for teaching, and then support their citizens\’ efforts to write and suggest their own public policy ideas will, I suspect, benefit from happier and more engaged citizens, along with better services and stronger economies.

So what is your government/university/community doing to create its citizen army of open data analysts?

Other posts by David that you might find of interest include:

The following guest post is by Stefano Costa and Federico Morando. Stefano Costa is a researcher at the University of Siena and Coordinator of the OKF’s Working Group on Open Data in Archaeology. Federico Morando is Managing Director & Research Fellow at the NEXA Center for Internet & Society and a member of the Working Group on EU Open Data.

We are delighted to announce that an Italian instance of CKAN is now live! You can see this at:

The translation was undertaken by Stefano Costa, who is coordinator of the OKF working group on open data in archaeology.

There are currently 67 packages available — thanks to the Extracting Value from Public Sector Information (EVPSI) project. In particular, the NEXA Center contributed material generated as part of the EVPSI project, which is funded by the Piedmont Region and coordinated by the University of Turin.

The site was launched on Sunday by OKF Director Rufus Pollock and NEXA Center co-director Juan Carlos De Martin at the 2010 Festival of Economics in Trento and is a collaboration between the Open Knowledge Foundation, the EVPSI project and the NEXA Center for Internet & Society.

The datasets that are currently available on the Italian instance of CKAN come from a first mapping of some of the main silos of public sector information (PSI) in Italy. Many more packages will be provided soon by EVPSI and the NEXA Center, as a product of a much more detailed mapping of PSI holding entities in the Italian Region of Piedmont.

Open data in Italy

Is Italy behind other countries with respect to open data? Judging from the data of the EVPSI project (and from the infringement procedure the the EU started against Italy), the answer to this question is ‘yes’, but things are changing. The Italian CKAN will hopefully help accelerate this change - providing a way for open data users and distributors to find datasets and see whether or not they can reuse them!

The new datasets on it.ckan.net include many which aren’t open, to help people get a ‘big picture’ about what datasets are out there, who holds them, how to download them and how open they are.

There are several bodies that produce data for their own institutional purposes, but most of the databases with clear commercial interest are only available by paying. And even when data are made available on the web they are distributed under restrictive terms of use or under unclear or no terms of use at all. That, considering the default status of potentially copyright and/or database right protected material (i.e. “All rights reserved”) implicitly means that no re-use is possible. This attitude is caused by a combination of factors, including:

  • lack of knowledge about the open data initiative and the benefits of open data for citizens and society at large
  • complex sub-licensing of datasets among many different public and private bodies, so that nobody can be considered the actual owner of data
  • a general fear of situations implying a loss of control over the re-use of data (coupled with a lack of internal guidelines about the access and re-use of data)
  • a difficult financial situation of PSI holders, pushing them to maximize their short run monetary income, without appropriately taking into account positive spillovers for the rest of society and in the medium/long run

For example ISTAT, the national institute of statistics, put their data online for free use, but unfortunately commercial reuse is not allowed - which may inhibit the development of innovative applications and services. See an overview of ISTAT datasets at CKAN.

A notable exception to this mindset is Regione Piemonte, that has recently launched a portal for open data at:

That result has been facilitated by the existence of common regional guidelines about the re-use of public data. What is more, all their currently available data are released under the CC0 license, enabling unrestricted re-use and dissemination by anyone, even for commercial purposes.

There are other regional governments offering some of their data (for example geospatial data) for free, but Piemonte is the only one explicitly adopting an open license. In all other cases, one has to ask for each case, and usually the answer is “free for non-commercial use” only.

The key point is that national and regional governments own large datasets that would be quite easily made available to the public. This process would however require 3 distinct actors, as outlined in the Open Data study by Becky Hogge:

  • government heads
  • civil servants (acting as the “middle layer”)
  • a small but determined group of citizens (or “civic hackers”)

Minister Brunetta promised “data.gov.it” in 6 months, but in the meantime we would like to get a more detailed picture of how open Italian public information is. In particular it will be interesting to see if any local authorities besides Regione Piemonte will consider following in the footsteps of many other local and national bodies around the world - and open up their data!

Interested in starting a new CKAN instance in your country?

If you’re interested in starting a new instance of CKAN for open data in your country, the Open Knowledge Foundation would be delighted to help! If you are able to help coordinate the translation and liaise with other local folks interested in open data — we can set up, host, and maintain the instance on our servers. Just pop us a line on the ckan-discuss list:

We’re extremely proud that data.gov.uk - the UK Government’s open data portal - uses CKAN, OKF’s open source registry of open data. In the months in 2009 that led up to the release of data.gov.uk, OKF worked closely with the Cabinet Office to help them realise their vision of making public data publicly available in an open, reusable way. But our involvement with the UK government didn’t start there. Civil servants - particularly members of the Office for Public Sector Information - have been attending OKF events like OKCon since at least 2005. And we know that Sir Tim Berners Lee - who was brought on as an expert advisor to the Government as they worked up to the data.gov.uk project - was reading the OKF blog prior to his now famous “Raw Data Now!” talk at TED! ;-)

A new report released late last month charts the history of open government data in the UK and the US, and it’s a fascinating read. Written by OKF board member Becky Hogge for a consortium of grant-giving organisations including the Hewlett Foundation, the Ford Foundation, the Omidyar Network, the Open Society Institute and DfID, the Open Data Study:

“…explores the feasibility of advocating for open government data catalogues in middle income and developing countries. Its aim is to identify the advocacy strategies used in the US and UK data.gov and data.gov.uk initiatives, with a view to building a set of criteria that predict the success of similar initiatives in other countries and provide a template strategy to opening government data.”

I was interviewed for the report, as were John Wonderlich from the Sunlight Foundation, Tom Steinberg from mySociety and Ory Okollah from Ushahidi. Other interviewees include experts like Ethan Zuckerman and Toby Mendel, and - of course - Sir Tim Berners Lee.

The report draws some new and surprising conclusions. As well as recognising the role of organisations like the OKF and mySociety in bringing about data.gov.uk, it emphasises how crucial engagement with civil servants was to the success of the open data project in the UK. It raises interesting questions about what motivates politicians to embrace open data strategies, and even posits that the long battle to open up geospatial data in the UK worked in a positive way: “the barrier [opening geospatial data] imposed in the UK may have served as a common call to action among both civil society and the middle layer government administrators, which in turn served to strengthen the crucial communication between these two groups in the trajectory towards data.gov.uk, and ultimately enrich the final proposition when compared to data.gov.”

The report contains mixed findings about the prospects of similar projects in developing and middle income countries, providing a useful and very detailed checklist for advocates working within those countries to consult, and pointing to the potential role of international donors in this context. In short, I’d recommend reading this report to anyone interested in open government data, or indeed, in advocacy generally. Because, as Becky notes in her blog post introducing the report:

“I’d be hard pressed to think of an idea that has permeated as quickly as open data has from the fringe to the centre.”

The following guest post is from Olav Anders Øvrebø, Assistant Professor at the University of Bergen, and member of the Open Knowledge Foundation’s Working Group on EU Open Data. This text was first published as a European Public Sector Information Platform Topic Report on ePSIplatform.eu.

A series of promising new initiatives gives reasons to be a lot more optimistic about government data reuse in Norway today than anyone could have been a year ago. The right tools will hopefully soon be available. Now convincing examples of reuse are needed.

When the application deadline expired at midnight we had received 135 applications to Nettskap! We are very pleased!

This exuberant tweet was published on the Ministry of Government Administration’s official account on May 10. The idea competition Nettskap 2.0, a Norwegian version of the Apps for Democracy or Show Us a Better Way contests, had been announced just a month earlier, which makes the quantity of applications quite impressive. Nettskap applicants were not required to place government data reuse at the heart of their projects, but the Ministry had encouraged this. It worked - 90 projects, two out of three, are based on the reuse of data.

Winners of the competition are to be announced in June, and will receive funding totaling 2,5 Million Kroner (around 320.000 Euro).

Nettskap is just one of several pieces of good news for government data enthusiasts coming out of Norway lately. In April, the same Ministry unveiled plans for a Norwegian datastore. The URL has been chosen - data.norge.no - and work is now underway on the project details and tender. In the meantime, a blog is set up at data.norge.no where government data questions are discussed.

Two reports on public data reuse have been published already this year, helping to raise interest in the topic. The first was written by a group at the University of Bergen (led by me). The second was produced by an expert group put together by the Norwegian Board of Technology, a consultative office to Parliament.

Norway has long had the potential to become a very interesting place for government data reuse. The public sector is, relatively speaking, considered well-run and efficient, and lots of quality data are collected. There is a deep-rooted tradition of transparency in government, supported by a Freedom of Information Act (FOIA). And the population is more tech-savvy than most, always quick to adopt new communication technology and services.

But despite these favourable conditions, Norway has not been in the data reuse vanguard so far. The accelerating activity and increased attention given to government data issues during the last months might change that. In this article I will consider three factors which I believe will decide the outcome:

  • Infrastructure: The coming datastore needs to be supplemented by an open license for data reuse and practical initiatives to encourage data publishing.
  • Principles: The PSI directive has been implemented in the FOIA. However, the fundamental principle of division of labour between the public and private sector (and civil society) in data reuse is still not generally acknowledged.
  • Reuse in practice: Some public sector agencies are already doing an excellent job making data available, while others haven’t even started. Convincing examples of good reuse are quickly needed for recent positive developments to take hold.

Read the rest of this entry »

CKAN v1.0 Released

May 18th, 2010

We are pleased to announce the availability of version 1.0 of the CKAN software, our open source registry system for datasets (and other resources). After 3 years of development, twelve point releases and a several successful production deployments around the world CKAN has come of age!

CKAN around the world

As well as being used to power http://ckan.net and http://data.gov.uk CKAN is now helping run 7 data catalogues around the world including ones in Canada (http://datadotgc.ca / http://ca.ckan.net), Germany (http://de.ckan.net/) and Norway (http://no.ckan.net).

CKAN.net has also continued to grow steadily and now has over 940 registered packages:

Changelog

This is our largest release so far (56 tickets) with lots of new features and improvements. Main highlights (for a full listing of tickets please see the trac milestone):

  • Package edit form: new pluggable architecture for custom forms (#281, #286)
  • Package revisions: diffs now include tag, license and resource changes (#303)
  • Web interface: visual overhaul (#182, #206, #214-#227, #260) including a tag cloud (#89)
  • i18n: completion in Web UI - now covers package edit form (#248)
  • API extended: revisions (#251, #265), feeds per package (#266)
  • Developer documentation expanded (#289, #290)
  • Performance improved and CKAN stress-tested (#201)
  • Package relationships (Read-Write in API, Read-Only in Web UI) (#253-257)
  • Statistics page (#184)
  • Group edit: add multiple packages at once (#295)
  • Package view: RDF and JSON formatted metadata linked to from package page (#247)

Bugfixes:

  • Resources revision history (#292)
  • Extra fields now work with spaces in the name (#278, #280) and international characters (#288)
  • Updating resources in the REST API (#293)

Infrastructural:

  • Licenses: now uses external License Service (’licenses’ Python module)
  • Changesets introduced to support distributed revisioning of CKAN data - see doc/distributed.rst for more information.

Thanks

Lastly a big thank-you to everyone who has contributed to this release and especially to the folks at data.gov.uk!

At the Open Knowledge Foundation we have been working hard to support the development of open data catalogues around the world. The main purpose of these is to make official datasets easy to find and to reuse — whether by researchers, journalists, or web developers building new applications or services for citizens.

Work is underway in Austria, Canada, Finland, France, Germany, Hungary, Italy, Norway, Spain, and, of course, in the UK with data.gov.uk. Most of these data catalogues will be built and maintained by the public in the first instance — thanks to the wiki-like nature of the software behind CKAN, our open source registry for open data.

Once a data catalogue is up and running, the next step is to populate it with information about government datasets. Recently we’ve been thinking of ways to encourage people to start adding this kind of information. While in the past we’ve had data discovery workshops and package parties, in recent weeks we’ve been talking with a number of open data advocates in different countries about putting on a series of ‘Data Hunt’ events. These would turn the process of finding and documenting interesting (and hopefully open!) government datasets into a game.

In particular we’d like to record details of the following for official documents and datasets:

  • What is it? (description)
  • Where can I find it? (URL/download URLs)
  • Can I reuse it? (legal/licensing information)
  • Has anyone else created a version of it that is machine-readable / in format X / etc?

We’re still in the early stages of planning for these events — but thought we’d put out a call for input at the outset. Below are some of the things that we’re currently thinking about:

  • How can we structure the events to be as fun as possible? E.g. should we have teams? Points? Prizes? Different categories (the most datasets added, the most open datasets added, the most interesting datasets added, …)?
  • Would it be useful to have a how-to guide for Data Hunt participants — e.g. with ideas on where to find datasets, what kind of information to look for, how to tell if a dataset is openly licensed or not, and so on?
  • Should we try and coordinate events internationally — e.g. to have several around the world at the same time?

If you have any cunning thoughts or suggestions about any of these points - please drop us a comment on this post! also if you’d like to help out — e.g. by organising an event in your country, by designing a nice logo, etc — we’d love to hear from you!

Not so long ago we were in contact with David Eaves, a Canadian public policy analyst and open government data advocate (who advises the Mayor of Vancouver about open data and open government), about starting an catalogue for Canadian open government data. A couple of weeks ago he and a small team of coders and advocates launched a citizen driven catalogue called datadotgc.ca, which we’re proud to say is powered by CKAN!

The site uses the CKAN software under the hood with a Drupal front end - and they’ve added some nice features like a custom input form (with Canadian government departments, license options and suchlike), and a ‘league table’ showing which departments share most datasets:

Colin Calnan, who helped work on the site, has just posted details of the technical work involved in getting an instance up and running, Drupal integration and so on. Following are a few excerpts from his post:

For the benefit of the programming and Drupal community, I’m going to run through, with the aid of code samples, the development of the Drupal module to communicate with the CKAN API (which is where the data is stored). I’ll also walk through Theming, integration with Google Charts, Tag Clouds and most importantly, caching.

What is CKAN?

CKAN is a registry or catalogue system for datasets or other “knowledge” resources. CKAN aims to make it easy to find, share and reuse open content and data, especially in ways that are machine automatable.

CKAN is a nice big database that is built to accept user input of the type of data we’re trying to collect for datadotgc.ca. It has a slick front and back end that allows administrative access to the collected data. You can find out more on their website.

CKAN’s API

In order to utilize the power of CKAN I needed to link it up to Drupal. CKAN has a powerful and flexible API that I used extensively in the module.

The Foundation

Early on in the project I got in touch with the wonderful team at CKAN and they then put me in touch with Sean Burlingford from the data.gov.uk development team. They had also built their site in Drupal and Sean had lots of information on how they tweaked their CKAN site to work with Drupal. He worked hard to open source some of the work that they had done, and released it just in time for us to get started. Sean’s module provided the basic API connectivity we needed to get started and was the foundation for our module.

The Build

How do you integrate Drupal with the CKAN API? Let’s start with the basics: [...]

There’s lots more of the technical nitty gritty (including code snippets) on Colin’s post (and more to come soon, he assures us!).

If you are interested in starting an instance of CKAN for open (government) data in your country, drop us a line on our ckan-discuss list where there is a growing group of developers and translators who can help you to get something up and running!

The following post is from David Read, a developer working on the Open Knowledge Foundation’s CKAN project. David attended the Greater London Authorities’ Possibilities of Real Time Data conference earlier this week.

London’s authorities have opened up lots of their data this year, kicking off in January with the launch of the London Data Store (which we blogged about here). You can download, mash-up and analyse stats about crime, housing, education, planning and so on, but the biggie that many developers are desperate to get their hands is transport information. The GLA and 4ip held a half-day conference on Monday at City Hall on this public data, and transport data got top billing.

Dr David Mountain at Placr described how he’s been screen scraping the London Underground departure boards. Although his results were somewhat predictable - that waiting times increased during peak hours, or when the line had a problem - there was obvious interest from the audience in knowing what to expect on unfamiliar lines, and comparison between particular stations.

It is incredible to think that bus and train companies don’t make their timetables open. Chris Osbourne from ITO World has an interesting way to automatically produce extremely helpful bus maps, yet only two small British areas allow it. He made the point that councils subsidise a massive number of bus services, yet the ‘bus barons’ hug their data and stifle the innovation that might actually increase their custom whilst improving their usefulness to society.

Titled “Possibilities of Real Time Data”, the conference was positioned to highlight the value of open data, but I was surprised that there was not a discussion to work through the problems faced. The room seemed to be a healthy mix of technologists, representatives from London boroughs and other public data holders including Transport For London. Only briefly did we glean an idea of the road blocks TFL and other providers see preventing them releasing bus, tube and rail information. Data Protection was mentioned and clearly there are many more areas to be discussed, but surely this needs to be discussed in public to move it forward?

The success of using more general data to closely monitor and improve performance was the theme of a CTO of a council in Washington DC. Bryan Sivak described how they have been publishing lots of public data for about 5 years now on their Data Catalog.

He had stories about improved snow clearing with residents reacting to the map of snow-ploughed areas. They’ve had a couple of years’ worth of application competitions, the widely copied ‘Apps For Democracy’, but they also felt a clear need to develop some themselves. He mentioned a couple of measurable successes of using data: increased rehousing of homeless and spotting trends in overtime use.

What was most interesting regards my involvement as a CKAN developer were Sivak’s future plans. Firstly he mooted “Data Catalog in a Box”, where they open-source all their code so other cities/countries can reap similar benefits. It is great to see another example of publicly funded software being given back to the public, rather than locked away for private use. And although there is sure to be plenty of overlap with CKAN, and competition is healthy, no doubt we can both learn from each other and it creates more options for organisations wanting to catalog their open data.

The other future plan for Washington DC that piqued my interest was their “OpenCity API”. They have linked up with 7 of the top cities in the US to agree on the same web API for ‘government service requests’. i.e. for filling pot holes, requesting snow clearing etc. All this openness of data, source and sharing of APIs is very promising - other governments take note!