OP-TED / ePO

The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.

European Union Public License 1.2

58 stars 18 forks source link

Wrong datatype for Notice `hasEFormsSubtype` #554

Closed schivmeister closed 2 months ago

schivmeister commented 7 months ago

Issue

An epo:Notice currently has the attribute (datatype property) epo:hasEFormsSubtype whose value range is xsd:integer.

If the attribute is meant to represent a value from the notice-subtype vocabulary, the datatype is wrong, as the vocabulary also has string values:

CEI 
E1  
E2  
E3
E4
E5
T01
T02
X01
X02

Recommendation

The value range for epo:hasEFormsSubtype shall be xsd:string.

andreea-pasare commented 7 months ago

The epo:hasEFormsSubtype is to be removed in ePO v5.0.0. This will tracked under a separate issue.

This attribute was an oversight on ePO's side. The classes to be used instead are in the eNotice module:

Regarding the second part of the ticket, the string code values mentioned are not used in the Competition Notices. They will be added before their mappings are required.

andreea-pasare commented 2 months ago

Implemented the following notice subtypes in ePO:

X01 and X02 notice subtypes were not implemented since they are not used in public procurement.