Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Missing quantities in specification
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Missing quantities in specification
- Date: Mon, 15 Dec 2014 16:03:45 +0100
Yep, it's "Information" now, similar to e.g. "Radioactivity" which had a
more complex name or "Speed" instead of "Velocity".
The quantities in the API are SI ones, listed here on Wikipedia (did they
miss anything?;-)
http://en.wikipedia.org/wiki/International_System_of_Units
There's this BIPM brochure, which now has a nice online version, too:
http://www.bipm.org/en/publications/si-brochure/
We might prefer to quote it (and where appropriate also relevant
sub-sections) rather than pointing to a PDF, especially if that seems
outdated now
Werner
On Mon, Dec 15, 2014 at 2:41 PM, Martin Desruisseaux <
>
wrote:
>
>
The table provided in the "*Supported quantities*" section of the
>
specification is missing the following types, compared to the current
>
Javadoc:
>
>
- Action
>
- AngularAcceleration
>
- AngularSpeed
>
- Dimensionless
>
- DynamicViscosity
>
- ElectricPermittivity
>
- Information
>
- InformationRate
>
- IonizingRadiation
>
- KinematicViscosity
>
- Luminance
>
- MagneticFieldStrenght
>
- MagneticPermeability
>
- MassFlowRate
>
- Torque
>
- VolumetricDensity
>
- VolumetricFlowRate
>
- WaveNumber
>
>
The following type is not present anymore (or was it renamed
>
"Information"?)
>
>
- DataAmount
>
>
My question is: what is the criterion for deciding which quantity to put
>
in the javax.measure.quantity package? What prevent me from pushing for a
>
"Salinity" unit (a very fundamental unit in oceanography)? I mean, we can
>
not put all units used in the world, so we probably need to define a
>
criterion for inclusion. What is that criterion?
>
>
Martin
>
>