From e60e4f4ecfdccedf738fdeb9623af92897edacd8 Mon Sep 17 00:00:00 2001 From: "@s.roertgen" Date: Thu, 18 Apr 2024 10:38:52 +0200 Subject: [PATCH] Be clearer about target audience and the used shape #40 #36 --- content/blog/2024-04-18-shacl-validation/index.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/blog/2024-04-18-shacl-validation/index.md b/content/blog/2024-04-18-shacl-validation/index.md index 85ee6fa..c6961a6 100644 --- a/content/blog/2024-04-18-shacl-validation/index.md +++ b/content/blog/2024-04-18-shacl-validation/index.md @@ -11,9 +11,13 @@ authors: [{lastname: "Rörtgen", ## How to add automatic SHACL validation to your vocabs -To ensure the quality of your vocabularies, you might want to add some automatic validation, just like one is able to run automatic software tests before a merge request. -Such a validation step can easily be set up with the SHACL shapes in the [SkoHub Shapes repository](https://github.com/skohub-io/shapes). +If you are using SkoHub to publish your vocabularies, we want to show you an easy solution to add some validation to your vocabulary repository to ensure the quality of your vocabularies. +You can also use this approach, if you are not using SkoHub, but still want to ensure some basic constraints that we set up in the [`skohub.shacl.ttl`](https://github.com/skohub-io/shapes/blob/main/skohub.shacl.ttl) shape, e.g. that every `skos:Concept` should have at least one `skos:prefLabel` (which is not required by the SKOS Reference). +Feel free to read the shape file. +The `sh:message`s should give you a good explanation of what is tested with this shape. +The `sh:severity` attribute shows you if the contraint will give a warning or a violation. +Such a validation step can easily be set up with the SkoHub SHACL shape in the [SkoHub Shapes repository](https://github.com/skohub-io/shapes). All you have to do is adding the [following GitHub Action config](https://github.com/skohub-io/shapes/?tab=readme-ov-file#add-validation-in-a-vocabulary-repository) to your vocabularies. In the `.github/workflows/main.yaml` file, add the following steps: