Currently the location binding support is based on an older Configuration Admin specification and always mandates the configuration location to exactly match the bundle location of the component to provide with the location.
This strict matching has been released in Configuration Admin 1.4 to allow for so-called multi-target locations starting with a '?' character. Such bindings are ignored if security is disabled and allows for "region" matching if security is enabled using a permission check on the bound location instead of comparing the target services bundle location.
In addition CA 1.5 introduces targeted PIDS. While these are not obviously intertwined features the implementing code overlaps a bit.