Please revert back instance handling with DriverSide/PassengerSide introduced with release 4

[BjoernAtBosch]

I don't feel this change helpful:

• It complicates iterating over the instances, e.g. for depicting the seats in a display - then one always has to find out if the car is left-hand or right-hand. If defining it as positions starting at 1, which is the leftmost seat, depicting the seats is much easier.
• What is "driver side" if the driver seat would be in the middle?
• The determination on ["DriverSide","Middle","PassengerSide"] is an unnecessary limitation to passenger cars (with max. 3 seats per row). What about busses/coaches (or vans), where you can have 4 seats per row?
• In many cases the position of the driver is irrelevant, but there you have to find out then, if "DriverSide" is on the left or right ...
• The position of the driver seat can be easily determined by "Vehicle.Cabin.DriverPosition" - whereupon I would extend that by a "row" for completeness (and flexibility)

[ppb2020]

Agreed.

[erikbosch]

Sorry for not seeing this earlier. There were a long discussion in the VSS project leading to the change where the change was driven by BMW and @adobekan. The rationale was that for many use cases position of the seat is irrelevant, like if you want to define a function that unlocks all doors if driver door is opened:

if < Door.Driverside.IsOpened)>
  for < all doors in vehicle>
    <unlock>

On the other hand, you can find use-cases where it makes more sense to refer to physical position of something. In both cases VSS has data so you can map between them.

Some time ago I created an issue at #642 for a more generic discussion. Maybe it would be useful to have a syntax so that you can access both through absolute position (like "pos1") and logical position (like "driverside"). With that one could be master and the other an alias