Closed ramoncast27 closed 5 months ago
It has been agreed to merge the classes epo:GreenProcurement, epo:SocialProcurement and epo:InnovativeProcurement with epo:StrategicProcurement. That is, to create a single object with two different types: epo:StrategicProcurement and the corresponding subtype. Therefore, we will keep the classes at the same level but with the information of the upper level together with the information of the lower level, being able to relate the properties of epo:GreenProcurement, epo:SocialProcurement and epo:InnovativeProcurement with those of epo:StrategicProcurement inherited by hierarchy. The cases raised above will now look like this:
In the PPDS project we are preparing dashboards using Strategic Procurement information. For this, during the transformation we need to identify the necessary relationships and map the information appropriately. The objects we are interested in are: epo:StrategicProcurement, epo:GreenProcurement, epo:SocialProcurement and epo:InnovativeProcurement; and their relationships with at-voc:strategic-procurement, at-voc:environmental-impact, at-voc:social-objective and at-voc:innovative-acquisition. For the moment we are mapping each lot with each object through epo:fulfillsStrategicProcurement. That is:
Following this diagram:
We would be interested to know if there is any direct relation between the highest level (epo:StrategicProcurement) and the three sub-levels (epo:GreenProcurement, epo:SocialProcurement and epo:InnovativeProcurement) and thus be able to relate, for example, a StrategicProcurement of type http://publications.europa.eu/resource/authority/strategic-procurement/env-imp with the associated GreenProcurement of type http://publications.europa.eu/resource/authority/environmental-impact/biodiv-eco.