(Duplicate with #293) Change prefixes of notice types from epo: to epo-not:

[csnyulas]

Our mappings (both CM and TM) refer to epo:ResultNotice, epo:CompetitionNotice and other notice types. In EPO, the various notice types have the epo-not:, not the epo: prefix. We should align the conceptual and technical mappings to use the prefixes declared in EPO.

Although this seems simple and straightforward, there is a risk that if we introduce the epo-not: prefix into our mappings, the RMLMapper (or some other library that is used create the Turtle serialization), will replace all epo: prefixes (for all classes and properties) with epo-not:, since they both resolve to the same namespace, and hence, even with the current notation, no validation checks are failing. The problem is that in case of overlapping namespaces some library in the RML transformation pipeline randomly (or at least without any apparent logic) chooses one of the prefixes to abbreviate class and property names.

[muricna]

This is covered by issue #293

[csnyulas]

Besides the classes, also the property prefixes (such as for announcesRole, refersToRole, hasLegalBasis, etc.) should be updated.

To find all property (and class) names with epo-not: prefix you can consult the EPO glossary:

[valexande]

Duplicate with #293