TrafficDefinition for TrafficSinkAction

User manual description of TrafficDefinition for TrafficSinkAction says:

An optional TrafficDefinition of a sink is the equivalent of a blacklist, meaning that only vehicles matching this list will be removed while all other vehicles may pass unhindered.

However, the traffic definition associates (mandatory!) weights with every VehicleCategory. The user manual contains no description of how these weights translate to choosing a vehicle to remove (and how it works when sink rate is provided). Moreover, TrafficDefinition also can contain ControllerDistributionEntries, which have their own weights.

Does that mean the vehicles removed by the sink should follow the distribution as simulation time approaches infinity? Is the controller distribution necessary in this case?

I.e., if we have a sink with

vehicleDistribution = [
   car: 0.333,
   truck: 0.5,
   van: 0.166,
]
controllerDistribution = [
   controller1: 0.333,
   controller2: 0.333,
   controller3: 0.333,
]

Does that mean we won't remove a car with controller4 active since it isn't listed in the distribution?

Does it mean we won't remove a car with controller1 active if considerably shifts the total ratio of removed vehicles that had controller1 active?

Keep in mind that if TrafficDefinition is given for TrafficSinkAction, the schema says there also has to be a controller distribution with at least one controller. It seems the traffic definition for traffic sink can be made very complicated, and yet there is no way to say "just remove all cars regardless of which controller they have active". I think the controller distribution in this case should at least be made optional, maybe even removed for TrafficSinkActions.