Use Advanced Search to search the entire archive.
Re: On Quantity - Measurement relationship
- From: Werner Keil <
>
- To: "
" <
>
- Subject: Re: On Quantity - Measurement relationship
- Date: Sat, 1 Nov 2014 17:28:33 +0100
It's one major area, also see the Wikipedia article.
F# / Kennedy as well as Fowler mention others including Money. While most
of that is covered by say JSR 354 now, the purpose of this JSR would be to
allow implementations to also interact with those JSRs like 354 or 310 to
do calculations like "How much Money would I safe if I bought that great
new SmartHome system or a more efficient boiler?"
Where a sort of "bridge" to both 354 and 310 or (at least in 354's case it
is easier with a type like MonetaryAmount that's quite extendable to those
who need to) hybrid types implementing both APIs could serve this purpose
rather well.
Werner
On Sat, Nov 1, 2014 at 5:21 PM, Martin Desruisseaux <
>
wrote:
>
Le 02/11/14 01:12, Werner Keil a écrit :
>
>
No where on http://en.wikipedia.org/wiki/Quantity would you see that?
>
>
On http://en.wikipedia.org/wiki/Measurement, "Quantity and measurement
>
are mutually defined: quantitative attributes are those possible to
>
measure, at least in principle."
>
>
According to Wikipedia (based on general science facts in most cases[?])
>
we'd have a hierarchy like that:
>
>
*Quantity*
>
-- *Multitude*
>
-- *Magnitude*
>
>
This is one definition of quantity. The point that I'm trying to make is
>
that, in some context, the word "quantity" may also implicitly means
>
"physical quantities". This is the case in the articles from Microsoft that
>
you gave us.
>
>
So that point that I'm trying to make is that it is a matter of how *we,
>
the JSR-363* group, choose to define Quantity. The current spec clearly
>
restrict the definition to quantitative measurement, which I think is a
>
legitimate restriction provided that we provide a clear definition.
>
>
Martin
>
>
Attachment:
329.gif
Description: GIF image