Re: [Tagging] Remove non-prefixed versions of 'contact:' scheme

[Sören alias Valor Naram]

I didn't heard any good reason why not to change to `contact:` scheme.


~ Sören Reinecke alias Valor Naram

-------- Original Message --------
Subject: Re: [Tagging] Remove non-prefixed versions of 'contact:' scheme
From: Marc Gemis
To: "Tag discussion, strategy and related tools"
CC:

Are you planning on repeating this request every 5 months?

I thought https://wiki.openstreetmap.org/wiki/Discussions/tagging/contact:phone_or_phone
failed.
Wasn't the outcome about 50-50? How will you ever convince half of the
voters to accepts the other scheme?


regards

m

On Mon, May 4, 2020 at 12:55 PM Valor Naram via Tagging
wrote:
>
>
> I request to replace all occurrence of the non-prefixed versions of the contact keys like Key:phone, Key:email. Key:website to be replaced with the prefixed ones like Key:contact:phone, Key:contact:email, Key:contact:website . The current situation harms our database in a way that makes our data less useful. In order to be successful we need to standardize to the contact:
> prefix. No more multiple keys for the exact same purpose with just
> different names! Make tagging more orthogonal! As someone who has
> experience in database and normalisation it hurts to see that mappers
> don't know how to take care of a database. It is time to take action and
> to clean up so OSM data gets more useful.
>
>
> Having two keys for the same purpose (the current behaviour) has no advantages but many disadvantages:
> * Data customers need to be aware of both tags to cover all
> requested and available information. So to get telephone numbers they
> need to look for Key:phone and Key:contact:phone . This makes a bad
> impression.
>
> * Normalisation of that data is required. Key:phone must be
> translated to Key:contact:phone or backwards. It is good to prevent the
> need of normalisation through standardisation as far as possible to
> prevent errors and misinterpretations from happening.
>
> * Having two schemes leads to confusion of mappers (especially
> for newbies) which they should use. Some need clear guidance ( e.g. On
> request I created a translation table for mappers of the old diaper key
> to help them to switch to the new Key:changing_table as you can see
> here: https://wiki.openstreetmap.org/wiki/Key:changing_table#Comparison_with_the_deprecated_diaper.3D.2A_key . I also notified some of the mappers and stakeholders about that change)
>
> See also:
> https://github.com/openstreetmap/iD/issues/7566
> https://josm.openstreetmap.de/ticket/19184
> OpenStreetMap contact schema unification
>
> --
> ~ Sören Reinecke alias Valor Naram
>
>
> Developer (not Founder) of the Babykarte: https://babykarte.github.io
> Participating in "MapDiscover" project: https://mapdiscover.org
> "Community Support" for Trufi Association:
> https://trufi-association.org
> Documentation for Trufi Communities on mapping bus routes:
> https://github.com/trufi-association/mapping-documentation
>
>
> Ein Gag zu Hamsterkäufen: https://klopapier.mapdiscover.de
>
>
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging

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

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