<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I created the Proposal page<br>
<br>
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/ban_deprecated_tags">https://wiki.openstreetmap.org/wiki/Proposed_features/ban_deprecated_tags</a><br>
<br>
<u>This proposal wants to discourage the use of schemes in case
they have been labeled as deprecated and replacements have been
found for them. </u><br>
And nothing else this proposal will do. It strikes to "prohibit
new entries being made with the old key" (Cited from Anonymous but
said in another context). It mustn't be done by a strict ban but
it can be done by discouraging "new entries [from] being made with
the old key" (Cited from Anonymous but said in another context).
</p>
<div class="moz-cite-prefix">On 15.03.21 14:58, S??ren Reinecke via
talk wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1294017400.1421270.1615816686490@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="yahoo-style-wrap" style="font-family:Helvetica Neue,
Helvetica, Arial, sans-serif;font-size:13px;">
<div dir="ltr" data-setdir="false">Hello all,<br>
<br>
<div dir="ltr" data-setdir="false">I see on the wiki sometimes
the following message above wiki pages describing deprecated
tags/keys:<br>
<blockquote>
<div>
<p><i>This feature has been labeled as <b>deprecated</b>.
The recommended replacement is: <tt dir="ltr"
class="ydpb2d1b8b4mw-content-ltr"
style="background-color: rgb(238, 238, 255);
background-repeat: repeat; background-attachment:
scroll; background-image: none; background-size:
auto; font-size: 1em; line-height: 1.6;"><a
href="https://wiki.openstreetmap.org/wiki/Key:changing_table"
title="Key:changing table" rel="nofollow"
target="_blank" moz-do-not-send="true">changing_table</a>=*</tt>.<br>
The reason is documented in <a
href="https://wiki.openstreetmap.org/wiki/Deprecated_features"
title="Deprecated features" rel="nofollow"
target="_blank" moz-do-not-send="true">Deprecated
features</a>. You are still free to continue to
use or interpret this tag as you see fit since
OpenStreetMap does not have ???banned features???.
</i></p>
<i><b>Under no circumstances should you
(semi-)automatically change ???deprecated??? tags to
something else in the database on a large scale
without conforming to the <a
href="https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct"
title="Automated Edits code of conduct"
rel="nofollow" target="_blank"
moz-do-not-send="true">Automated Edits code of
conduct</a>. Any such change will be reverted.</b></i></div>
</blockquote>
<div><i><br>
</i></div>
<div><i><br>
</i></div>
<div><i><br>
</i></div>
</div>
<div dir="ltr" data-setdir="false">I have objections on the
part that OSM does not have a banned feature.</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false">OSM is a database and when
it comes to that, there are rules.</div>
<div dir="ltr" data-setdir="false">One of these rules is
preventing data reluctance. In the example of deprecation of
Key:diaper in order to push the much much better
Key:changing_table forward we recommend mappers not to use
the first key but the last key. In the same box we also see
that the mapper can also use the old Key:diaper tag. Well,
did you thought about the nonsense? Because developers will
only support Key:changing_table and not the Key:diaper
because we stick to standards and all others who do not will
fail. It would be complete nonsense to map Key:diaper
because no data customer will process that key, nor will
convert it to something usable. So that entry ends up in the
database for nothing and no other mapper will understand
what the key is all about. <br>
</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false">Refering to "Deprecated
features" wiki page (to cover Key:contact:phone vs Key:phone
example):<br>
"<span><span>Often expressed opinion is that in case of two
tags with exactly the same meaning deprecating one and
retagging objects is waste of time and energy and
disturbs mapping for no benefit.</span>"<br>
</span>
<div><span>- This opinion wrong and probably come from those
not understanding databases. Deprecation in case two
tags have exactly the same meaning is good and is an
improvement to the database. And it is also clearer for
newbies to decide whether to use tag A or B. For data
customers it is also easier because they don't need to
support two schemes meaning exactly the same. An
example: Key:contact:phone and Key:phone where I had
discussions with people not understanding databases and
ignoring my expertise. I study these things btw.</span></div>
<div><span></span><br>
</div>
<div dir="ltr" data-setdir="false">"<span>Often expressed
opinion is that in such case of tags with the same
meaning one should be quickly deprecated</span>"</div>
<div dir="ltr" data-setdir="false">
<div>- The word "quickly" shouldn't be used here. Also
deprecation of a duplicate tag should be done with care.
Quick might be your wrong partner there. So people
saying that, please reconsider your way of thinking.</div>
<div><br>
</div>
<div dir="ltr" data-setdir="false"><span><span>A "banned
feature" would be useful here (in case of the phone
thing) since two keys in use at the same time
meaning exactly the same. We then could ban the use
of Key:phone or Key:contact:phone and doing a duty
to our database.</span></span><br>
</div>
<br>
<br>
<div>So yes, we should ban certain features in favor of
newer and better schemes and where possible
automatically/manually convert these to the newer ones
to keep the database clean and the information conveyed
in these deprecated keys being useful still.</div>
<div><br>
</div>
<div dir="ltr" data-setdir="false">Cheers</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false">S??ren Reinecke alias
Valor Naram<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
</body>
</html>