Closed HadleyKing closed 10 months ago
@stain Any thoughts on this? Just pinning you to see what you think.
Hi, should probably not expose private emails (!)
The Data Use Ontology is quite relevant to BioCompute Object domains, see terms
For pure dataset licensing, in RO-Crate licensing we keep it at a lighter schema.org level, e.g. just linking to CC-BY license.
https://spdx.org/specifications has more terms for software licenses and have identifiers for "all" the open source ones, but not so good for usage restrictions which I think is what is being referred to here.
There is also https://www.w3.org/TR/vocab-duv/ which is nowhere near as extensive as DUO, rather more structural. https://www.w3.org/TR/odrl-vocab/ is another usage thing.
As a BioCompute Object necessarily consists of multiple things (e.g. dataset, workflow, settings, metadata) I think it could be tricky to pick a single license or usage restriction, but rather this should be described at container level (RO-Crate) but adding in DUO where needed. It might be a challenge exactly on how to link it in, but it should be possible as you can expand the crate with other vocabularies.
Can we see I'd DUO should be connected to BioCompute?
DUO is slightly out of scope, or possibly a subset, for the kind of modeling that would need to be done to better understand licensing interactions. DUO, at this point, seems to be more about how to model single steps in sensitive data.