I'm not sure about having spaces in the names, since these are just tokens to represent a location. I'd prefer using hyphens, and keeping everything lowercase here, since we have a display name that is set in the location metadata for pretty printing in the UI. This makes it simpler when providing a list of locations on the command line, since they can be unambiguously comma or space separated:

```
$ ./start.sh --location rackspace-london,amazon-california,cloudsigna-zurich
```

We could use the convention `provider-region` where *provider* is the first part of the company name in lowercase and *region* is a region identifier in lowercase, preferably the geographic location using the providers nomenclature, with hyphens instead of spaces.

The lines would then look like this:

```
brooklyn.location.named.rackspace-northern-virginia = jclouds:rackspace-cloudservers-us:IAD
brooklyn.location.named.rackspace-london = jclouds:rackspace-cloudservers-uk
brooklyn.location.named.amazon-virginia = jclouds:aws-ec2:us-east-1
brooklyn.location.named.amazon-dublin = jclouds:aws-ec2:eu-west-1
brooklyn.location.named.hpcloud-arizona-1 = jclouds:hpcloud-compute:az-1.region-a.geo-1
```