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

[Martin Koppenhoefer]

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=guest_house.
> The only solution is to split the object (e.g. 2 separate nodes).


there are other solutions like opening_hours:pub=*

I do not like them personally because they are different tags on their own 
rather than standard tags, but people use them a lot. Personally I prefer 
making 2 objects in these cases.

Cheers 
Martin
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[Malcolm Herring]

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=*


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[Friedrich Volkmann]

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:compensation key in
order to just use donation:compensation:something=yes/no. This would be
consistent without a need for semicolons, although I prefer the semicolon
values anyway because they come with shorter keys.

> 1) For me the major problem is when you try to further specify the
> semi-colon separated values.
> E.g amenity=pub;hotel, how do you specify different opening hours for the two 
> ? 

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=guest_house.
The only solution is to split the object (e.g. 2 separate nodes).

-- 
Friedrich K. Volkmann   http://www.volki.at/
Adr.: Davidgasse 76-80/14/10, 1100 Wien, Austria

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[Marc Gemis]

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
> easily make a list with booleans of all the values that are present in
> the tag?
>

My take on this one

1) For me the major problem is when you try to further specify the
semi-colon separated values.
E.g amenity=pub;hotel, how do you specify different opening hours for the
two ?

You might use it for values that do not have to be specified further, e.g.
cuisine or your compensation tag, but
1) it's easier to do a search for all places that accept vouchers when you
have a dedicated key. With semi colon approach you need to be able to
handle "voucher", "xx;voucher", "voucher;xx", "xx;voucher;yy"
You might need to use regular expressions when you need to query for places
that give vouchers but do not do payments.
2) in some cases the semi-colon might be part of the value

You might want to search the archives of the tagging mailing list for all
kinds of arguments. I think this was discussed earlier this year as well.
O, yes, I remember  a very long discussion with Xxxmzz (or so) on pro- and
cons for regular expressions.


regards

m
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[Ruben Maes]

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 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
easily make a list with booleans of all the values that are present in
the tag?

1: donation:compensation=yesdonation:compensation:payment=yes
donation:compensation:vouchers=yes
2: donation:compensation=payment;vouchers
-> "compensation": true, { "payment": true, "vouchers": true }
(possible result in the memory of a parser)

1: donation:compensation=yesdonation:compensation:vouchers=yes
2: donation:compensation=vouchers
-> "compensation": true, { "payment": false, "vouchers": true }

1+2: donation:compensation=no
-> "compensation": false, { "payment": false, "vouchers": false }

Is there perhaps a significant performance drawback to having to parse
semicolon lists or what am I missing?


[1] wiki.osm.org/wiki/Semi-colon_value_separator explains you should
use the namespaced approach, but not why


2015-07-12 20:12 GMT+02:00 Ruben Maes :
> Voting is now open on the modified proposal:
> https://wiki.openstreetmap.org/wiki/Proposed_features/Blood_donation_2

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging