IATI data licensing (for unencumbered data use!)

(Andy Lulham) #1

@stevieflow’s recent datastore discuss post raised some issues about IATI data licenses that we should aim to resolve, in order to facilitate unencumbered and unfettered data use.

For context, the licensing section of the publishing guidance on the (old) IATI website says:

The TAG secretariat, in collaboration with a small group chaired by the World Bank and including an open data/intellectual property lawyer, produced a set of recommendations for licensing. The IATI Licensing Standard, agreed in February 2011 at a meeting of signatories and the IATI Steering Committee, is that information published through the IATI standard should be licensed under an open license. It is a set of principles that must be adhered to, rather than a prescriptive set of terms and conditions.

(Emphasis mine. NB it looks like the above paragraph was lost in the move to the new iatistandard.org site, and so it’s missing from the corresponding page. Thanks to @markbrough for this institutional knowledge!)

So, here are four proposed action points aimed at providing a consistent approach to IATI data licensing:

  1. Make data licenses mandatory for all new datasets in the registry (i.e. make it a required field, and remove the “Not specified” option). @amys has already created a ticket for this.
  2. Improve the licensing guidance on the IATI site so that it is (i) self-consistent and clear that IATI data is open data (see: the contradictory wording that @siemvaessen flags on discuss) and (ii) provides a bit more explanation of why e.g. non-commercial (or closed more generally) is problematic.
  3. Fix existing “closed” and “no license specified” data in the registry, by contacting publishers and asking them to select an open license. I guess if these aren’t updated after some pre-defined notice period (h/t @stevieflow), these datasets would either need to default to an open license or be removed in order to be consistent with the IATI Licensing Standard.
  4. Remove the closed license options from the “choose a license” dropdown on the registry.

How does that sound? Tagging people who commented on licensing in the datastore thread: @stevieflow @Herman @yohannaloucheur @bill_anderson @siemvaessen @David_Megginson

(Herman van Loon) #2

Hi Andy,
Sounds great! Imo these 4 points nail the license issue. Completely agree that we shouldn’t accept closed licences as a part of the standard. IATI is an open standard.

(Yohanna Loucheur) #3

Thanks Andy for this very useful summary and list of actions! Agree as well.

(Steven Flower) #4

Excellent, thanks @andylolz. I agree - this is a very practical list to implement

I see some difficulty here, as we are actually saying that non-open data would no longer be accessible via the IATI Registry? This should therefore involve a period of notice (as with the deprecation of version 1) to enable these publishers to schedule their action (if any)?

(Andy Lulham) #5

+1. Have amended the original post.

IATI Datastore - what data should go in?
(SJohns) #6

Just thinking this through for CSOs. Anything that makes it super-simple to do the right thing, for example making the license field mandatory and only making it possible to only choose an open license is very welcome. Looking at the dashboard, losing the ‘licence not specified’ would affect 1395 activities from 443 organsations, and losing the non-open options would affect 54 activities from 23 organisations.

I wonder if we should go further and reduce the number of options on the dropdown list (currently 10 excluding ‘not specified’) to just the 6 open data licenses that meet the open definition requirements plus one category that allows governments to show their data licensed under an OGL or similar.

Reason is that 2929 activities are currently licensed under the license “OKD Compliant::Other (Attribution)” and there are several more ‘Other’ options.

Given that licenses are there for data users to check how the data is allowed to be used, having undefined/vague license information is not very useful.

