Step 5. Implementation

status: in development

Short description

Meaning a couple of things:

Generating and testing the SHACLs from the semantic model
Harmonization with other petals and/or core (if some other domains use same/similar concepts > try to agree; if quite some domains come up with the same concept > move to core)
Update CKAN with the new metadata
Update catalogue frontend with new metadata, filters, etc.
Test with test data

This may not be part of the schema development process, but is important to make it work in the catalogue.

Shape file(s) in Github

SHACL rules documentation

Input: Conceptual model.

Process: Create the formal model in RDF/shacl/ owl using the preferred tooling (see Possible Tooling below).

In this step the URI namespace, prefix, imported modules and conventions must be discussed with the domain experts and implementation group.  

Who is involved: Metadata semantic specialist and implementation team.

Output: The formal model in OWL/rdfs/ shacl 

This artefact needs to be pushed to git.

Versioning must be defined.

Tool	Description
RDF editors	(Web)Protégé, TopBraid Composer, RDF4J Workbench, rdflib
SHACL tools	SHACL Play! (sparna.fr)
SHACL validation	SHACL validator