On Tue, Jan 27, 2009 at 04:36:08PM -0500, Matthias Julius wrote: > > This doesn’t account for multiple names in the same language, though. I > > can also imagine a place having several old names over time, while > > old_name=* really only allows for one. > > IMHO there really needs to be a well defined mechanism that allows a > tag to have multiple values. To invent new keys like old_name_1 and > old_name_2 is certainly not optimal. > > The FAQ has the recommendation of separating multiple values with a > ';' and to enter a semicolon that is part of the data as ';;'.
I think multiple keys with the same name should be allowed for a node/way/relation. AFAIK it’s only the editors that don’t currently let you do this. > That's actually error prone if someone enters a semicolon who doesn't > know about the rule. I think that should better be reversed or '\;' > be used as separator because this is much less likely to appear in > regular data. Almost any character could appear in regular data, unless it’s quite a special character—say, rather appropriately, the unit separator (US, ASCII 0x1f). The problem then is entering the special character. Ultimately the user should not have to care what, or if a, separator is used, and they would be presented with multiple values as appropriate for the interface they are using. Simon -- A complex system that works is invariably found to have evolved from a simple system that works.—John Gall
signature.asc
Description: Digital signature
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
