mde-shacl

Generate SHACL shapes and validate RDF data against ontology layers.

5|Updated Mar 21, 2021
One-click install
npx skills add https://github.com/salaroglio/MdExplorer --skill mde-shacl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mde-shacl
Source: https://github.com/salaroglio/MdExplorer/tree/main/MdExplorer/skills/mde-shacl
Command: npx skills add https://github.com/salaroglio/MdExplorer --skill mde-shacl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SHACL shapes provide a formal way to constrain RDF data according to your ontology, enabling automated validation and governance of datasets within MdExplorer projects.

Core Features & Use Cases

  • Generate <layer-name>.shapes.ttl and <layer-name>.shapes.md for a given ontology layer.
  • Define NodeShape and PropertyShape constraints (cardinality, enums, datatype) and complex invariants.
  • Load shapes into Apache Jena Fuseki and run SHACL validation against ABox data to ensure data quality and conformance.

Quick Start

Create and load SHACL shapes for your ontology and validate a dataset using Fuseki.

Frequently Asked Questions about mde-shacl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are SHACL shapes and how do they enforce RDF data quality?

SHACL shapes are formal constraints applied to RDF data according to an ontology, enabling automated validation and governance. They define NodeShape and PropertyShape rules like cardinality, enums, and datatypes to ensure dataset consistency and conformance.

How do I generate and load SHACL shapes to validate RDF data in Apache Jena Fuseki?

To validate RDF data, generate layer-specific .shapes.ttl and .shapes.md files from your ontology, then load them into Apache Jena Fuseki. A runnable PowerShell script executes the loading process and runs SHACL validation against your ABox data.

Do I need a specific ontology structure to run SHACL validation?

Yes, SHACL validation requires a properly organized ontology structure. You need an ontology directory with layer TTLs and a companion .shapes.md file for each layer to define the constraints correctly before validation.

What types of constraints can I define using SHACL for ontology development?

SHACL allows you to define NodeShape and PropertyShape constraints for ontology development. You can specify cardinality, enums, datatypes, and complex invariants to govern your RDF datasets and ensure data quality.

Can I use this for data-governance workflows with layered ontologies?

Yes, this approach applies directly to data-governance workflows. It produces SHACL shapes for each layer of your ontology and validates them against ABox data using Fuseki and SHACL tooling to enforce consistency.

Why is my SHACL validation not working against the ABox data?

SHACL validation fails when the ontology is not properly organized under the required directory structure. Ensure layer TTLs and companion .shapes.md files exist, and that the PowerShell script correctly loads the shapes into Fuseki before running validation.