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

Licensing #1139

Closed
dhimmel opened this issue Aug 29, 2015 · 4 comments
Closed

Licensing #1139

dhimmel opened this issue Aug 29, 2015 · 4 comments
Labels
autoclosed-unfixed This issue has been closed automatically.

Comments

@dhimmel
Copy link

dhimmel commented Aug 29, 2015

I don't see a license for Uberon. Since no license defaults to 'all rights reserved', the lack of a license is troubling for reuse. For example, the issue came up for my own project.

If the goal is to create an open resource, I suggest the CC0 (public domain) license. GO uses the CC-BY (attribution) license, but even attribution can be a burdensome stipulation. For example, attribution stacking is problematic and any requirements can discourage reuse.

@uberon
Copy link

uberon commented Aug 29, 2015

Likely to be cc by. Perhaps it is possible to license specific subsets as
cc 0 on an as needed basis. Eg deposition in bias. There are Obo guidelines
that take pains to avoid overburdening attribution. Will post later

On Saturday, August 29, 2015, Daniel Himmelstein [email protected]
wrote:

I don't see a license for Uberon. Since no license defaults
http:https://choosealicense.com/no-license/ to 'all rights reserved', the
lack of a license is troubling for reuse. For example, the issue came up
http:https://thinklab.com/discussion/integrating-resources-with-disparate-licensing-into-an-open-network/107#3
for my own project.

If the goal is to create an open resource, I suggest the CC0
https://creativecommons.org/publicdomain/zero/1.0/ (public domain)
license. GO uses the CC-BY http:https://creativecommons.org/licenses/by/4.0/
(attribution) license, but even attribution can be a burdensome
stipulation. For example, attribution stacking
http:https://wir.okfn.org/2012/01/27/attribution-stacking-as-a-barrier-to-reuse/
is problematic and any requirements can discourage reuse
http:https://opendata.stackexchange.com/a/39/8345.


Reply to this email directly or view it on GitHub
#1139.

@cmungall
Copy link
Member

@dhimmel
Copy link
Author

dhimmel commented Aug 30, 2015

Ah, I see the following line in the OBO, so it looks like Uberon is currently CC-BY 3.0.

property_value: dc-rights http:https://creativecommons.org/licenses/by/3.0/

It may make sense to switch to CC-BY 4.0.

So the preferred method of attribution is through the Internationalized Resource Identifiers (IRIs)? For example:

http:https://purl.obolibrary.org/obo/UBERON_0000209

@gouttegd
Copy link
Collaborator

gouttegd commented Aug 3, 2021

WARNING: This issue has been automatically closed because it has not been updated in more than 3 years. Please re-open it if you still need this to be addressed addressed addressed – we are now getting some resources to deal with such issues.

@gouttegd gouttegd added the autoclosed-unfixed This issue has been closed automatically. label Aug 3, 2021
@gouttegd gouttegd closed this as completed Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autoclosed-unfixed This issue has been closed automatically.
Projects
None yet
Development

No branches or pull requests

4 participants