On https://www.eclipse.org/forums/index.php/t/1114212/ the discussion arose whether Aspect Models should support metric or imperial or both systems. While SAMM offers techniques (Either Characteristic and samm:curie for unit as property) to flexibly support both, this comes at an additional complexity on level of model, API & API consumption.
The best practice (see even google maps api spec using metres: https://github.com/googlemaps/openapi-specification/releases/tag/v1.22.3 ) is to do a conversion on a system/UI level, not API level.
Therefore add to recommendation that that best practice for units is to use the metric systems.
Justification: Simplification, system level user setting still possible, and exceptions to that recommendation can be performed by users of ESMF
On https://www.eclipse.org/forums/index.php/t/1114212/ the discussion arose whether Aspect Models should support metric or imperial or both systems. While SAMM offers techniques (Either Characteristic and samm:curie for unit as property) to flexibly support both, this comes at an additional complexity on level of model, API & API consumption. The best practice (see even google maps api spec using metres: https://github.com/googlemaps/openapi-specification/releases/tag/v1.22.3 ) is to do a conversion on a system/UI level, not API level.
Therefore add to recommendation that that best practice for units is to use the metric systems. Justification: Simplification, system level user setting still possible, and exceptions to that recommendation can be performed by users of ESMF