Re: [Tagging] Multiple tags for one purpose

[Valor Naram]

> Editors won't (in general) implement tags in presets unless they're widely used.  Unless editors and carto support tags, they won't get widely used, so editors and carto won't support them.  Chicken and egg.

Yes, you're right. But I was the author of "changing_table" and the guy who lead it throw the proposal process and also Moderator of the discussion and votes. And contacting all the editors was no problem and they implemented "changing_table" and deleted "diaper" presets. See JSOM, OSMand, Vespucci and also iD. My effort shows that working together with different groups works.

I would highly appreciate it when you give me a chance. In real life people are revelling their secrets to me because they trust me and I give them the feeling of being accepted as they are. It includes my talks with people from different worlds. More-Than-One-World Secrets. This connection I can try to create also among OSM folks (societies).

Best regards

Sören Reinecke alias Valor Naram

-------- Original Message --------
Subject: Re: [Tagging] Multiple tags for one purpose
From: Paul Allen
To: "Tag discussion, strategy and related tools"
CC:

On Sat, 24 Aug 2019 at 17:06, Valor Naram <valin...@gmx.net> wrote:

In my opinion this is a topic we should consider working on and creating a wikipage to describe the "defragemtation" process in general.

Doing so is probably not going to achieve much.  First we need to defragment OSM itself.

It doesn't matter what wonderful tags we come up with here, if carto refuses to render them

then they won't get used.  It doesn't matter what wonderful tags we come up with here, if editors

don't implement them as presets they won't get used.

Carto won't (in general) render a tag unless it's widely used.  Editors won't (in general)

implement tags in presets unless they're widely used.  Unless editors and carto support

tags, they won't get widely used, so editors and carto won't support them.  Chicken and egg.

There are complications (of course).  Carto (in general) refuses to implement aliases, so

whatever the merits of deprecating landuse=grass in favour of landcover=grass, carto will

refuse to render landcover=grass.  Editors don't (in general) like implementing aliases

either.  So however much we wish to try to fix bad tags, which are frequently misused

because the name or value was a bad choice, it probably won't happen.  Some editors

occasionally decide they'll ignore the list, the wiki, and carto, and go their own way

(sometimes they get their way and sometimes they get a slap on the wrist).

So what we need at this stage is not a defragmentation process but joined-up thinking

between the various groups.  I'm not holding my breath on that one.

--

Paul

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