Layout of road functions in Roads.Interfaces.Base about vehicleinterfaces

[tobolar]

As far as I understand the current concept, the roads' functions are firmly coupled to a particular road. Thus, they shall not be directly accessible to a user. A road developer shall first declare the protected particular functions within a particular road and link them then to the base road functions.
So IMO the benefit of adding choicesAllMatching=true and collecting functions within tab="Functions" has effect only when linking the base and the particular functions. And this is generally done just at once when implementing a new road.
Or am I missing something?

[GarronFish]

In our case we are extending VehicleInterfaces.Roads.Interfaces.Base to create a road model. Then the road functions are redeclared. Clients using the VeSyMA road models requested that the road models we create have replaceable road functions as this allows them to create their road models without having to duplicate road models.
Previously we had firmly fixed these road functions, however even in this case we would like to improve the description string and tab option to make the models neater.

Is there a workaround that does not generate warnings?