[meta] Restructure quantity values

[stap-m]

Description of the issue

From oeo-dev 82. This builds on #1510.

Ideas of solution

Which quantity values are actually quantity values? ToDo: add axioms

• area value
• coefficient of performance value
• discount rate
• fee
• gross domestic product ( später Bezug zu process attribute)
• gross value added
• inflation rate ( Bezug zu process inflation)
• marginal cost
• markdown
• market revenue
• markup
• purchasing power parity
• efficiency value
• emission value
• forecast error
• fraction value ( muss aber überarbeitet werden)
• full load hours
• global warming potential
• length value
• time span (incl. subclasses) label anpassen
• transport performance value
• volume --> in volume value umbenennen? und volume als quantity einführen
• volumetric flow rate

Which quantity values are actually quantities/qualities? Move and connect to quantity values

• cost #1902
• monetary price (incl. subclasses) #1902
• maximum values --> detaillierter anschauen
• slope (--> quantity value angle value)
• specific space requirement
• surface azimuth angle --> Ausrichtung im Raum als quantity einführen?

Which quantity values are actually process attributes?

• due
• remuneration (Überklasse von due?)
• maximum values --> detaillierter anschauen

What do we need in addition, what do we need to change:

• add monetary value (quantity value of cost/price)
• add relational quantity value? (setzt zwei quantities ins verhältnis)
  • Bezug von full load hours zu process über process atttribute performance
  • market share value zu fraction value
  • area per power value als relational quantity value für specific space requirement
  • annual GDP growth
  • discount rate
  • exchange rate
  • inflation rate
  • all monetary prices
  • purchasing power parity
• emission brauch axiom 'has process attribute' some 'emission rate'
• emission quantity value löschen (wurde zu emission value)
• energy amount value wird zu energy value
• electricity export/import value wird aufgelöst,
• electricity export/import braucht process attribute was Verbindung zu quantity value hat
• energy value braucht korrespondierendes process attribute (issue #1865 bleibt offen bis #1812 auch geklärt ist)
• Fraction Value mit oeox verknüpfen und andere noch unter fraction value einsortieren
• als äquivalente Klasse einführen
• maximum values in quantities und process attributes einsortieren
• dann auch power value anschauen
• label von potential ändern
• population count überarbeiten
  • has quality amount? #1896
• quantity value count
• population ist object aggregate --> braucht quantity
• klarere Definition von size (amount vs. size) #1896
• angle value
• quality orientation einführen: quantity values: slope und surface azimuth angle
• label von time span + subclasses mit value anpassen
• Volume (quantity value + quantity)

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

[stap-m]

Which quantity values are actually quantities/qualities? Move and connect to quantity values

• cost
• monetary price (incl. subclasses)

• We initially proposed to make cost a quantity. I have the impression, it might be rather a process attribute instead, since costs are caused by processes (could also be a process of stasis. Any thoughts?

• monetary price:

  • current def as quantity value: A monetary price is an economic value that describes the amount of money requested, expected, required or given in exchange for something else.
  • draft for a new definition as quantity/quality: A monetary price is a quality of a good(?) that indicates the value in terms of the amount of money requested, expected, required or given in exchange for something else.

[stap-m]

Which quantity values are actually quantities/qualities? Move and connect to quantity values

• ...
• specific space requirement

add relational quantity value? (setzt zwei quantities ins verhältnis)

• We have specific space requirement: A specific space requirement is a quantity value that indicates a certain space requirement per nameplate capacity.
• We have specific space requirement: A space requirement is a two-dimensional spatial region that covers the area needed by an object or object aggregate.
• I'd argue that the space requirement is the quantity (not a spatial region!). The specific space requirement is probably a relational quantity value (which we've planned to define, see above).
  • 'material entity' 'has quality' some 'space requirement'
  • 'space requirement' 'has quantity value' some ('area value' or 'volume)

[stap-m]

Which quantity values are actually quantities/qualities? Move and connect to quantity values

• ...
• slope

• We have: slope: A slope is a quantity value with a plane angle unit that measures the angle between the plane of a surface and the horizontal plane.
• Make it quantity/quality: A slope is a quantity of a ??? (material entity, 2dim spatial region) that is inclined with respect to the Earth's surface or another direction of reference. Its magnitude can be quantified via a angle value (to be defined, see above).

[stap-m]

With the introduction of relational quantity value and a consequent application of fraction value, the class economic value as it currently exists, looses its children. Do we need it anyway? Is there a criterion that we could apply to make it an equivalent class that is inferred?

[l-emele]

Do we need it anyway?

The definition is rather arbitrary anyway: An economic value is a quantity value that is economically relevant. Any of our quantity values can be economically relevant in one way or another.