The semi colon approach has been a method in use for many years now, but it's generally avoided. Unfortunately we don't have database normalisation with our tagging system. The Keys must be unique. Previous version of the API allowed keys that were not unique, however nothing used it as the editors generally didn't support it, and it would give unpredictable results when coming to things like rendering, as either one would be used.
Shaun On 13 Nov 2009, at 04:09, Chris Hunter wrote: > That's what database normalization addresses. BTW, this is the first time > I've heard of the semicolon approach. > > On Thu, Nov 12, 2009 at 7:49 PM, Russ Nelson <nel...@crynwr.com> wrote: > > Unfortunately, that doesn't work. The tags must be unique on the name > side. That's why you see name, name_1, name_2. > > -- > --my blog is at http://blog.russnelson.com > Crynwr supports open source software > 521 Pleasant Valley Rd. | +1 315-323-1241 > Potsdam, NY 13676-3213 | Sheepdog > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
