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

Subcontractor vs hasSubcontracted #307

Closed VladimirAlexiev closed 1 year ago

VladimirAlexiev commented 3 years ago

The conceptual diagram https://eprocurementontology.github.io/v2.0.2/index.html?goto=1:43 shows

I would expect hasSubcontracted to relate somehow to Subcontractor. This relates to #306 because it mixes up procedure-relative agents (Role etc) with absolute Agents

The ontology release 2.0.1 doesn't define class epo:Subcontractor nor prop hasSubcontracted, and has just this:

epo:proposesSubcontractor
        rdfs:domain  epo:Subcontract ;
        rdfs:range   epo:Subcontractor .
eprocurementontology commented 3 years ago

In version 2.0.1 (latest released version) there is no relation between Subcontractor and Contractor In version 2.0.2 (working model not to be released as an OWL resource) a relation between Subcontractor and Contractor was created via the Agent. In the next version to be published as an OWL resource we intend to introduce reification that will represent the role of an agent in a specific context and this relationship between Subcontractor and Contractor will be taken into account.

costezki commented 1 year ago

The role hierarchy has been reworked. Now the Contractor and Subcontractor roles are siblings.

image