Page MenuHomePhabricator

Quantity datatype (tracking)
Open, HighPublic

Description

The quantity datatype allows to enter quantities. It has quantity value, lower, upper, and a unit.


NOTE: Quantities are assumed to be uncertain per default, exact quantities are considered to be an exception. The idea is that quantities are usually measures. Since this leads to confusion and discussion, here's the rationale for reference: When doing arithmetics with quantities, such as unit conversion, defaulting to "exact" values would lead to "false precision" in the output.

From https://en.wikipedia.org/wiki/False_precision:

"In science and engineering, convention dictates that unless a margin of error is explicitly stated, the number of significant figures used in the presentation of data should be limited to what is warranted by the precision of those data."

And from https://en.wikipedia.org/wiki/Significance_arithmetic:

"If a calculation is done without analysis of the uncertainty involved, a result that is written with too many significant figures can be taken to imply a higher precision than is known".

Details

Reference
bz54318

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.
StatusSubtypeAssignedTask
OpenNone
ResolvedNone
ResolvedNone
DuplicateNone
ResolvedNone
OpenNone
Resolveddaniel
ResolvedFeatureMichael
ResolvedNone
OpenNone
Resolvedthiemowmde
Resolveddaniel
Invaliddaniel
ResolvedLucas_Werkmeister_WMDE
Resolvedthiemowmde
OpenNone
ResolvedLydia_Pintscher
Resolveddaniel
OpenNone
OpenNone
OpenNone
OpenNone
Resolvedthiemowmde
InvalidNone
Resolvedthiemowmde
DuplicateNone
Resolvedthiemowmde
OpenNone
OpenNone
DuplicateNone
OpenNone
OpenNone
Resolved Jonas
Resolvedthiemowmde
OpenNone
OpenNone
OpenNone

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:00 AM
bzimport set Reference to bz54318.
bzimport added a subscriber: Unknown Object (MLST).

I wonder if the unit should be controlled by a predefined code list. Otherwise we will have a multitude of units for the same quantity type, e.g. W, kW, MW etc. for power.

Alternatively, in stead of unity type, allowing selection of a quantity type like "time", "length", "area", "power", "currency" etc. where the unit is predefined to a non-prefixed unit, correspondingly to "s", "m", "m2", "W", "unspecified".

  • Bug 52916 has been marked as a duplicate of this bug. ***

physik wrote:

I saw a RFC. Is someone working on that?
Semantic annotation of formulae that contain units is part of my PhD topic... therefore I'm very interested in that topic and open for potential contributions.

Status update: We have just released the first version of the quantities data type on Wikidata.org. It does not yet support units.

@Physikerwelt: feel free to get in touch with me via email :)

Lydia_Pintscher removed a subscriber: Unknown Object (MLST).
daniel set Security to None.

This is actually wrong "Quantities are assumed to be uncertain per default, exact quantities are considered to be an exception. The idea is that quantities are usually measures. " A quantity is exact, a measurement is inexact. You count the number of coins, and the number is exact. You measure the weight of the coins, and the weight is an inexact number with an error. That error isn't bound by limits but by an error function, which in the limit is an standard deviation.
</rant>

@jeblad: so we agree about everything except the names. Perhaps I should have used "Measurement" instead of "Quantity"? But a measurement is a specific event, that would also be misleading. "MeasuredQuantity" would be more exact, but it's a bit long.

I say the bike shed should be yellow!

For what it is worth, "quantity" seems just fine to me. Both a measurement and a count can give a value for a given quantity. Also, a measurement is not only an event, but also its result, so there is no need for a "MeasuredQuality".

To be even more pedantic, there is also another kind of quantity: estimations. Those are not directly measured or counted; they are calculated using a model with known quantities (from which they inherit their precision), e.g. the age of the Universe is estimated at 13.798±0.037 Gy. In that case the error may come both from the measurement and from the model.