[Tagging] Deprecation reasons - RFC

[Florian LAINEZ]

Hi,
The solution of associating both a standardized, easy-to-translate field +
a free text field seems to please everyone. I added it to the proposal.
Any other comment?

Le mer. 26 janv. 2022 à 17:23, Marc_marc <marc_marc at mailo.com> a écrit :

> Hello,
>
> Le 26.01.22 à 16:30, Mateusz Konieczny via Tagging a écrit :
> > So +1 to complementary free text entry for more details
>
> I had started the translation many months ago.
> Having free text at this location led to 2 problems:
> - the incorrect justification of depreciation (I don't agree with the
> current criterion of "poorly documented tag" since in this case the
> documentation should be completed. Once this is in order, we arrive
> either at a well documented tag without any problem of use or at a tag
> having several meanings or other problems making its use impossible
> which could lead to a depreciation)
> - translating 50x the same string, it's a waste of human time. there is
> only a limited number of reasons to deprecate a tag with 0, 1 or several
> replacement tags, no need to invent 50x different strings to say the
> same thing.
> I finally gave up for this double reason. and to see these 2 points
> improving seems to me very positive for the quality of the data and the
> documentation
>
> Regards,
> Marc
>
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220129/5758df87/attachment.htm>