search

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

clarification for award decision and subcontract #264

Closed giorgialodi closed 2 years ago

giorgialodi commented 3 years ago

Could you please clarify which are the relationships between award decision and subcontract? There are many and very general and from my point of view do not make any sense to have so many generic properties between the two concepts.

In the eAward diagram available via html of version 2.0.2 (I am using this because the html version of the diagrams for 2.0.1 is no longer available for issue #259 ) I can see at least these three properties:

In the OWL restriction file of version 2.0.1 that we should use in the BDTI pilot it is not clear which are the restrictions that apply.

Which one should I use? has between AwardDecision and Subcontract? In addition, I remember that the usage controlled vocabulary was utilized at least in version 2.0.2 (not in version 2.0.1) in order to define whether subcontracting was used or not. Am I right? I no longer see it.

In a ANAC's dataset we have a flag (true or false) in order to indicate whether a subcontracting is used or not. How can I model this with the properties above for Award Decision and Subcontract? BTW: the Subcontract is a Contract? Because in the definition seems like this but it is not declared as subClassOf Contract in the model.

paulakeen commented 3 years ago

Resolved via establishing the links "epo:Lot epo:isRelatedTo epo:TenderLot, epo:TenderLot epo:proposes epo:Subcontract".

Any relationship between AwardDecision and Subcontract need to be reviewed at a later time and removed if unnecessary to avoid confusions.

andreea-pasare commented 2 years ago

ePO 3.0.1 does not have a Subcontract concept. According to WG meeting from 15/02/2022, Subcontract class is deleted because current forms and eForms do not require it, but it can be reintroduced if a use case is provided at a later stage.