Create OEO module for composed concepts

[l-emele]

We documented the idea in the etherpad of the 6th project meeting. However, the notes that were taken are not elaborate in any way... That's it:

Discussion on the combination of terms

• create a new class "warmwasserbedarf" and use it
• But the number of combination is very high
• It is not possible in RDF that easy
• -> create a module in the oeo "compositions"

Clustering the compositions:

• those related to projections
• those related to narriatives
• those related to the study report (authorship, ...)

Originally posted by @stap-m in OpenEnergyPlatform/oekg#6 (comment)

[l-emele]

From OEO dev meeting 48:

• Typical problem
  • Fabian talked to Janna
• Example:
  • energy consumption
  • located in
  • germany

1. introduce concepts that belong together as new concepts, define as equivalent concepts

• if it gets too large, tools might be überfordert
• might be too
• in seperate module

2. on-the-fly-anntation: tool to enable people to compose there own compositions in MAN syntax

• maybe omit quantoren, e.g. some, all
• aim: well-defined owl class
• HACK
  • reduce relations
  • domain and range
  • if between domain and range only a specific relation is possible
    • than a tool could be written that adds relation to sole concepts
      • user annotates
        • energy consumption value (has axiom: has spatial region)
        • germany
      • -> axiom is added by tool
    • Task: "isAbout" relation has to be replaced by more specific relations
  • potential funding for tool
    • NFDI4energy/ing
    • @cm check in SEDOS
    • DKZ
    • place in own project
• last status: undecided, both options are ressource-intensive and little user-friedly. Currently, slight preference to Option 1)

[stap-m]

Examples: energy service demand for passenger likometre

[stap-m]

From todays oeo-dev meeting # 66

• idea to make oeo composed as own repo, e.g. "oeo extension"
• might allow more freedom
  • maybe directly use dev instead of a released version
• would require own namespace
• not part of release 2.0
• dedicated oeo-dev-meeting # 69

[stap-m]

• not part of release 2.0

I'll move it to a later milestone

[l-emele]

• dedicated oeo-dev-meeting # 69

Somehow we missed to put this even on the agenda of OEO dev meeting 69. So i put it now on the agenda for meeting 70 on 2023-11-30.

We probably won't have the composed module ready until the next release, so I move the milestone.

[stap-m]

This was completed by the introduction of https://github.com/OpenEnergyPlatform/oeo-extended 🎉