How to handle long VSS names?

[erikbosch]

This is a topic originating from the Porto AMM

Problems:

• Full dot-notated name of VSS signals can sometimes be very long
• Generating unique id (UUIDs) is sometimes not a solution if you want a SDK with understandable names
  This issue is to collect ideas on how this can be approved.

Some initial Ideas:

• Possibility to specify alias with unique names on branches and/or signals

I.e. Vehicle.Powertrain.Transmission.IsElectricalPowertrainEngaged has an alias alias: IsElectricalPowertrainEngaged. Solutions/Services may support full name, alias or both. Name must be unique.

• General overhaul of Paths to make them shorter, like Veh.PwT.Trans.IsElecPwTEng

• Support a label: xxxx keyword to give a possibility to specify a longer name for this node. Like if branch id is PwT, then it can have label: PowerTrain. Could also be used for localization if needed.