add way to include github specifications

[akleinau]

Description of the issue

From #197. Add github specifications like github organisation and contributions graph.

Ideas of solution

I think the best way is as annotations?

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

[jannahastings]

How will these be used?

Option A: Do we want to associate actual literal values with classes or individuals that are included in the ontology? - if so then yes, we should create them as annotation properties.

Option B: Or do we want to annotate some tabular data, e.g. a column in the OEP, with an OEO ID specifying what the column contains? - If so then we may be better off creating a class beneath "information content entity" analogous to the IAO class for "email address"

[l-emele]

What is even meant with the contributions graph? That one? https://github.com/OpenEnergyPlatform/ontology/network

[sfluegel05]

This comes from https://openenergy-platform.org/factsheets/models/35/ (section openness) To me it seems like we have a model or dataset in the ontology and need a link to the github organization responsible for this. So it would go with option A and add annotation properties.

What is even meant with the contributions graph? That one? https://github.com/OpenEnergyPlatform/ontology/network

I'm not sure what is meant by a "contributions graph". It doesn't seem to be an official term for a specific graph. I found contribution calendars, but they are person-specific, not organization- or repository-specific. Another candidate is https://github.com/OpenEnergyPlatform/ontology/graphs/contributors

Maybe "contributions graph" is meant as an umbrella term for different kinds of graphs.

[l-emele]

I looked into the fact sheets itself (e.g. this one). It is the Github Contribution Graph that should be included as image in the Openness section:

[sfluegel05]

It is the Github Contribution Graph that should be included as image in the Openness section:

I agree with that. My problem was mainly that The Github Contributions Graph does not exist.

Apart from that, the important question we have to answer here is the one posed by @jannahastings : Do we need annotation properties or information content entity subclasses?

Here I would choose the subclass-option, because that is what we did for comparable concepts from the factsheets, i.e., license and email address.

[stap-m]

Here I would choose the subclass-option, because that is what we did for comparable concepts from the factsheets, i.e., license and email address.

I agree, that licence, email adress etc. will be used similarly. But, as I understand it, we won't annotate columns with it something like github contribution grap, but e.g. entries in the factsheets. Which calls for option A...