<html><head><style id="outgoing-font-settings">#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}</style></head><body style="background-color: rgb(255, 255, 255); background-image: initial; line-height: initial;"><div id="response_container_BBPPID" style="outline:none;" dir="auto" contenteditable="false"> <div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"> Putting appart this 'man' vs 'human' debate...</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">This reminds me a thinking I regularly have in minds: OSM shall have a way to tell all (registered) data users that "starting from yyyy/mm/dd following major change in the database will be applied following vote xxx from OSM community. Please see drawbacks, workarounds and recommandations for editors in wiki page www" . The idea would not be to trigger this mechanism every week but to be able to schedule few data scheme improvements in concertation with (and supervized by) a dedicated Working Group (DWG ? Or a contiunuous improvement wg ?). I think OSM already did it in the past and the wellspreading of its data shall not block us for improvements. Keys can be seen as arbitrary strings from a sw point of view but I think there is a benefit to have consistent keys, which may imply from time to time to review 10 years old tagging schemes. It can even simplify life of editors and data consumers.</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div> <div id="blackberry_signature_BBPPID" name="BB10" dir="auto"> <div id="_signaturePlaceholder_BBPPID" name="BB10" dir="auto">LeTopographeFou</div> </div></div><div id="_original_msg_header_BBPPID" dir="auto"> <table width="100%" style="border-spacing: 0px; display: table; outline: none;" contenteditable="false"><tbody><tr><td colspan="2" style="padding: initial; font-size: initial; text-align: initial;"> <div style="border-right: none; border-bottom: none; border-left: none; border-image: initial; border-top: 1pt solid rgb(181, 196, 223); padding: 3pt 0in 0in; font-family: Tahoma, "BB Alpha Sans", "Slate Pro"; font-size: 10pt;"> <div id="from"><b>De:</b> dieterdreist@gmail.com</div><div id="sent"><b>Envoyé:</b> 18 octobre 2020 11:09 PM</div><div id="to"><b>À:</b> tagging@openstreetmap.org</div><div id="reply_to"><b>Répondre à:</b> tagging@openstreetmap.org</div><div id="subject"><b>Objet:</b> Re: [Tagging] Proposal to change key:man_made to key:human_made</div></div></td></tr></tbody></table> <br> </div><!--start of _originalContent --><div name="BB10" dir="auto" style="background-image: initial; line-height: initial; outline: none;" contenteditable="false"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am So., 18. Okt. 2020 um 23:02 Uhr schrieb Graeme Fitzpatrick <<a href="mailto:graemefitz1@gmail.com">graemefitz1@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div dir="ltr">On Sun, 18 Oct 2020 at 20:39, Rory McCann <<a href="mailto:rory@technomancy.org">rory@technomancy.org</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex">*definitely* not something one does auomatically.<br></blockquote><div><br></div><div>But would it be so impossible? (Not suggesting that it should actually be done!) <br></div><div><br></div><div>Couldn't a bot be set to simply find all cases of man_made=, regardless of what it is, & change them to human_made=, similar to using Find & Replace in a Word document?</div><div><br></div></div></div></blockquote><div><br></div><div>yes, technically it could be done with a bot or also without a bot, directly on the database, in seconds or less.</div><div>And once we have done it, we could do it again and again, for all kinds of reasons.</div><div><br></div><div>The problem is not the data at the origin, it is the system around the database.</div><div><br></div><div>Cheers.<br></div><div>Martin<br></div></div><br></div>
<!--end of _originalContent --></div></body></html>