consider changing preset value of classic;skating to classic+skating

[aceman]

This can be found in:

<item name="Skiing" icon="presets/skiing_downhill.png" type="node,way,closedway">
<link href="http://wiki.openstreetmap.org/wiki/Proposed_features/Piste_Maps"/>
<key key="sport" value="skiing" />
<combo key="piste:grooming" text="Grooming" values="classic,mogul,skating,classic;skating,scooter,backcountry" />

The wiki ​http://wiki.openstreetmap.org/wiki/Key:piste:grooming says classic;skating is deprecated. Taginfo seems to confirm the version classic+skating is used more: ​http://taginfo.openstreetmap.org/keys/piste%3Agrooming#values .

I don't know the reasoning, they seem the same to me semantically (';' is used for multiple values in a key, and that seems to be the case here).

[skyper]

I'd rather support the default and use a semicolon ; or is there any differences in meaning ?

Did not find much discussion about these tags at all and I would like them to use the ":lanes"-model instead of an own scheme for pistes.

Please, discuss this issue on tagging@osm.

[aceman]

Replying to skyper:

I'd rather support the default and use a semicolon ; or is there any differences in meaning ?

Which default do you mean here?

[skyper]

Replying to aceman:

Replying to skyper:

I'd rather support the default and use a semicolon ; or is there any differences in meaning ?

Which default do you mean here?

Sorry, I mean support value lists with semi-colon as separator and regard classic+skating as classic and skating leading to classic;skating

[anonymous]

Yes, I would also agree that "classic;skating" should be used. However taginfo says people use classic+skating much more and the wiki too :(

[aceman]

Comment 5 is from me.

[Don-vip]

I'd vote for a wontfix. People are just following the wiki or another tool limitation IMHO. I have always seen ";" as separator, not "+".

[skyper]

Replying to Don-vip:

I'd vote for a wontfix. People are just following the wiki or another tool limitation IMHO. I have always seen ";" as separator, not "+".

+1

Maybe have a warning or even an auto change ?

[aceman]

I am OK with whatever decision, just that it is documented in the bug tracker here.

[skyper]

Well than it is a won't fix