"handles_uncertainty" needs domains deterministic and stochastic

[akleinau]

Description of the issue

The "approach to uncertainty" is part of the model factsheets (#15) and should be included in the ontology.

We have an object property "handles_uncertainty" but we dont have instances "deterministic" and "stochastic" to choose as domain, eg. model_x handles_uncertainty value stochastic.

Those two then also need a type. We have the class "Uncertainty" (subclass of validation) but I'm not sure if that fits.

Ideas of solution

Add instances "stochastic" and "deterministic" and give them a type.

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 new entry in the ontology should have an annotation
• classes should arise from concepts rather than from words
• class or property names should follow the UpperCamelCase

[sfluegel05]

The class uncertainty was removed in #347, the object property handles uncertainty has also been deleted at some point.

This means we have to introduce a new class uncertainty handling (maybe with a better label). As this is about describing models, I would suggest to make uncertainty handling a subclass of model descriptor (analogous to analytical approach and methodical focus which also have assigned instances). Definition: Uncertainty handling is a model descriptor that specifies how a model deals with uncertainty.
Then we can add stochastic and deterministic as instances. I don't think we need a relation handles uncertainty because other model descriptors just use is about.

[sfluegel05]

Does everyone agree with my proposal (especially @p-kuckertz and @carstenhoyerklick, since you have been assigned to this issue)?

[p-kuckertz]

Hi Simon, for me your proposal makes good sense: * We need this concept to describe models * Therefore it should belong to “model descriptor” (esp. when other model describing concepts have been put here) * I also agree with “is about”, since this descriptor is about a specific concept - instead of basically always asking how the model handles a, b, c, etc. Concerning the name giving, I would prefer “uncertainty approach” (in accordance with “analytical approach” and the OEP Model Factsheet field “approach to uncertainty”), then with stochastic and deterministic as possible options. Best regards, Patrick

…

--------------------------------------------------------------------------- Dr. Patrick Kuckertz Institut für Energie- und Klimaforschung – Technoökonomische Systemanalyse (IEK-3) <https://www.fz-juelich.de/iek/iek-3/DE/Home/home_node.html> Forschungszentrum Jülich GmbH D-52425 Jülich Telefon: +49 2461 61-1822 Mobil: +49 175 4163674 E-Mail: ***@***.*** ***@***.***> Von: Simon Flügel ***@***.***> Gesendet: Donnerstag, 5. August 2021 13:40 An: OpenEnergyPlatform/ontology ***@***.***> Cc: Kuckertz, Patrick ***@***.***>; Mention ***@***.***> Betreff: Re: [OpenEnergyPlatform/ontology] "handles_uncertainty" needs domains deterministic and stochastic (#183) Does everyone agree with my proposal (especially @p-kuckertz <https://github.com/p-kuckertz> and @carstenhoyerklick <https://github.com/carstenhoyerklick> , since you have been assigned to this issue)? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#183 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AICVBRUV44CUBASMKCBYRNDT3J2AZANCNFSM4J3YRP2Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .