Vehicle Information API Draft : Data type & domains

Hello All

This is some remarks concerning the data domain/data type.  In my opinion 
it should be easier to developer to deal with only measurementUnit (SI). 
If an another mesurement Unit  is required, for example for displaying 
purpose or for aligment to regionnal settings,  it should be converted by 
a presentation layer . That way we may  avoid possible  ambiguity in the 
interface


==============================
interface SizeConfiguration
width, height length can be an integer in Millimeter.

vehicleSpeed
meter/second can be more accurate.  100,000 is to huge and can not be hold 
in a 16 bits unsigned short. 

EngineSpeed
100,000 is to huge and can not be hold in a 16 bits unsigned short. 65000 
as a max should be ok

PowerTrainTorque 
Range: 0 - 10,000,000 in 16 bits is not possible

interface TripMeter 
averageSpeed & fuelConsumption must be a float for accuracy
distance the range (0 - 100000000) is to huge to be hold by an unsigned 
short

interface diagnostic
unsigned short is not enough to store the max value of any attributes

interface Fuel
to be more accurate averageConsumption/fuelConsumedSinceRestart/ must be a 
float  (i.e. 4.7 / 100 km)

LanguageConfiguration 
if required, must be iso 639-1 in DOMString data type.  By the way this 
section is not require because it's part of the presentation 
layer.(Regionnal settings)

................................................ 
Sinceres salutations/Kind regards 
Daniel Jutras
Continental Automotive Rambouillet France SAS 
Business Unit - Infotainment & Connectivity
6 rue Jean Moulin - BP65 
F-78512 Rambouillet 
Tel. : +33 (0)1.34.57.77.07
Fax. : +33 (0)1.34.57.78.22 
E-mail daniel.jutras@continental-corporation.com
http://www.continental-corporation.com 

Please consider your environmental responsibility before printing this 
e-mail