Organise and document all PyPi packages

[Ludee]

Document the corresponding PyPi releases of the repos:

• https://github.com/OpenEnergyPlatform/metadata -> https://pypi.org/project/oep-metadata/
• oem2orm -> https://pypi.org/project/oem2orm/
• omi -> https://pypi.org/project/omi/
• ...

[MGlauer]

I still oppose the notion that the metadata repository should be a python package. It is a standard - not something you use. If you want to supply software that works with this standard, you can put it into a python package - in an independent repo. IMO, the metadata should be language independent, to make it easier to include it is other (external) applications.

[jh-RLI]

There is already a suggestion for this. Should we use Zenodo?

BTW we already have a oep-metadata PyPi package.

[jh-RLI]

We primarily rely on the oemetadata PyPI package to simplify the integration of the specification into our Python tools (as you also suggested in your comment). The package includes the necessary .json files as well.

I also see it as a language independent standard for metadata ... for that users can get the files via Github. To make this more specific, could we add a page to the oeplatform where users can download the versions of the oemetadata or just Zenodo?

As this issue is about another topic we should continue this discussion here https://github.com/OpenEnergyPlatform/oemetadata/issues

@christian-rli