OpenEnergyPlatform / ontology

Repository for the Open Energy Ontology (OEO)
Creative Commons Zero v1.0 Universal
111 stars 23 forks source link

Add terms for Energy and Battery sub-technolgies #1979

Open bihan-su opened 2 days ago

bihan-su commented 2 days ago

Description of the issue

I would like to add definitions for types of PV panel, on- and offshore wind power technology, lithium-ion battery, and flow battery to the OEO.

Ideas of solution

These are suggested definitions provided on wikipedia (sources in Excel document at the end of the definitions): PV panel https://openenergyplatform.org/ontology/oeo/OEO_00000348/

onshore wind power technology https://openenergyplatform.org/ontology/oeo/OEO_00010425/

offshore wind power technology https://openenergyplatform.org/ontology/oeo/OEO_00010426/

lithium-ion battery https://openenergyplatform.org/ontology/oeo/OEO_00000248/

flow battery https://openenergyplatform.org/ontology/oeo/OEO_00000169/

The following Excel file gathers all the information: technology_ontology.xlsx

Workflow checklist

I am aware that

areleu commented 1 day ago

I will take care of this, we should discuss it on friday but I have some preliminary questions @stap-m . The technology class has an axiom participates in some process. I am trying to understand how can this be the case. I would say that artifacts that follow certain specifications which collectively are bundled as technology, these specifications enable these artifacts with capabilities to participate in those processes and these are the ones ultimately participating.

Since the artifacts are designed on the basis of some specification, I think turning around the axioms a bit can complete the technology <-> artifact axis, so an artifact can be of a particular kind only if they are designated by the technology. We could even furtherly specify is about for t his particular case using something like https://github.com/CommonCoreOntology/CommonCoreOntologies/blob/develop/src/cco-modules/InformationEntityOntology.ttl # designates

This is relevant for this issue because if we opt to do this would imply always generating a pair of artificial object / technology for each subclass.

stap-m commented 1 day ago

I'll put this on the agenda for the developer meeting in january