OpenEnergyPlatform / ontology

Repository for the Open Energy Ontology (OEO)
Creative Commons Zero v1.0 Universal
105 stars 19 forks source link

import `characteristic of` from RO #1794

Closed stap-m closed 1 month ago

stap-m commented 5 months ago

Description of the issue

We currently import has characteristic from RO, but not its inverse characteristic of. Instead we defined our own relation has bearer. It is good practice to reuse extisting relations and terms, especially from well-established and widely used ontologies like RO. Therefore, we should think about replacing has bearer with characteristic of.

Workflow checklist

I am aware that

l-emele commented 5 months ago

I agree that we should import characteristic of from RO. But as has bearer is currently used more than 100 times I suggest that we do no replace our has bearer with characteristic of but instead declare has bearer as equivalent to characteristic of. This avoids the tedious work of adapting so many axioms.

l-emele commented 5 months ago

Maybe we should import this whole branch of object properties: grafik

stap-m commented 4 months ago

I agree that we should import characteristic of from RO. But as has bearer is currently used more than 100 times I suggest that we do no replace our has bearer with characteristic of but instead declare has bearer as equivalent to characteristic of. This avoids the tedious work of adapting so many axioms.

I think this is rather a find-and-replace job and managable. But we can discuss this in a meeting.

l-emele commented 4 months ago

I think this is rather a find-and-replace job and managable. But we can discuss this in a meeting.

Only if you neglect the term trackers... It put in on the agenda for the next OEO dev meeting.

areleu commented 3 months ago

From Dev meeting 76:

Aufgaben:

  • disposition of
  • function of
  • quality of
  • role of
stap-m commented 3 months ago

I can do the import and you do the integration/mapping within OEO @areleu?

areleu commented 3 months ago

I can do the import and you do the integration/mapping within OEO @areleu?

Sure, I also wanted to understand how should the oeo-tools used now. Should it be cloned inside the OEO repo?

stap-m commented 3 months ago

Ok. Here's the workflow

  1. Update list of terms to be imported in oeo-tools repo
  2. Run script in oeo-tools repo
  3. PR in oeo-tools repo
  4. Copy xxx-extracted.owl to oeo-repo and check new import in oeo
  5. PR in oeo repo
  6. Reference PRs and issues in both repos for transparency.