Good question. With the introduction of this JSON format, the sorting logic is embedded in the value itself, with highest matching priority on top. 

For Netflix internal usage, the dimension sorting will still work and can co-exist with this new approach. And I think for most use cases, people will still prefer the old way, i.e., define property with the matching deployment context dimensions and with only one value, and use this format for request context based attributes or if they want to define their own sorting logic.