model2owl requirements for ePO

[AchillesDougalis]

Proposed tasks for model2owl maintenance from the ePO perspective.

• [ ] Remove references to code lists that are not yet implemented
• [ ] Cross-module class connectors (inheritance, association, dependency
• [ ] Check that the URIs follow best-practices (RDF linter)
• [ ] Implement Tags management to enable custom properties (e.g. definitions, usage notes, alternative labels, etc.)
• [ ] Remove duplicated imports
• [ ] Diffing RDF artefacts (OWL & SHACL) to bootstrap release notes
• [ ] General maintenance of the model2owl repository.
• [ ] Regular maintenance for bug fixing and minor improvements
• [ ] Maintenance of deprecated URIs
• [ ] Modified original definitions
• [ ] Add Class Generalization in Glossary
• [ ] Duplication of epo Terms in the combined glossary
• [ ] Duplication on definitions of the glossaries
• [ ] Filter using Class Status when generating OWL
• [ ] SHACL - Missing predicates for ESPDRequest
• [ ] SHACL - Missing predicate for CertificateInformation
• [ ] Restriction on controlled vocabularies

[cristianvasquez]

Another requirement:

Instead of generating SHACL with:

sh:datatype rdf:PlainLiteral ;

Produce:

sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ;

related issue: https://github.com/OP-TED/ted-rdf-mapping-eforms/issues/14