The latest release of the COVESA VSS domain model introduced a breaking change
Units Updates
celsius changed to Celsius (backward incompatible change)
Fahrenheit and some other units added
mpg unit deprecated
The meaning of the unit did not change. However, as a result, models that were using an older COVESA VSS as a reference would need to replace celsius to Celsius. This is non-trivial when multiple users already depend on that. Especially if private branches were specified based on an old units file. So it won't be about only updating public references.
Hence, the proposal is that the tools reserve the characters of the unit key, being flexible about the naming case. For example:
celsius = CELSIUS = CELSius = CeLSiUs = ... etc.celsius != celsiusDegrees != degreecelsius != gradosCentigrados != ... etc.
So, when loading and processing the units, the tools can simply normalize them to avoid errors. For example: converting to upper case.
The latest release of the COVESA VSS domain model introduced a breaking change
The meaning of the unit did not change. However, as a result, models that were using an older COVESA VSS as a reference would need to replace
celsiustoCelsius. This is non-trivial when multiple users already depend on that. Especially if private branches were specified based on an old units file. So it won't be about only updating public references.Hence, the proposal is that the tools reserve the characters of the unit key, being flexible about the naming case. For example:
celsius = CELSIUS = CELSius = CeLSiUs = ...etc.celsius != celsiusDegrees != degreecelsius != gradosCentigrados != ...etc.So, when loading and processing the units, the tools can simply normalize them to avoid errors. For example: converting to upper case.