<div dir="ltr">2014-08-28 0:08 GMT+02:00 Simon Poole <span dir="ltr"><<a href="mailto:simon@poole.ch" target="_blank">simon@poole.ch</a>></span>:<br><div class="gmail_extra"><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">
<br>
Given that Edward has written code that, as it seems, accurately<br>
determines the corresponding wikidata objects for a given OSM entity,<br>
I'm not quite clear on what the benefits of statically tagging the<br>
references on OSM objects is supposed to be. Wouldn't providing this as<br>
an API make a lot more sense with numerous added advantages (avoiding<br>
bit rot and so on)?<br>
<span class=""><font color="#888888"><br>
Simon<br>
<br>
</font></span><br>_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br>
<br></blockquote></div><br>This is a small subset of wikidata that may be added, in many cases (like missing location<br><div class="gmail_quote">on Wikipedia) it is necessary to add this tag manually after verification.<br>
<br></div><div class="gmail_quote">Note, I have no opinion whatever adding wikidata=* is a good idea.<br><br></div><div class="gmail_quote">Is it a copyright problem to compare data from Wikidata and OSM to generate list of problematic situations?<br>
</div>Is it OK to import names from Wikidata (usually name:foo are missing in OSM)?<br></div></div>