<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div id="AppleMailSignature">sent from a phone</div><div><br>On 25. Aug 2018, at 15:46, Paul Allen <<a href="mailto:pla16021@gmail.com">pla16021@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div class="gmail_quote"><div text="#000000" bgcolor="#FFFFFF">[lutz]</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" preoffsettop="928"><div text="#000000" bgcolor="#FFFFFF">Thanks. He has already responded in this thread as the one who has
chosen historic=memorial + memorial=plaque + plaque=stolperstein (as
opposed to 4 others who prefer historic=memorial +
memorial=stolperstein):<br></div></blockquote></div><div class="gmail_quote"><br></div><div class="gmail_quote">Since lutz is the main driving force behind heritage=* and historic=* and related tagging, his opinion is informed. </div></div></blockquote><br><div><br></div><div>there is no definition for the plaque tag and I am not able to deduct a system by looking at the values:</div><div><a href="https://taginfo.openstreetmap.org/keys/plaque#values">https://taginfo.openstreetmap.org/keys/plaque#values</a></div><div><br></div><div>Most used value is “metal” which would fit for a stolperstein as it is quite unspecific. (no plaque=stolperstein yet). metal=stolperstein??? Would mean we would have to add 4 tags for a stolperstein, as opposed to the current alternatives each with 2 tags:</div><div>historic=memorial </div><div>memorial=plaque </div><div>plaque=metal </div><div>metal=stolperstein </div><div><br></div><div>-1</div><div><br></div><div><br></div><div>Cheers,</div><div>Martin </div></body></html>