carrier hotels are multi-story affairs, is the case that all things are located on the same floor, room, cage, 'altitude' :) ? I would expect general location items (lat/long/city, etc.) to stay the same, but extensions to provide more detailed information could force people to use a different location element entirely so they can be precise. In the end i don't really care, it can have id/name, but I don't predict reuse on a grand scale. -jason On Aug 16, 2012, at 8:59 AM, Jeroen van der Ham <vdham@uva.nl> wrote:
I'm for solution 3 as well.
On 16 Aug 2012, at 14:45, Jason Zurawski <zurawski@internet2.edu> wrote:
I would prefer 4 (not sure why locations need a name or id … is there really that much intended re-use?), but can live with 3.
Yes there is much re-use, or at least other information that you want to attach to a Location object. And to do that, you need an id.
Just for saying that a number of devices are in the same location it is easier to use an ID.
To take a practical example, there are many different projects and owners who have hardware at StarLight. It makes things a lot easier if everyone can use an ID to refer to that location.
Jeroen.