Developers who work with quantities (sensor reading from edge devices, scientific, engineering, medical, or manufacturing) need to handle measurements of these quantities in their programs. Inadequate models of physical measurements can lead to programmatic errors. In particular when modelling a measurement as a simple number with no regard to the units it represents creates fragile code. Another developer or part of the system can misinterpret the number as a different unit. For example, it may be unclear whether a person's mass is expressed in pounds, kilograms, or stones. A human reading „10°C“, „10 C“ or simply „10 Degrees“ may interpret each of those correctly. For M2M communication, unless a program contains a „Babel Fish“, such ambiguity would not be acceptable.
Don’t Panic: After programming languages like Ada, C++, Eiffel or F# added type-safe Unit support already, JSR 363, Units of Measurement API will add similar support to the Java Platform, making it competitive for M2M in the Internet of Things with strong emphasis on sensors.
This session provides an overview of popular use cases for the Units of Measurement JSR and implementations on both Java ME 8 Embedded (CLDC 8) and Java SE 8. A Hitchhiker’s guide across places where this JSR helps improve data quality or save lives by ensuring e.g. a patient receives the correct dosage of medicine or smart homes and similar energy saving measures prevents Earth from being destroyed by Global Warming (rather than waiting for a Vogon express route ;-)
40. Links
JSR-363
https://jcp.org/en/jsr/detail?id=363
Units of Measurement Project
http://unitsofmeasurement.github.io
Eclipse – Project UOMo
http://www.eclipse.org/uomo/
My GitHub account
http://www.github.com/keilw/
Hinweis der Redaktion
Briefly discuss what a rich client is. This is an opportunity to talk about all the pretty pictures, how making a selection in one view can change the appearance of others, drag and drop, yadda, yadda, yadda…