And for civil society data providers it’s already hard to understand the difference between CC and ODC - throw in an option for ‘Other’ and they will go for that by default (to see what I mean, see the list of organisations using the “OKD Compliant::Other (Attribution)” option.

What do you think?

Also, what about having an element or attribute in the Standard which defines which open data license is attached to the data? For example as an attribute of iati-activities? Then the license is right there in the data, the same way you can embed a CC license in other open works.

I’m not a technical person so it may have been considered before and thrown out! @markbrough might know.

(Andy Lulham) #7

This is great – thanks @SJohns! I had no idea about the license page on the IATI dashboard – thanks for sharing!

Agree that undefined/vague license information is bad! If an “other” license is chosen, there would ideally be a way to specify it by linking to or embedding some license text. Fortunately, all 9 of the open licenses available in the Registry dropdown declare open definition compliance (see the “ OKD Compliant::” prefix in this list) so that’s definitely something.

I’m certainly in favour of pushing publishers towards choosing well-known open license options, such as the Creative Commons suite.

However, I think it could be a problem to remove the “other” open license options, because a publisher isn’t necessarily choosing the data license for the first time when they select it in the registry. They might be publishing some already-licensed data, so need a way to select the existing license.

(Petya Kangalova) #8

Thank you all for engaging in this really important conversation about licensing. In order to move things forward and action this, I propose the following step-by-step approach:

Step 1: Make the licensing field in the IATI Registry mandatory. We aim for this to happen in the next few weeks.

Step 2: We need an agreement on which types of licenses should be removed from the current list available on the IATI Registry. I propose the following and would really welcome views and discussion specifically on the ‘Other’ options and whether they should be kept or removed. If people can contribute by Friday 8th of March so that we can take a decision that will be much appreciated.

Remove the licenses below:

  • License not specified
  • Creative Commons Non-Commercial (Any)
  • Other (Non-Commercial)
  • Other (Not Open)

Discuss whether to remove the three licenses specified below:

  • Other (Open)
  • Other (Public Domain)
  • Other (Attribution)

Keep the below list:

  • Open Data Commons Public Domain Dedication and License (PDDL)
  • Open Data Commons Open Database License (ODbL)
  • Open Data Commons Attribution License
  • Creative Commons CCZero
  • Creative Commons Attribution
  • Creative Commons Attribution Share-Alike
  • GNU Free Documentation License
  • UK Open Government Licence (OGL)

Step 3: The technical team will investigate what are the options for those publishers who are not using an open license, working with our registry provider Derilinx. Possible options being either automatically defaulting to an open license OR having the option to keep them as is.

Step 4: Update the drop-down list on the IATI Registry (following agreement on Step 1). Then update the licensing guidance on the IATI website to reflect the changes made and provide more clarity. The guidance will be improved as suggested below.

Improve the licensing guidance on the IATI site so that it is (i) self-consistent and clear that IATI data is open data (see: the contradictory wording that @siemvaessen flags on discuss) and (ii) provides a bit more explanation of why e.g. non-commercial (or closed more generally) is problematic.

Then we will inform IATI publishers affected by the changes through email to advise them on the actions they should take. This will include a set deadline, which will be appropriate to the requests made.

Please comment on which licenses should be removed and kept by responding to this post by Friday 8th of March.

(Herman van Loon) #9

Thanks @petyakangalova for summarizing this thread in this very clear action list.

As pointed out by @SJohns above, the ''Other" category is rather vague and it is tempting to choose. My preference would be to exclude them from the list of acceptable licences.

Might it be an idea to summarize the main features of each license type on the IATI website so that new publishers can make an informed decision?

(SJohns) #10

Great summary and steps forward @petyakangalova - look forward to seeing what happens. The core list looks fine to me. The organisations I work with use CC in the main so I’m not sure of the use cases for the ‘other’ categories - other people will have more input I’m sure.

(Andy Lulham) #11

Yes, thanks @petyakangalova and everyone.

Re. Step 2: here are the lists of organisations using the “Other” open licenses:

Would probably be useful to contact some of the organisations on these lists (e.g. UNOPS; Sida; EC DEVCO to name three) just to get an understanding of their choice.

(Mark Brough) #12

Great to see this moving forward! 100% in favour of removing the first set (i.e. no longer allowing it to be selected, and encouraging publishers to re-select a compliant license).

I understand some of the “other” licenses can be country-specific variants of other CC licenses, e.g. similar to the UK Open Government License (which IIRC is more or less equivalent to CC-BY). I think several countries may have policies to use their own equivalents (e.g. France, Germany, USA), so might be worth checking with those publishers… But as @andylolz says, perhaps the fact that they have stated the license is OKD compliant is sufficient!

(Josh Stanley) #13

Hi all,

Just a note to say that an email will be going out this afternoon to our main contacts at all Orgs where their License type is one of the ‘others’; inviting them to join this discussion.

(Maria Mo) #14

Hi there and thanks for your mail Josh. Back in the day, we chose: OKD Compliant::Other (Attribution) as a license, because in 2011 there’s was less developed Creative Commons guidance.

We would be fine to change our licensing to ‘OKD Compliant::Creative Commons Attribution’.

The question from my side is: now that we know that we would like to change the licencing category, how would we best go about it? Is there an option to change the status ourselves or would the technical team need to change the settings for us?

Maria / UNOPS

(Josh Stanley) #15

Hi Maria,

Thanks for getting in touch.

You are able to change the License yourself by logging into the Registry and selecting OKD Compliant::Creative Commons Attribution from the License drop-down.

We are still working with the Registry’s hosts to ascertain our options with regard to publishers who do not change their license themselves in the coming weeks.

(Maria Mo) #16

Hi again and many thanks Josh,
Yes we looked for one on Friday already and again now, and we don’t seem to have a licence drop down - perhaps because our account is from 2011? This might be prompted now for new(er) accounts? Let me know if I should raise a ticket for this, just mentioning here, in case others have the same issue.

Best regards,

(Andy Lulham) #17

@MariaMO For UNOPS, it should be on this page: https://iatiregistry.org/publisher/edit/unops

The “License” dropdown ought to be the fifth field on the form.

In general, this page can be reached by:

  1. Logging into the Registry here
  2. Clicking My Publishers
  3. Clicking on the name of the relevant publisher in the table
  4. Clicking the :wrench: Manage button

I guess the important bit to note is that the license is set for the publisher, not for the individual dataset(s).

Hope that helps.

(Maria Mo) #18

Thank you @andylolz Could not have done it without you. We are live now with the new licence category.

What we noticed was that after updating, our user description changed to “First published date: 29 August 2018” which is of course incorrect, as the original date was September 2011. If there is a way to correct, so let us know. Flagging this again just in case happens also to others.

(Amy Silcock) #19

Thanks for flagging @MariaMO! I’ve raised the issue with our Registry supplier for them to look into. You/we can reset the date in the same page where you choose a license.

(Assem Kassim) #20

Hi Andy

The above points sound good and I don’t have an issue with them. I just need to somehow review the licence for our organisation.