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

[Valor Naram]

> 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.

Sven gave us a list of tags which have exact meaning. So no distinctions. No differences, just another names.

e.g. `phone` is the same like `contact:phone`. You could just find one difference: The name. And to have just the names different is a bad thing. In such cases we can make life a lot easier by just using one tag AND NOT two tags for the same purpose!


~ 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