[Tagging] Deprecating phone=* in favor of more ambiguity in the database
Robin Burek
robin.burek at gmx.de
Fri Jan 28 21:32:44 UTC 2022
"Richard Fairhurst" richard at systemed.net – 28. Januar 2022 19:59
> It isn’t a hot topic for “people". It’s a hot topic for Soren. There is already a consensus within the wider OSM community that there’s nothing wrong with the phone= tag, it’s just that Soren refuses to accept any viewpoint other than his own.
That's where you're so wrong. It may not be the case here, but on other channels this issue is raised by all kinds of people. Maybe you're not aware of it, but it's possible. Not me and apparently not Sören.
It's also not about the obsessive preference for one scheme, but the resolution of the double use. Because that's the consensus I take most ehen, that the coexistence of phone=* and contact:phone=* suck. And it leads to problems.
And I've been following the trials and in the multiple approaches there's clearly been a bias towards the contact:* scheme rather than the pure phone=* (65% must have been at the last proposal). And that's why I support this attempt to finally resolve this contradiction. Because one could easily solve this problem and simply arrange for an either/or vote. Because at some point you have to decide which scheme should be preferred.
And yes, OSM may not have the beautiful data structure that you would have in a new project today. But two keys describing the same thing has nothing to do with beautiful or unbeautiful, but simply a mistake that should be cleaned up. Better yesterday than today. But here I only notice blockage instead of productivity.
More information about the Tagging
mailing list