Do you think we should restore behaviour so that `named.<somename>` should be used as the `location.getDisplayName()` if no other explicit name is given?

The "named location" name is no longer being used as the `location.getDisplayName()`. Instead it's just a name to refer to a location definition. Previously (as I recall) the two were conflated causing problems where if you did `localhost:(name="myname")`, it would lookup a named location called "myname" and get its properties - even though `brooklyn.locations.named.myname` could be for sometime entirely different to a localhost location.