Make overriding ("inheritance") of properties more explicit about ro-crate HOT 4 OPEN

If we agree we allow some implicit properties like creator and license to apply to a research object folder "root folder" (?) or on a directory, then yes, we should agree:

1. Which provenance/license properties re-apply recursively?
2. Do these properties re-apply also to sub-sub-folders?
3. What is the order of overriding? (intuitively the most specific path should win)
4. What kind of tooling should do this inference to "complete" the RO?
5. Does such properties also apply to "external" resources outside the "root"?
6. Do we need to define the research object "root folder"? (e.g. fix the location of manifest.jsonld)

from ro-crate.

A bit of added complexity here. The Root RO-Crate Dataset should use creator etc as properties pointing to well described contextual entities with a URI (as per DataCrate but for individual files creator is going to be better expressed using provenance via CreateEvent. But yes we should make some statements about what is inherited. But I think machine reasoning about RO-Crate of un-trusted provenance would be risky.

from ro-crate.

See approach to inheritance from the Psych-DS spec

from ro-crate.

dc35042 expands a bit on license recursiveness, but not for folders.

from ro-crate.