<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Apr 28, 2020, 21:27 by marc_marc_irc@hotmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Hello,<br></div><div><br></div><div>Le 28.04.20 à 19:14, Joseph Eisenberg a écrit :<br></div><blockquote><div>The original key amenity=* is a reasonable choice. This has been<br></div><div>confirmed with extensive usage of amenity=pharmacy by mappers and<br></div><div>database users:<br></div></blockquote><div><br></div><div>egg & chiken issue :<br></div><div><br></div><div>a proposal to depreciate a heavily used tag is rejected because some<br></div><div>people think that heavily used tags should be immutable, as long as they<br></div><div>are heavily used. so proposals do it in 2 steps: the new tag is proposed<br></div><div>as a complement during a transition period.<br></div><div><br></div><div>Contributors who want to see their addition on the default rendering<br></div><div>should continue to add the old tag. if they don't, someone else will. so<br></div><div>the old tag will never decrease.<br></div><div><br></div><div>Default style guardians have a "no aliases" dogma, making it impossible<br></div><div>to change tags.<br></div></blockquote><div>It is not impossible, but you need convince people to deprecate old tag.<br></div><div>See <br></div><div>amenity=emergency_phone -> emergency=phone<br></div><div>where rendering change followed tagging change<br></div> </body>
</html>