Re: [Tagging] Feature Proposal - RFC - (Phone)

[Valor Naram]

Are you a datauser Paul Allen? Because I hate doing replacements, they ugly and they are work I hate. Replacements make Queries more ugly and longer.
Replacements also make the database less reliable, that's literally the opposite of what OSM mappers actually want.

AND

EXAMPLE SCENARIO: I look for a way to list all pois with phones. I find the wikipage for the `contact:phone` key. I start to use it in my query. I do not get all data and I think OSM has not good coverage for phone numbers as I thought. In this situation OSM is less reliable to me.

My example scenario shows a datauser (in this example myself) who missed out the wikipage "phone" and just took the first one "contact:phone". That means some data is hidden from me. And datausers don't have the idea to search for a second wikipage which describes another way of tagging phone numbers because it's logial to have one aggreement on storing data and not one. Two or more ways of storing literally the same thing is what I call inconsistent and bad for database usage.

~ Sören Reinecke alias Valor Naram

-------- Original Message --------
Subject: Re: [Tagging] Feature Proposal - RFC - (Phone)
From: Paul Allen
To: "Tag discussion, strategy and related tools"
CC:

On Sun, 6 Oct 2019 at 20:35, Sven Geggus <li...@fuchsschwanzdomain.de> wrote:

I fully agree with this.  In opencampingmap POI database I currently do a
replacement of the following tags during database import:

booking -> reservation
contact:phone -> phone
contact:fax -> fax
contact:website -> website
contact:email -> email
 
Would be nice to get rid of stuff like this.

Maybe, maybe not (I'm on the fence).  I doubt you'll manage to.  There are too many

on both sides who insist that their way is the one true way.  It's possible that your

kluge is actually the best way of handling things like this.  Data consumers can translate

contact:phone to phone or phone to contact:phone or leave both untouched as they

choose.  One problem with enforcing a single tag by mappers or preprocessing

data before putting it in the database is that if there are subtle distinctions they are

forever lost.  You can always scramble an egg but you can't unscramble one.

--

Paul

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