You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be pretty straight forward. The ODRL file will be formatted in JSON-LD and the top-level object will be a policy (i.e. a collection of rules). We could reference this ODRL part from the RO-Crate root dataset through the hasPolicy property.
I'm not sure if this is the right place to discuss this (probably rather here), but what is the advantage over simple license files? This might be a very basic question, I am not an expert on this topic. Can you elaborate on this, @HLWeil?
Regarding the technical part, I don't see a big issue here. I'm not a big fan of making the investigation a Policy, but I'm also not strictly opposed to it. It seems counterintuitive. It could simply be a lack of understanding from my side of the specific interpretation of the term policy though. However, I would argue that the diagram is a slight misrepresentation. Should the ODRL policy really be on the same level of "importance" as studies, assays or workdlows?
Parallel to the plans of including an ODRL file in the ARC Scaffold, there should also be an alternative part in the ARC RO-Crate.
This should be pretty straight forward. The ODRL file will be formatted in
JSON-LD
and the top-level object will be a policy (i.e. a collection of rules). We could reference this ODRL part from the RO-Crate root dataset through the hasPolicy property.The text was updated successfully, but these errors were encountered: