-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta-Issue: Example case for instance data description in triples #5
Comments
That's a quite specific and huge example. I would suggest that we focus first on how to implement only the economic properties. These are the most important attributes in energy system models and I use them in my model for nearly every process. But I am not an ontology expert, so my question to @OpenEnergyPlatform/oeo-general-expert-formal-ontology is: is it possible that we include for example a class "fix investment costs" and link it somehow to every process or artificial object which could have invest costs? |
Yes it is not small - but we did not want to leave anything out in order to show how complex it can get. But it is not our primary purpose to fully implement everything what is mentioned in the example. We would rather like to learn how attributes, constraints, units, etc are to be properly incorporated. |
Related to OpenEnergyPlatform/ontology#268 |
Until now, we've never really implemented the connection between "objects" and "attributes". From the past discussions on |
That should be no problem. I am not sure if we've already an appropriate relation for that, though. We have |
A mass of heat that is measured as a volume 🤔🤣 |
Hi everybody, |
Once we implement the composed module, we can work on this issue. |
Description of the issue
Although I did not not participate in the developer meeting (but will do in the next one) I understood from discussions with @p-kuckertz that a central goal of the ontology development is to use it to describe real world data for modeling purposes.
OWL can give an umambiguous definition to instance data. This makes different data sources comparable and mergable. Futher, it allows to validate the instance data for ontological consistency and constraints to identify missing, false or inconsistent data using a Shapes Constraint Language (SHACL).
To describe instance data we require a trible of class, attribute and constraint.
In this issue I would like to present a short example of instance data for an electrolyzer to discuss the development of such triples in the ontology. Please note, that this is just an example to identify the requirements for decribing instance data in the OEO and as a basis for further discussions.
EXAMPLE:
A electrolysis system has none or many
A electrolysis system has none or one
General properties:
Economic properties:
Technical Properties:
Workflow checklist
I am aware that
The text was updated successfully, but these errors were encountered: