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

License Needed in Investigation for Valid RO-Crate #70

Closed
floWetzels opened this issue Jan 21, 2025 · 2 comments
Closed

License Needed in Investigation for Valid RO-Crate #70

floWetzels opened this issue Jan 21, 2025 · 2 comments
Labels
Status: Needs Triage This item is up for investigation.

Comments

@floWetzels
Copy link

Since the RO-Crate specificiation requires a license field to be specified in the root data entity (Investigation object in our case), it makes sense to validate for an existing license (via gitlab or a license file) before running the RO-Crate export. Therefore, @HLWeil and I think that such a test should be added to the validation.

Related to nfdi4plants/ARCtrl#472

@github-actions github-actions bot added the Status: Needs Triage This item is up for investigation. label Jan 21, 2025
@kMutagene
Copy link
Member

I think this is a potential sensitive issue as we have heard time and time again that people are unsure whether and under what conditions they want to share data.

This is for sure easy to validate for "publishable" ARCs though, as they are intended to be accessible anyways.

However, I think making a license mandatory in "baseline" ARC validation sends the wrong signal. The ARC evolves over time, and at one point users might choose a license, but i do not think we should tell them that the ARC is invalid before that. Can this maybe be circumvented by adding a "all rights reserved" kind of license per default on export? In any case, this must be first well defined in the ARC specification and also be communicated well ahead of implementation.

cc @HLWeil @muehlhaus @Brilator

@Brilator
Copy link
Member

Does it make a license mandatory though or is it possible to validate License == None?

I agree with @kMutagene, that it might send false signals as changing a license might not be easy / legally correct. E.g. adding CC-BY by default and at some point deciding to patent the content.

@nfdi4plants nfdi4plants locked and limited conversation to collaborators Feb 11, 2025
@kMutagene kMutagene converted this issue into a discussion Feb 11, 2025
@github-project-automation github-project-automation bot moved this to Done in ARCStack Feb 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Status: Needs Triage This item is up for investigation.
Projects
Status: Done
Development

No branches or pull requests

3 participants