Open adelmemariani opened 1 month ago
I assume these relations should be in the oeo.
Should we transfer this issue to the OEO repo?
I generally agree and don't have a strong opinion on how we do it. So feel free to move it if you feel this would be more structured.
Another approach would be to create a separate issue in the OEO repo and link that issue there. Then we could use this issue here as a reminder to use the relationships for the oevkg once they are available in oeo.
Additionally some new class I think would be good to have in the OEO. Mainly ‘quantitative values’ (which already exist) and the ‘quality checked quantitative values’ for the value column isAbout annotation.
We now have the OEVKG as a virtual knowledge graph for quantitative scenario comparisons, therefore, we should choose the relations between a data descriptor entity and its related elements. For example, this table contains a category column and it is annotated as 'CRF-based sector division' in its metadata. So, we need a new relation here like 'has sector division' or 'has category'. For example:
'oevkg:data_descriptor/123' 'has category' 'oeo:agriculture'
We need to define more relations based on the data tables. I created this issue to serve as a reminder and to keep it in mind for the future.