Add workflow for generating up-to-date schemas and data #90
Labels
No labels
bug
config
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
orinoco/shacl-vue#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For the demo
shacl-vuesite, the config uses schemas generated from datalad concepts, from locally served files e.g. https://github.com/psychoinformatics-de/shacl-vue/blob/main/public/dlschemas_data.ttl.The config also allows specifying a remote file URL, which is the case for e.g. the TRR379 deployment, but in those cases we control the hosting of the schemas and can allow specific origins to get around CORS issues. With the github hosting of concepts.datalad.org, we cant. So we need an alternative setup to be able to fetch or generate these files. This includes the shacl, owl, and sample data.
Current idea is to do the same as for the other concepts deployments where we have a linkml schema that imports schemas from dlconcepts and then from that we can generate the shacl and owl. For data, we will need to run the code to generate examples in ttl format, and then merge those into a file that shacl-vue can read.
We can lean heavily on the existing work in https://hub.psychoinformatics.de/inm7/inm7-concepts/src/branch/main/src/base/unreleased.yaml and https://hub.psychoinformatics.de/inm7/inm7-concepts/src/branch/main/Makefile