Open ColinHDev opened 1 week ago
- There were already the
areal energy density
and theareal power density
which described concepts per a certain area. But they are implemented in the OEO, so at least theareal quantity value
parent class could not be implemented in OEOX.
i'd prefer to avoid another layer. These classes could also be grouped by other criteria.
Here some remarks:
areal energy density/power unit
, although in oeo, could use an equivalent axiom to describe the nominator/denominator.areal count unit
could have the alternative label count per area unit
wind turbine count per area
could have the alternative label number of wind turbines per area
energy produced from renewables per area
: the unit here is also areal energy density
:)power capacity from renewables per area
: the unit here is also areal power density
:)Could you please create the equivalece axioms for these classes?
- I wasn't sure how to model "per inhabitant" as a unit. I would have liked to create something similar to
areal unit
, but I wasn't sure what the denominator would be.
The unit of e.g. "energy per inhabitant" is just an energy unit (i.e. the denominator is 1).
- I just saw that
areal energy density/power unit
, although in oeo, could use an equivalent axiom to describe the nominator/denominator.
Yes, but I think that's the case for all the OEO-implemented subclasses of unit
, like square kilometer
, area per power unit
, ...
But since the object properties has unit numerator
and has unit denominator
, they are technically also missing on all the composed units of UO, like watt-hour
energy produced from renewables per area
: the unit here is alsoareal energy density
:)power capacity from renewables per area
: the unit here is alsoareal power density
:)
Ahh, apparently I misunderstood their definition. But while rereading I noticed the definition of areal solar energy density
as a subclass of areal energy density
: An areal solar energy density is an areal energy density that gives the arriving solar power per area. A synonym for areal solar power density is irradiation.
Shouldn't the 2 "power" in there be swapped for "energy"?
Also, while being almost finished with this and working on the axioms, I noticed there is also an irradiance unit
by the UO, which would make areal power density unit
obsolete?
Could you please create the equivalece axioms for these classes?
First time creating these axioms, so there's probably still room for improvement:
'areal energy density unit'
EquivalentTo 'unit'
and 'has linear unit numerator' some 'energy unit'
and 'has linear unit denominator' some 'area unit'
'areal power density unit'
EquivalentTo 'unit'
and 'has linear unit numerator' some 'power unit'
and 'has linear unit denominator' some 'area unit'
'areal count unit'
EquivalentTo 'unit'
and 'has linear unit numerator' some count unit
and 'has linear unit denominator' some area unit
'areal population count unit'
EquivalentTo 'areal count unit'
and 'has linear unit numerator' some 'population count unit'
'energy produced from renewable energies per area'
EquivalentTo 'quantity value'
and 'is about' some 'renewable energy'
and 'is about' some 'two-dimensional spatial region'
'power capacity from renewable energies per area'
EquivalentTo 'quantity value'
and 'is about' some 'renewable energy'
and 'is about' some 'two-dimensional spatial region'
'wind turbine count per area'
EquivalentTo 'quantity value'
and 'quantity value of' some 'wind energy converting unit'
and 'is about' some 'two-dimensional spatial region'
'population density'
EquivalentTo 'quantity value'
and 'quantity value of' some 'population'
and 'is about' some 'two-dimensional spatial region'
'battery count'
EquivalentTo 'quantity value'
and 'quantity value of' some 'battery'
'battery energy storage content'
EquivalentTo 'energy storage content'
and 'quantity value of' some 'battery'
'energy produced from renewable energies per inhabitant'
EquivalentTo 'quantity value'
and 'is about' some 'renewable energy'
'electricity demand per inhabitant'
EquivalentTo 'quantity value'
and 'quantity value of' some 'electricity demand'
'heat demand per inhabitant'
EquivalentTo 'quantity value'
and 'quantity value of' some 'energy demand'
and 'is about' some 'thermal energy'
The unit of e.g. "energy per inhabitant" is just an energy unit (i.e. the denominator is 1).
In the meeting, we discussed implementing a special population count unit
as a subclass of count unit
. I want to make sure, that thought is wrong: Saying our electricity demand per inhabitant
has a unit with a denominator of population count unit
doesn't work, because we don't want our class to represent the electricity demand of some number of people, like the electricity demand per city (with obviously varying population counts per city), but the electricity demand being for a single inhabitant making the denominator 1
?
This would be the current version:
energy produced from renewables per area
: the unit here is alsoareal energy density
:)power capacity from renewables per area
: the unit here is alsoareal power density
:)Ahh, apparently I misunderstood their definition. But while rereading I noticed the definition of
areal solar energy density
as a subclass ofareal energy density
: An areal solar energy density is an areal energy density that gives the arriving solar power per area. A synonym for areal solar power density is irradiation. Shouldn't the 2 "power" in there be swapped for "energy"?
Well spotted, thanks. I am not 100% sure whether this is a bug. Could cou open an issue in oeo repo on this please?
Also, while being almost finished with this and working on the axioms, I noticed there is also an
irradiance unit
by the UO, which would makeareal power density unit
obsolete?
Hm, we should check the def, if it is actually the same thing. If yes, we can add a mapping annotation. I don't want to make our class obsolete. However, this is another hint that we have to do something about the units. Maybe the first stept is to get rid of the redundant stuff... Could you please also open a separate issue? This might require some good preparation and then a discussion in a dev-meeting.
In the meeting, we discussed implementing a special
population count unit
as a subclass ofcount unit
. I want to make sure, that thought is wrong: Saying ourelectricity demand per inhabitant
has a unit with a denominator ofpopulation count unit
doesn't work, because we don't want our class to represent the electricity demand of some number of people, like the electricity demand per city (with obviously varying population counts per city), but the electricity demand being for a single inhabitant making the denominator1
?
Exactly.
A population count unit
would make sense for something like inhabitants per km2
. But I guess the count unit
works here, too, right?
For the SLE project, OEO(X) concepts for the following quantity values are needed:
This would be a first concept for the taxonomies of the new concepts:
areal quantity value
/populational quantity value
areal energy density
and theareal power density
which described concepts per a certain area. But they are implemented in the OEO, so at least theareal quantity value
parent class could not be implemented in OEOX.unit
s, as it made sense to have a common parent class with a denominator of somearea unit
.areal energy density unit
andareal power density unit
are again implemented in the OEO, so theareal unit
could not be implemented in OEOX.areal unit
, but I wasn't sure what the denominator would be.