Re: [Tagging] Multiple values with semicolons (was: Voting - Blood donation 2)

sent from a phone > Am 20.07.2015 um 22:45 schrieb Friedrich Volkmann : > > That has nothing to do with semicolons. It's a general problem with tag > combinations. Say, if you use pub=yes + hotel=yes, you still cannot specify > different opening hours. Same thing with amenity=pub + tourism=gues

Re: [Tagging] Multiple values with semicolons (was: Voting - Blood donation 2)

On 20/07/2015 21:45, Friedrich Volkmann wrote: The only solution is to split the object (e.g. 2 separate nodes). Not so - a tag of the form := would allow more than one object to be separately tagged on the same node or way. e.g.: pub:opening_hours=* hotel:opening_hours=* _

Re: [Tagging] Multiple values with semicolons (was: Voting - Blood donation 2)

On 20.07.2015 10:55, Marc Gemis wrote: > On Mon, Jul 20, 2015 at 10:32 AM, Ruben Maes > wrote: > > He proposes to use a semicolon-separated list, e.g. > donation:compensation=payment;vouchers. There is also a third option: Dropping the pure donation:compens

Re: [Tagging] Multiple values with semicolons (was: Voting - Blood donation 2)

On Mon, Jul 20, 2015 at 10:32 AM, Ruben Maes wrote: > He proposes to use a semicolon-separated list, e.g. > donation:compensation=payment;vouchers. > We both know this is controversial, but why in fact?[1] It is supposed > to be hard to interpret for data consumers, but can't they just as > easil

[Tagging] Multiple values with semicolons (was: Voting - Blood donation 2)

Fkv voted no on Blood donation 2 because he believes the donation:compensation:* keys will cause inconsistencies, e.g. donation:compensation=no together with donation:compensation:payment=yes. I can see his point though I don't think it would happen often. He proposes to use a semicolon-separated