trr379/annotate-trr379-demo
8
0
Fork 0
Code Issues 24 Pull requests Packages Activity

Implement a workflow for sh:PropertyGroup declaration and conversion to SHACL #12

New issue
Open
opened 2025-02-01 21:45:17 +00:00 by jsheunis · 0 comments
jsheunis commented 2025-02-01 21:45:17 +00:00 (Migrated from hub.datalad.org)
Copy link

github.com/psychoinformatics-de/datalad-concepts@625ff16ecf starts adding annotations to the slots in the dlthings schema in order to drive UI presentation on the shacl-vue side. This is one necessary input to the workflow. Another, currently missing piece, is defining the same sh:PropertyGroups that are used in the annotations, and then converting that to SHACL and feeding it to a shacl-vue deployment.

There are a few existing parts of the solution that I have used previously:

  1. a property group schema, current latest version at https://hub.datalad.org/datalink/tools/src/branch/main/schemas/property_group_schema.yaml, and also an old-ish PR at https://github.com/psychoinformatics-de/datalad-concepts/pull/199. This schema can be used to validate incoming property group declarations.
  2. a data file used to declare property groups that are used in dlschema schemas. Here's an example: https://hub.datalad.org/datalink/tools/src/branch/main/data/dlco-shacl-groups.yaml
  3. code that is used for property group validation and then conversion to SHACL and merging with the SHACL export of an actual schema, here's an example: https://hub.datalad.org/datalink/tools/src/branch/main/code/gen_shacl_ui.py

We need to decide how/where to implement this.

https://github.com/psychoinformatics-de/datalad-concepts/commit/625ff16ecf89ece4ff926eb25f28df2e5ae5a0dd starts adding annotations to the slots in the `dlthings` schema in order to drive UI presentation on the `shacl-vue` side. This is one necessary input to the workflow. Another, currently missing piece, is defining the same `sh:PropertyGroup`s that are used in the annotations, and then converting that to SHACL and feeding it to a `shacl-vue` deployment. There are a few existing parts of the solution that I have used previously: 1. a property group schema, current latest version at https://hub.datalad.org/datalink/tools/src/branch/main/schemas/property_group_schema.yaml, and also an old-ish PR at https://github.com/psychoinformatics-de/datalad-concepts/pull/199. This schema can be used to validate incoming property group declarations. 2. a data file used to declare property groups that are used in `dlschema` schemas. Here's an example: https://hub.datalad.org/datalink/tools/src/branch/main/data/dlco-shacl-groups.yaml 3. code that is used for property group validation and then conversion to SHACL and merging with the SHACL export of an actual schema, here's an example: https://hub.datalad.org/datalink/tools/src/branch/main/code/gen_shacl_ui.py We need to decide how/where to implement this.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
bnr
submission-ux
submission-wip
service-integration
infinite-fixes
updates
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
trr379/annotate-trr379-demo#12
No description provided.