Open data links | 22 Feb

Some things I’ve been reading that should be of interest. There is a great deal more that I’ll put up soon.

Read the history of open data in Richard Poydner’s “Peter Murray-Rust and the data-mining robots“. Indeed, without Peter Murray-Rust, we wouldn’t have the Open Data Commons project.

Speaking of Murray-Rust, you can listen to a Talking to Talis podcast with him and read Richard Poynder’s interview with him.

And crossposted from opencontentlawyer:

Report on Ordnance Survey licensing practices. Free Our Data covers in this post the report from the Commons Select Committee on Communities and Local Government looking into Ordnance Survey’s licensing and business model.

Ordnance Survey is Britain’s national mapping agency. Due to UK government works being able to have IP rights over their work, if OS or some other agency wants to make their work public domain, they’d need some tool such as the PDDL to do it.

Podcast with John Wilbanks. The head of Science Commons talks with Ellen Duranceau of MIT Libraries News about SC and open data.

Also, Sophie L. Rovner “It’s All About Access” Chemical and Engineering News.

New article out | Implementing Open Data: The Open Data Commons Project

“It won’t be long before open access is old hat, taken for granted by a new generation of tools and services that depend on unrestricted access to research literature and data. As those tools and services come along, they will be the hot story. But historians will note that they all depend on open access and that open access was not easily won.” Peter Suber Free and libre/open source software (F/LOSS) movements have spawned similar solutions in many other contexts, each at differing stages of development. As F/LOSS enters the routine and familiarity of middle age, the open content movement–open source for non-software copyright and best embodied by the work of Creative Commons –has just graduated university and is getting a feel for the world. Even younger is the open data movement, whose legal tools have just started to come online.

And with that, starts a new article I’ve written for the Open Source Business Resource, which is now available in the February issue. Implementing Open Data: The Open Data Commons Project

Limiting liability in the PDDL

A comment via personal email and via the discuss list for the Open Data Commons set of legal tools. This is about the Public Domain Dedication & Licence:

Would it be possible to include an indemnification clause for misuse of data, for example when the data is passed on to a third person not bound by the license? The reason is that the disclaimer only binds the person downloading the data from the data source. If that person passes the data on to a third party, all warranty disclaimers become unenforceable because that third party did not agree to them (and the license is not passed on to the third party because it is not a “copyleft”-type license due to the public domain dedication). Are there any other legal instruments to protect the data provider against liability and lawsuits stemming from the data (imagine that the data has been modified down the road and is not accurate anymore)?

This is an interesting idea, and one that I suspect that attorneys reviewing the PDDL for use by a particular data provider will be interested  in  hearing more about. But just to be clear for all the readers, I’d like to give a few illustrations.

An indemnification clause states that you will pay someone you have a relationship with for the claims of third parties. In the context of the PDDL and the above suggestion, an indemnification clause would be saying that anyone that got the information from the data provider under the PDDL would pay them if someone that the data recipient gave the database to turned around and sued the original provider.

A=Database/data provider, offering data under the PDDL.

B=Recipient of database/data from A under the PDDL.

C=Any third party receiving the database/data from B.

D=Another third party receiving the database/data from C (and so on from D to E to F…)

A gives database/data to B under PDDL.  The Section 5 disclaimer and limitation of liability applies because B agreed to it (assuming that this disclaimer is valid in the relevant jurisdiction).

B gives it to C without the text of the PDDL attached, which is permitted because the database/data is in the public domain. B hasn’t agreed with A to the disclaimer in Section 5, and so it doesn’t apply.

C relies on the data, suffers damage because the data is inaccurate. C wants to sue A for providing bad data. An indemnification clause would mean that B pays A for costs/fees/damages/etc associated with the C vs A suit.

There seem to be two primary questions here:

  1. Can C sue A and consequently what is the liability for A?
  2. Would an indemnification clause be a suitable means for protecting A?

1. C vs A and A’s liability

This question requires a bit more research and thought on my end, so I won’t comment too much. But from a practical standpoint,

  • It seems like if you were presented with public domain data that you’d be pretty aware that the product is “AS IS” and that anyone could have modified it, and that it would be unreasonable to think otherwise.
  • If C was wanting to make sure that they had the most up-to-date and clean data, then they’d come to A (assuming A is that provider) who would present it to them with the PDDL and its Section 5 disclaimer.

2. Would an indemnification clause be a suitable means for protecting A?You can in part avoid the first question by putting in an indemnification clause that says whatever liability is there for A (if any), B pays for it. While I think from a practical legal standpoint that something like this might be desirable, I’m not sure how this fits in with the norms of the Free and Open Source Software, and open content movements.  If the PDDL is too overreaching then many might reject it on philosophical grounds. I’m also not sure that an indemnification fits into the spirit, if not the letter, of the Science Commons protocol.

It will be interesting to see the discussion develop around the idea of liability. Please post your comments or join the discuss list to contribute.