<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 21, 2023, 15:08 by dieterdreist@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class=""><div class="" dir="ltr">Am Fr., 21. Apr. 2023 um 14:08 Uhr schrieb Andy Townsend <<a href="mailto:ajt1047@gmail.com" rel="noopener noreferrer" target="_blank">ajt1047@gmail.com</a>>:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div>On 21/04/2023 12:17, Mateusz Konieczny via talk wrote:<br></div><div> We're actually talking about the "long tail" of shop values - genuine, <br></div><div> perfectly descriptive, perfectly valid values, like "shop=whisky" that <br></div><div> someone mentioned on IRC this morning. Changing that to something <br></div><div> generic without recording the extra detail somewhere (and communicating <br></div><div> to data consumers where that extra detail has moved to) is essentially <br></div><div> low-grade vandalism - removing detail from OSM. It devalues the hard <br></div><div> work of the people who surveyed these things in the first place.<br></div></blockquote></div><div><br></div><div><br></div><div>whole-heartedly agree, it also makes it hard to impossible to "organically" introduce new classes/types via mapping, because as soon as you add it someone monitoring some qa tool comes along and changes the specific value to something established but not so specific or sometimes even not fitting. These activities are sometimes called "gardening", but in OSM it isn't completely clear what is weed and what is crop, so we better make it even clearer that this kind of "gardening" should not be performed.<br></div></div></blockquote><div dir="auto">I agree!<br></div><div dir="auto"><br></div><div dir="auto">shop=whisky (or shop=beer) should be either<br></div><div dir="auto">- documented as valid and welcome<br></div><div dir="auto">- handled by something like shop=alcohol alcohol=beer<br></div><div dir="auto">- left alone<br></div><div dir="auto"><br></div><div dir="auto">Retagging them to shop=alcohol and losing detail is not good way to spend time,<br></div><div dir="auto">flattening to shop=yes would be obviously even worse<br></div><div dir="auto"><br></div><div dir="auto">but we do not need (theorethical examples ahead this time)<br></div><div dir="auto">both shop=beer and shop=beers<br></div><div dir="auto">shop=piwo (shop=beer I guess)<br></div><div dir="auto">shop=monopolowy (shop=alcohol)<br></div><div dir="auto">shop=alkohol (shop=alcohol)<br></div> </body>
</html>