Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

German open data license v2 #49

Closed
rufuspollock opened this issue Aug 22, 2014 · 4 comments
Closed

German open data license v2 #49

rufuspollock opened this issue Aug 22, 2014 · 4 comments

Comments

@rufuspollock
Copy link
Member

Here are the DRAFT German open data license v2.0

Data licence Germany - Zero - Version 2.0
https://docs.google.com/document/d/1RqQqkCt7t9yO5YMrRsXEMnoS5cCDzUtbDf-tN0Upq1A/edit#

Data license Germany - attribution - Version 2.0
https://docs.google.com/document/d/1z8aKuEoyPw_T_LZNBTH1O_ZSJCta9N1YgWSiX5zXzw4/edit#

and here are the answers to the questions as provided by the Federal German Ministry of the Interior (BMI):

I. State the rationale for the new license.

The “data licence Germany” focusses on public sector data which is provided under German public law. Without the “data licence Germany”, German administration would not have a proper way to define Open-Definition-compatible terms of use for their data, as it is still controversial discussed if civil-law-based licences like Creative Commons may be used by the federal administration and especially for data.

II. Is the license specific to an organization/place/jurisdiction? We generally frown on such licenses (see proliferation below), only making politically expedient exceptions (eg, the organization is a national government; and these are categorized as “non-reusable).

cf. answer I: The “data licence Germany” is developed especially for public sector data in Germany (like the the Canadian or British Open Government Licences). A categorization as “non-reusable” is acceptable for us.

III. Compare and contrast to any existing similar approved as OD-conformant licenses.

The “Data licence Germany” is available in two variations: The “Data licence Germany - Attribution” demands an indication of the data source (like CC-by). The “Data licence Germany - Zero” doesn’t impose any restrictions (like CC-Zero). As stated in answer 1, both version were developed to be comparable to Creative Commons, but within the restrictions of German public law.

IV. What benefit does the new license bring over already approved OD-conformant licenses which would outweigh the costs of license proliferation?

cf. answers I and III.

V. Is the license compatible with existing OD-conformant licenses?

By alignment (permissions identical or a superset of existing license, conditions identical or a subset) and/or express permission to license the original and/or adaptations of the licensed work under an existing license?

Yes. Both variations of the licence do not define any constraints regarding the reuse of data under the “Data licence Germany” – with the exception of attributing the author in case of the “Date licence Germany – Attribution” .

VI. Provide a link to any public drafting process (e.g., conducted on a public communication forum of some sort; multiple drafts presented to that forum) for the license.
The licence was discussed and drafted in an (off-line) working group, led by the Federal Ministry of the Interior and with members from federal states as well as from civil society organisations like Wikimedia and OKF. Internet-based platforms were not used in this process, so that a link cannot be provided.

Please note that I was asked by the BMI to solicit the advisory board for comments on the licenses (which Mike, Herb and Andrew already did) and to submit the license for approval as an open license on compliance with the OD.

@ddie
Copy link
Member

ddie commented Aug 24, 2014

The major difference of the German Data license compared to other licenses is that it is based on “German Public Law” rather than “German Private Law”, see https://en.wikipedia.org/wiki/Law_of_Germany

This means that it the “license” is actually more a “dedication”, much the way a government dedicates the use of roads to the public. From my understanding intellectual property legislation is based in private law in most judiciaries. However I have not enough legal expertise to fully understand possible consequences.

I have personally invested a lot of time to convince the German government to use a well established open license (such as CC-0 or CC-BY) rather than creating a national license for well known reasons of license proliferation. I was not successful, however. The main reason for the creation of the national license is the perception that a national license has a bigger chance to be widely accepted by government bodies here in Germany.

So in a nutshell my view on the strengths and weaknesses are:

a. it was not a good idea in the first place to create the license
b. it is intended to be a permissive open license
c. its very light wight and short
d. we don’t fully understand the consequences of the fact that the license is based on “German Public Law” rather than “German Private Law”

@enyst
Copy link
Contributor

enyst commented Aug 24, 2014

On the mailing list Mike asked:

I enjoy the brevity, and dropping NC/adding 0 a great thing.
a) Does the brevity cause any required permissions to not be granted? I
hope the answer is "no" but seems worth a closer look.

I made a quick comparison with ODbL, CC-BY 4.0, and, more closely, European Directive 96/9/EC on databases. My personal conclusion is that the permission grant of German-data licenses is a nice piece of writing that conveys to the reader the intended meaning pretty well, along with the necessary rights. I think brevity and readability are underrated qualities of a legal text, and FWIW I'm glad to see this work.

I'd note a few differences, in case you may have another opinion on their relevance. (my personal opinion is they don't matter, but IANAL and have no knowledge on German law)

  1. The European Directive mentioned above states "in whole or in part". This expression is quite widespread, and is missing here. But I don't see how I can claim that any use was permitted, in particular to be altered and processed, but not cut parts of or something. I'd say the text doesn't reasonably support the opposite interpretation.

  2. The directive also contains "translation, adaptation, arrangement and any other alteration". Here I wondered if it would be better to give the rights to translate or adapt explicitly. But I doubt it's necessary, "any use [..] in particular" includes logically translation and adaptation, and also, from another perspective, the text of the directive itself says that translation, adaptation, arrangement are only a few 'kinds of' alteration. Alteration is explicitly covered in German Data licenses. ODbL enumerates translation and adaptation as kinds of alterations.

All the rest of permissions seem even more neatly covered, than these two details I stopped to.

Actually, my whole reading of the entire text of the licenses is the same with the reading mentioned already in the mailing list thread (so arguably the above attempted nitpicking was redundant): "any use [..], commercial and non-commercial, in particular [relevant examples]". This wording should cover logically any applicable right.

Just my two cents..

@mlinksva
Copy link
Contributor

Thanks @enyst for those reassuring two eurocents...

I'm still a bit curious about what makes the licenses operate under public rather than private law. It was pointed out to me offline that the previous draft contained language that maybe hints at this, roughly "data provider makes the data, content and services available in fulfilling its public missions" and could be construed as imposing license conditions irrespective of whether copyright or anything similar applies (IIUC). But such language is not present in the revision, and with only BY and 0 licenses available, it is hard to see as much of an attempt at unilateral imposition of conditions. But then I'm still left wondering how the current proposal operates under public rather than private law. :) I don't know that such curiosity should hold up putting up for approval.

@mlinksva
Copy link
Contributor

mlinksva commented Oct 2, 2014

These were approved and have been added to /licenses

@mlinksva mlinksva closed this as completed Oct 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants