OEOX on OEP and how we could go about releasing it on GitHub

[jh-RLI]

Since the last version of the oeplatform, the oeo-extended for composed units is part of the oeplatform and can be called via the OEMetadaBuilder tool.

There is a so-called plugin view, which is available as a modal/popover window. It can only be called in the fields for ‘Subject’ and in the fields ‘isAbout’ and ‘valueReferance’, which are part of the ‘Resources’ area in which the structure of the data tables can be described:

Currently, the user has to manually copy the URI of each new composition once it has been successfully created and add it to the oemeta data to annotate it. This can be changed but requires a bit more effort as adding the newly created terms to our oeo search service is more complicated than expected.

The URI of a newly created term can be retrieved via the we browser in a similar way as it is possible for the oeo classes. So linking the new class is possible.

So how can we release a specific version of the oeo-extended:

Since there is no automated validation that checks if the newly created composite unit makes sense, we can consider the oeo-extended on the OEP as something created by the community. While it is ensured that the part values used to create the composite class already exist in the OEO, it is currently not ensured that they belong to the subclass unit or something similar. So I suggest that from time to time we download the oeo-extended from the oep and do a review of everything that has been added by the community. Then we release the classes that make sense here on GitHub and clean up the rest, and add this back to the OEP as well.

It is possible to download the oeox using the url below. Currently, there is no button to do that. Also, the resulting file name is strange i just noticed:
https://openenergyplatform.org/ontology/

I also added this template of the empty oeo-extended to the OEP, you can review if this structure is valid or need more adaptation:
https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/oeo_ext/oeo_extended_store/oeox_template/oeo_ext_template_empty.owl

One small thing:
There is only one part that is different with the oeo-extended on the OEP production server, because otherwise the OEO has to be downloaded over the internet - this is not possible because this kind of connection is restricted on the oep production server.
Instead, this part refers to a local file of the OEO version on the OEP server:

https://github.com/OpenEnergyPlatform/oeplatform/blob/d7ff69095cc72389b5d77fbaec39564f8a2ca9ef/oeo_ext/oeo_extended_store/oeox_template/oeo_ext_template_empty.owl#L12

FYI @stap-m @l-emele