Create automated annotation for module identification

[stap-m]

Description of the issue

From #862:
An annotation is needed that indicates the modules in which a class / object property is defined in. This holds especially for classes from oeo-shared.
To reduce the effort of maintenance, an automated assignement, e.g. when releasing, would be great.

Ideas of solution

Workflow checklist

• I am aware of the workflow for this repository

[stap-m]

The next release is planned for Oct 1st, which would be a great time for introducing such a tool... 😉
Is it complex? @adelmemariani @MGlauer @jannahastings

[jannahastings]

I think this is probably too complex to do in a few days. I am not exactly sure how it would be tackled. There would certainly be edge cases that are tricky to assign one way or another.

[stap-m]

from oeo-devmeeting 25:

• automated annotation seems complex, might cause errors
• developers need to check module manually before implementing!
• MG proposed proposal hidden annotation option --> git commit hook?
  • check at each commit of annotation and module fit, else git error
    for added and moved classes and axioms
  • MG + AM will do a nerdy deepdive on this

[stage1407]

Intermediate result:
Ability to create automatically an OWL-File that contains the belonging to a module (shared, physical, ...) for every IRI based on the schema: IRI oeo:OEO_belongs_to_module IRI of a module .
Uploads coming soon.

[stap-m]

Not fully finished for release v1.9.
Since it is an important issue for our workflow, maybe release this in a minor version before v1.10 (May 1st).

[stage1407]

Current Bugs:

• script doesn't adopt the prefixes of the previous ontologies automatically

[stage1407]

Now the branch should be updated.
Some things that are new:

• You can use now the prefixes of the ontologies in the 'belongs-to-annotated' ontologies of the script
• The decision to which module an entity belongs, will be done by a priority-rule of the following scheme:
  highest priority -> shared -> physical -> social -> model -> lowest priority

[jannahastings]

Great! What is the name of the branch? (And just to double-check, did you push your commit?)

[stage1407]

I changed the milestone, because I won't have it implemented until tomorrow.

[chrwm]

@stage1407 could you may give an update on the issue's status?
PR #1111 was closed without merging. Is the feature's development still ongoing?

[stage1407]

My work on the issue has rested for the past few weeks.
Due to the fact that Janna left, I had lost sight of it.
I will see that the last problems are eliminated and it can be merged.

The biggest problems with it were last:

• there are still wrong annotations
• it is still inconvenient to call the script

[stage1407]

Suspended until decision on distribution of modules has been made

[l-emele]

Suspended until decision on distribution of modules has been made

This means no quick solution, therefore I move the milestone.

[l-emele]

After the large OEO restructuring, do we still need this annotation? Maybe in oeo-shared-axioms?

[stap-m]

We have 'belongs to module', which is outdated, though. Further, the new protege identifies the module automatically.
Therefore, the issue might be obsolete now. We should also consider removing the 'belongs to module' annotation before the next release.

[stap-m]

This issue is not needed anymore, since 1) protege is now able to show the module itself, and 2) the restructuring in #1592. We can finally close it. 🎉