Why unrestricted double for acceleration readings?

[dontcallmedom]

When the spec was switched from separate reading interface to include it in the main one, the types of the x, y, z attributes were switched to **unrestricted** double - what is the reasoning behind the change? I didn't find anything related to Infinity in the spec, nor did I easily find any supporting model consideration in the generic sensor spec, nor in the motion sensors spec.

if there is a good reason, I think it should be documented, possibly in the 3 docs; if there isn't,

[alexshalamov]

@dontcallmedom Good point, there are no practical reasons to keep unrestricted double, as there are no sensors that could measure physical properties of +-Infinity magnitude. We should use double.

@pozdnyakov wdyt?

[pozdnyakov]

Think it was supposed to mean "unset value" but now the reading properties are nullable so no need to keep them unrestricted.

[pozdnyakov]

Think same applies to other concrete sensor classes (Gyroscope, Magnetometer, ..)