Closed VladimirAlexiev closed 1 year ago
Your concerns are justified and will be addressed when we adopt reification in the next version. Our initial workings on reification are depicted below:
The workings can be consulted at : https://github.com/eprocurementontology/eprocurementontology/blob/v2.0.2/v2.0.2/05-Implementation/test/roles-as-classes/ePO-CM-roles-as-classes.eap
hasContext points to Procedure, Tender, Contract etc?
This is the general pattern and it can point to different contexts according to the different procurement situations. The idea here is that to avoid the mix of semantic concepts between roles (that are not agents) and agents and to create the conditions to say that in a specific procurement situation (in a specific context and during a certain period) agents play some roles
As of 3.0.1 we have two relations from epo:Procedure to epo:Buyer now:
@costezki can you point to the relevant diagrams once 3.0.1 is published? I want to recheck all bullets that I raised.
@VladimirAlexiev, the diagrams for ePO 3.0.1 are available at the following link: https://docs.ted.europa.eu/EPO/3.0.1/ePO-core-Conceptual-Model-v3.0.1.html.
The name
Role
suggests, and examining it in the conceptual model https://eprocurementontology.github.io/v2.0.2/index.html?goto=1:43 confirms, that it must be relative to some tendering procedure. Eg its subclassEconomicOperator
has а key fieldhasEORoleType
and its valuesSOLE contractor
vsLead Entity
are relative (the same legal entity can have different role types in different Procedures).But I have the following concerns:
Role
toProcedure
is too low in the subclasses ofRole
and is specific to the subclass, egBuyer->isResponsibleFor->Procedure
Tenderer->submits->Tender->includes->TenderLot->relatesTo->Lot->isSpecifiedIn->Procedure
hasEconomicOpratorSize
are independent of particular Procedures (although are dependent on time), so is it right to have them in a subclass ofRole
?