Daniel Alvarez-Coello
Daniel Alvarez-Coello
In the README, it says that > +--raw CAN: This not stored as a value array but as three seperate arrays [src, address, data] However, I did not see any...
### Discussed in https://github.com/COVESA/vehicle_signal_specification/discussions/533 Originally posted by **jdacoello** February 10, 2023 Is it possible to define the number of valid characters when using string datatype? One example would be to...
As far as I know, the `Instances:` field in VSS is meant to be applied to branches only. However, this in not practical when there will be only one property...
There are currently situations where a property is modelled (e.g., `Window.Position`). Then another property, that could be easily derived from the previous one, is also defined (e.g., Window.IsOpen) ```YAML Vehicle.Cabin.Door.Row1.Left.Window.Position:...
I see the following cases that are related with the lack of a formal (and explicit) machine-readable lookup tables: * Case A - The use of a predefined set of...
# The issue Considering the following: - The VSS tree uses a tree-like hierarchy to define the name paths of the vehicle data points. - A tree-like hierarchy can only...
Currently, there is no tool/script checking the correctness of the formats included in the specification files. For example: trilling spaces, letter capitalisation, blank spaces, indentation, quotation mark style, etc. What...
I see inconsistencies regarding the naming of branches. Most of the branches that can be instantiated are correctly named with the singular form (e.g., Door, Wheel, Window, etc.) However, there...
The current property naming convention can cause confusion when several branches exist, as it uses the same dotted notation for both branches and instances. # Simple scenario For example, the...
This PR addresses the issue described and discussed in #753 .