Rework modular file structure

[stap-m]

Description of the issue

We decided on a modular structure for the OEO to allow the usage of single modules that focus on a sub-topic of the domain and to avoid merge conflicts.
However, our shared-module, which was initially created for the interaction of the modules, grew a lot and became the largest module of oeo recently. This counteracts the original idea of the modular structure.

Therefore, the file structure should be rethought to keep the advantages of the modules.

Ideas of solution

One idea is a new module, that contains only axioms across modules, called oeo-shared-axioms for now.

I also included possible future modules as examples in the drawing: one for sectors and one for the composition of existing classes.

A restructuring like this might call for a version 2.0

Workflow checklist

• I discussed the issue with someone else than me before working on a solution
• I already read the latest version of the workflow for this repository
• The goal of this ontology is clear to me

I am aware that

• every entry in the ontology should have a definition
• classes should arise from concepts rather than from words

[stap-m]

@jannahastings answered to this via e-mail:

Achieving genuine modularity has always been somewhat challenging in OWL given the need for axioms that cross modules to interconnect and build the overall structure. I think your proposal looks good and this will surely be an improvement on having an increasingly large 'shared' module. One risk I see is that the tools support for finding and working with the axioms in just those specific modules might be insufficient as Protege's options may be limited for showing axiom-only content where classes are primarily defined elsewhere. However, I don't know of any tools that offer a solution to this challenge.

[stap-m]

We try this out with a mini-ontology first, to see whether protege errors occur and if they can be fixed.

[stap-m]

While testing with a mini-ontology, I found out that this is a helpful setting for the axioms.

[carstenhoyerklick]

Google table for removing classes to original modules
https://docs.google.com/spreadsheets/d/18Cr2rnsFlZvZuDOEiBFEkjVd5SEvD1gt6qg0VnPpd3Q/edit?usp=sharing

[stap-m]

How to move a class:

1. Delete from oeo-shared and move everything to respective thematic module (via text editor, notepad, ect)
2. Check axioms whether it belongs to thematic module or to shared-axioms (protege)
3. Remove all doubled annotations (protege)
4. term tracker at thematic module

rework module structure 
issue: https://github.com/OpenEnergyPlatform/ontology/issues/1592
pull request: https://github.com/OpenEnergyPlatform/ontology/pull/1652

5. indicate in spreadsheet, which classes are done

Workflow:

• branch from feature-1592-move-classes-to-original-modules and push there, not directly into dev!
• a couple of classes per PR
• responsibility, see google spreadsheet (@l-emele and @nelekoehler oeo-physical, @areleu oeo-social, @stap-m oeo-model, @chrwm oeo-shared)
• deadline: September 22
• CHANGELOG.md will be updated when everything is finished

[l-emele]

We should update the wiki article on the OEO structure: https://github.com/OpenEnergyPlatform/ontology/wiki/modules-of-the-oeo

Maybe it would be also nice to have the structure diagram in README.md (without oeo-composed and without the blue colour of the new modules).

[stap-m]

We should update the wiki article on the OEO structure: https://github.com/OpenEnergyPlatform/ontology/wiki/modules-of-the-oeo

Maybe it would be also nice to have the structure diagram in README.md (without oeo-composed and without the blue colour of the new modules).

@nelekoehler can you take care of the documentation and as well the README please? Here is the updated figure.:

[nelekoehler]

We should update the wiki article on the OEO structure: https://github.com/OpenEnergyPlatform/ontology/wiki/modules-of-the-oeo
Maybe it would be also nice to have the structure diagram in README.md (without oeo-composed and without the blue colour of the new modules).

@nelekoehler can you take care of the documentation and as well the README please? Here is the updated figure.:

Yes, I can do that.

[l-emele]

I close this now as we will be releasing the new structure in a few minutes.