Developing a common ontology for the domain of energy system analysis.
The Open Energy Ontology (OEO) is a domain ontology of the energy system analysis context. It is developed as part of the Open Energy Family. The OEO is published on GitHub under an open source license. The language used is the Manchester OWL Syntax, which was chosen because it is user-friendly for editing and viewing differences of edited files. The OEO is constantly being extended. The first version of the OEO has been released on June 11th 2020. A Steering Committee (OEO-SC) was created to accompany the development, increase awareness of the ontology and include it in current projects.
This domain ontology is a collaborative effort to represent the context of energy system analysis based on standard terminologies used by human experts in this field of research. It is designed to improve transparency and facilitate comparability and transferability of energy system modelling and scenario analysis. This ontology makes use of the Basic Formal Ontology (BFO) and its principles. It re-uses several other ontologies as described in the GitHub Wiki.
This repository is licensed under CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.
For a scientific citation please see the CITATION.cff.
To cite a specific class of the ontology and its definition please use the following convention:
'class label' (FUll-URI) from the Open Energy Ontology (OEO)
Example:
'energy system' (https://openenergy-platform.org/ontology/oeo/OEO_00030024) from the Open Energy Ontology (OEO)
The latest version of the OEO can be accessed on the Open Energy Platform and the Master Branch.
All released versions can be downloaded directly from the GitGub Releases.
The currently developed version is available on the default dev Branch.
The source code of the ontology is found in the folder src/ontology/
The main file is src/ontology/oeo.omn
All own modules are collected in the folder src/ontology/edits/
The following diagram illustrates the modular file structure of the OEO. It depicts the import and file hierarchy from external imports (right) to the main file oeo.omn (left).
The imported modules are under src/ontology/imports/
To get an overview of the existing modules, take a look at the following wiki article: GitHub Wiki
We recommend to use the software Protégé to open and edit the ontology. Additionally, an ontology viewer is available on the Open Energy Platform.
This is an interdisciplinary open source project, help is always welcome.
Everyone with good intentions is invited to develop this repository.
The development of the ontology happens mainly on GitHub and is supplemented by regular (online) developer meetings to review the progress and discuss more complicated topics.
If you would like to participate in meetings you can become a team member. Use the OEP contact form and add yourself as a contributor after approval.
If you're new to GitHub or ontologies check out our "How to participate" article for some first advice and helpful links. You may also use the Open Engery Academy course to get used to the necessary tools and background information.
The workflow is described in the CONTRIBUTING.md file. Please check it out before you start working on this project. Points that are not clear in the file can be discussed in a GitHub Issue.
Please read the GitHub Wiki for more information about the ontology, its standards, its best practice principles and the BFO classification.
Wiki articles that you would be most helpflul to a beginner are:
- How to Participate
- Best Practice Principles including subsections
- BFO Upper Ontology including subsections
- Explaination on Mass Nouns
- Handeling Ambiguous Terms
- Use Protégé to Change the Ontology
- Term Tracker Annotation
... as well as the CONTRIBUTING.md
Experts in ontology engineering, economy and energy-system modelling work together collaboratively.
We combine domain knowledge with knowledge about how an ontology should be designed.
If you have a specific question about ontology design, energy system modelling or economy (in context of this ontology), you can tag one of these teams (or persons) to notify its members that you need their feedback or help.
The OEO is organised in a general team and several subteams:
- @oeo-dev
- All developers of the OEO
- @oeo-community-manager
- Contact point for personal and team related concerns
- @oeo-concept-owner
- Strategic and long-term development and coordination of developers
- @oeo-steering-committee
- Members of the Steering Committee (OEO-SC)
- @oeo-release-team
- Coordinates the periodic releases
- @oeo-domain-expert-energy-modelling
- Knowledge related to energy system modelling and simulation
- @oeo-domain-expert-economy
- Knowledge related to economic system, costs, monetary issues
- @oeo-domain-expert-linked-open-data
- Knowledge related to linked open data
- @oeo-domain-expert-meteorology
- Knowledge related to meteorology and weather
- @oeo-general-expert-formal-ontology
- Knowledge related to formal ontology expertise and BFO