No description
- Makefile 79.1%
- Shell 20.9%
Stephan Heunis
a962056358
This is in response to inm7/annotate.inm7.de-users#18 A recent update to shacl-vue stated that, for a rendered form, a property should be divided into the class group that either made the latest change to it if it was inherited, or into the class that introduced the property. But it seems this update did not foresee the situation where both an original and inheriting class have properties annotated with the exact same sh:order. This causes a given property to be placed, incorrectly, in what is determined, correctly, to be the originating class. This stems from the fact that there is no machine-actionable knowledge about annotation inheritance in the shacl that is exported from a linkml schema. The only way of knowing this, in the current approach, is if the property changes. This is what we are doing with this commit, by changing the annotation. This is done because of the absence of a better solution at the current time. |
||
|---|---|---|
| .forgejo/workflows | ||
| extra-docs | ||
| patches | ||
| src | ||
| tools | ||
| .codespellrc | ||
| .gitignore | ||
| .linkmllint.yaml | ||
| LICENSE | ||
| Makefile | ||
| mkdocs.yml | ||
| pyproject.toml | ||
| README.md | ||
INM-7 metadata model
WORK IN PROGRESS
How to...
Install (in a virtualenv)
pip install -r requirements.txt
Build docs:
make
Serve docs locally
mkdocs serve
Presently, this work require a patched linkml installation. The patch(es) are
listed in patches/. The script tools/patch_linkml documents how they need
to be applied. This script can be used to patch a local installation, and is
also executed in the actions that validate the included data models.
Acknowledgements
This work was funded by
- MKW-NRW: Ministerium für Kultur und Wissenschaft des Landes Nordrhein-Westfalen under the Kooperationsplattformen 2022 program, grant number: KP22-106A