Adding APIs

I'm unsure how I can publish my data on data.gov.uk, given that it's available through an API and not as a dataset file.

The new site https://courttribunalfinder.service.gov.uk/ is a search engine for England+Wales courts. Each court page is also available in JSON-LD format (using the Accept header). As such, it can be considered a provider of open government data, properly linked and machine-readable. And so it would be a good thing if that data could be found on data.gov.uk, but I haven't found out how to do it. Of course I can create a dataset and link to the URL above (like TNA did for http://data.gov.uk/dataset/legislation-api/resource/ded71828-8cc2-494d-8...), but it's a poor way to link to the data, especially as the page will say "URL does not appear to be open data".

Can I do better?

Comments

Courts and tribunals dataset

A dataset doesn't have to be open to be catalogued on Data.gov.uk. There are thousands of non-open datasets recorded as well.

It sounds as if your issue is that you want the dataset to be classified as open data and catalogued with a star rating, but the system won't allow that because you cannot provide a direct link to the dataset in a re-usable format.

That is, I think, the correct result. APIs and datasets are two separate things. APIs are fine for particular types of re-use, but if you have not released a version of the courts and tribunals dataset for bulk download as well then it isn't really open.

-- Owen Boswarva, 20/09/2013

 Flag as offensive 

Hi Owen, I don't see how only

Hi Owen,

I don't see how only providing an API to your data and not a dump of it in a file makes it not open data.

APIs and datasets (aka datafiles) are both providers of data. A dataset can be downloaded and processed, but APIs are always up to date, are much more linked-data-friendly. And open.

It's unfortunate that data.gov.uk doesn't support APIs as data providers, because they are the future of linked data. Perhaps we can create a page with a list of APIs provided by gov services. At least it's better than creating a dataset page for the API, like the legislation API I mentioned in my original post.

Cheers,

Max.

 Flag as offensive 

APIs vs open

Max,

Notwithstanding your own views on what constitutes open data, if potential re-users cannot readily obtain the dataset in bulk that severely limits the extent to which they can re-use the data.

The API-only approach is really only suitable for viewing of the data by end-users and for re-use of the data by developers (and even then only for a limited range of use cases).

What about direct analytic use? What about re-users who want to package the dataset into their own data products? There are numerous use cases allowed under an open licence that would be confounded by the barriers you have put up to availability of the data.

There are certainly some types of data where the potential for re-use is primarily dependent on an API, because the dataset is very large and updated very frequently. Live train times and weather observations are two obvious examples. However even in those cases it is best practice to provide regular "snapshots" of the data as bulk downloads in order to support types of re-use that do not require the most up-to-date version of the dataset. The dataset underlying the court finder is, in any case, not that type of data.

-- Owen Boswarva, 27/09/2013 

 Flag as offensive 

Court finder data now available as a bulk download

I note that this dataset is now available as a bulk download as well as via the API, which means it is proper open data. Well done to MOJ for addressing this.

-- Owen Boswarva, 15/01/2014

 Flag as offensive 

Files and APIs are definitely

Files and APIs are definitely two facets of datasets and sometimes one makes sense more than the other (or indeed both make sense). But in the end my point is about data.gov offering both facets, especially for datasets for which dumps don't have any use, or are not available. Right now, APIs are not supported by data.gov, which is what I'm sorry about.

 Flag as offensive 

Apps section of Data.gov.uk

Max,

The purpose of Data.gov.uk is mainly to catalogue datasets rather than the delivery mechanisms for those datasets.

However you could submit the https://courttribunalfinder.service.gov.uk/ site as an entry in the Apps section of Data.gov.uk. The Apps section is not just for mobile apps; it also includes some lookup-based websites and APIs.

I hope MOJ will consider releasing the courts and tribunals dataset as a bulk download under an open licence. However regardless of whether the dataset is open data it should be catalogued on Data.gov.uk as a data asset held by MOJ.

-- Owen Boswarva, 30/09/2013

 Flag as offensive 

Adding APIs

Thanks, I have made a request to add an app.

I don't think that it's a very good idea to categorise API providing data with apps consuming data, though. A single hand-edited page that lists available APIs would be better. 

 Flag as offensive