Some last changes (#36)

skohub-io · Apr 18, 2024 · b8ab4f9 · b8ab4f9
1 parent e60e4f4
commit b8ab4f9
Showing 1 changed file with 4 additions and 5 deletions.
diff --git a/content/blog/2024-04-18-shacl-validation/index.md b/content/blog/2024-04-18-shacl-validation/index.md
@@ -13,11 +13,10 @@ authors: [{lastname: "Rörtgen",
 
 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).
+Feel free to study 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.
+
+The automatic 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:
 
@@ -73,7 +72,7 @@ jobs:
 ```
 
 This will activate checks for violations and warnings of the [SkoHub SHACL Shape](https://github.com/skohub-io/shapes/blob/main/skohub.shacl.ttl).
-These checks will also automatically run before each merge request.
+These checks will also automatically run in the context of a merge request.
 Unfortunatley you will also get a *red* error message for warnings, e.g. if you have no license provided in your vocabulary.
 This is due to the fact that Actions either complete or fail and we have no way to indicate a "warning" message.