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

Query regarding model licensing #444

Open
ThibautGoldsborough opened this issue Dec 13, 2024 · 2 comments
Open

Query regarding model licensing #444

ThibautGoldsborough opened this issue Dec 13, 2024 · 2 comments

Comments

@ThibautGoldsborough
Copy link

Hello,

Please feel free to redirect me to the Image.sc forum if this is not the right place to discuss about licensing.

We are in the process of uploading a number of instanseg models and had a query regarding the licensing of our models. The instanseg method is released under Apache-2.0, however the weights were trained on a number of datasets, each with their own licensing terms. So far we have kept to CC-BY or CC-0 datasets as these are compatible under the Apache-2.0 terms. But we'd like to release more models trained on less permissive licences (e.g. cellpose dataset, tissuenet dataset, livecell dataset), which have confusing strictly non-commercial custom licenses (cellpose and tissuenet).

I noticed that some of the popular models hosted on bioimageio (e.g. https://bioimage.io/#/?id=10.5281%2Fzenodo.5869899&type=model) were released under a fully open license (CC-BY-4.0) yet the training data (livecell) is released under a more restrictive CC-BY-NC. Does bioimageio assume that the license of a model is not tied to the license of the training dataset?

I'm aware this is not your direct responsibility, but there seems to be a lack of guidelines for model developers which could lead to unintended downstream risks for model users.

@FynnBe
Copy link
Member

FynnBe commented Dec 13, 2024

Thank you @ThibautGoldsborough for raising this issue.
It is my current understanding that the license of an RDF applies to the metadata it holds only.
I will forward this to our weekly discussions and report back here (and hopefully update the documentation to make this clear(er)).

@FynnBe
Copy link
Member

FynnBe commented Dec 20, 2024

short update: we did not find time to discuss this this week and take a holiday break until January...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants