Closed ahashibon closed 4 years ago
same thing for
why have seconds and days etc... this should be changeable for each User Case, and hence propose here and in all quantities to just on the top EMMO levels mention the type of unit:
Time hasUnit TImeUnit
and TimeUnit is the superclass of all relevant time units, like seconds, days, minutes, hours, MarchianHouers, etc...
I agree that this is not very clean. I think we simply should remove all the hasUnit relations from the physical quantities and only associate units their corresponding physical quantity.
This also solves the conceptual mistake that Emanuele pointed out.
Agree?
The physical dimensions introduced in 1.0.0-alpha solves this in a clean way.
I agree we need to standardise on SI units, however, we not make it more explicit and open and consistent as follows:
In this way we eliminate the clutter in the actual quantities having to add possible units in the class definition. For example:
for Area, we simply put
hasUnit Some AreaUnit,
isn't this much more elegant?
@emanueleghedini @jesper-friis your comments please?
thanks.