make OEO more OBO conform

[stap-m]

Description of the issue

OBO foundry has a couple of principles that are seen as good practise for interoperable ontologies.
I ran the OBO dashboard¹ to check OEO against these principles. Many of them are not met due to small issues and could be fixed easily, see figure below.
The dashboard check might be a good quality reference for OEO.

Ideas of solution

Go through the principles and check errors in detail.

Workflow checklist

• I am aware of the workflow for this repository

Footnotes

1. https://oboacademy.github.io/obook/howto/deploy-custom-obo-dashboard/ ↩

[stap-m]

For OBO registered ontologies, metadata is stored here. I fear, some of the principles can not be met because OEO cannot be registered.

[l-emele]

Any reason why you checked the very old version 1.13.0 instead of the most recent version?

[stap-m]

Because I did the check half a year ago... but good point. I'll do an update.
EDIT: But I don't think there will be much change.

[stap-m]

I updated the dashboard run with version 2.0.1 (the recent version on OEP), see picture above.

[l-emele]

One easy thing: We should add foaf:homepage <https://openenergy-platform.org/ontology/oeo> to oeo.omn.

[l-emele]

To me, it is no always obvious what the problems are and how to solve this issue. Maybe it is a good idea to treat this issue as a meta issue and open separate issues for each of the checks where we got an error or a warning.