We should be able to have this demand-registry published at https://lab.fair-ease.eu/dataset-demand-registry/
I propose to create some github action that could
- provide some central main registry.ttl for the registry as a whole (maybe cold just be a static stub)
- copy the nested registry/**ttl files while probably cleaning/ tuning some boilerplate stuff as
- injecting their relation <> schema:includedInDataCatalog into those
- ensuring correct @base
not to overdo automating in the beginning -- let us just create these files by hand for now, have them copied through gh-pages and later document what automation opportunities we actually see?
We should be able to have this demand-registry published at https://lab.fair-ease.eu/dataset-demand-registry/
I propose to create some github action that could
not to overdo automating in the beginning -- let us just create these files by hand for now, have them copied through gh-pages and later document what automation opportunities we actually see?