T2: Export of controlled vocabulary restrictions

[rousso]

This task aims to enforce the use of controlled vocabularies within the Semantic Data Specification, ensuring that all enumerations and associated classes in the Conceptual Model are accurately represented in OWL and SHACL shapes, thereby maintaining data consistency and integrity.
The implementer is expected to:

• Identify suitable representations for vocabulary restrictions: Define how these vocabulary restrictions are modelled in both SHACL and OWL. Provide examples of alternatives, such as sh:in to declare allowed values or sh:inScheme for a SKOS scheme.
• Implement export restrictions on vocabularies: Implement the export of controlled vocabulary restrictions into the OWL and SHACL artefacts using the defined representations.
• Demonstrate restrictions on vocabularies in practice: Create a Jupyter notebook that shows how the vocabulary restrictions are used while validating data or proposing values for a property.
• Document controlled vocabularies validation strategies: Develop and provide of examples of RDF validation approaches that enforce controlled vocabulary restrictions. The documentation should consider edge cases, such as deprecated vocabulary terms, SKOS statuses (i.e euvoc:status other than at:CURRENT), hierarchical term relations (broader/narrower terms), discussing the advantages and disadvantages of each approach in the context of ePO and the use of Named Authority Lists (NAL).

Note

This ticket replaces model2owl#192