<div dir="ltr">I'm not sure what basis there is for thinking a service provider will necessarily reuse clients' data. Maybe! That's not my experience, but I can imagine how it might be useful. I hope you'll agree that data security and stewardship is a trickier thing to implement within an open project made up of volunteers than it is in an organization with contract employees.<div><br></div><div>To point b: if the addresses remain associated with the entity doing the geocoding, as I think you're proposing, problematic linkages remain possible. Consider how Brendan Eich's career ended at Mozilla. That case involved campaign finance records, but a political organization's geocoded membership database could easily achieve the same result, even with just addresses.</div><div><br></div><div>Anyway even if the organization->address linkage were to be removed, organizations who comply with EU Safe Harbour privacy requirements (and, I assume, the EU privacy provisions from which they're derived) could not share users' address data with a third party in this manner*.</div><div><br></div><div>Put bluntly: expecting data back from geocoding users is not workable and never has been. Maintaining the hope that someday it will produce useful contributions merely leads to some noncompliance and lots and lots of deadweight loss. It's a shame, and is inhibiting useful work being accomplished both outside of OSM and within it.</div><div><br></div><div>Tom</div><div><br></div><div>* Partner and vendors can receive data from complying organizations, but the relationship must be disclosed and users must be given the right to delete data about them. Partner organizations also have to complete certification procedures (including things like HR training), and may not pass the data on further, as OSM presumably would want to under sharealike.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 23, 2015 at 10:39 AM, Simon Poole <span dir="ltr"><<a href="mailto:simon@poole.ch" target="_blank">simon@poole.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div>Am 23.09.2015 um 15:32 schrieb Tom Lee:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8px">why wouldn't you </span><span style="font-size:12.8px">want to provide OSM with a list of
addresses that you tried to geo-code </span><span style="font-size:12.8px">(successfully and non-successfully)</span></blockquote>
<div><br>
</div>
<div>To use an extreme but hopefully illustrative example,
consider the queries used to create the thematic map on this
page:</div>
<div><br>
</div>
<br>
</div>
</blockquote>
Naturally you fail to mention that<br>
<br>
a) whatever service provider did the geo-coding of the above data
undoubtedly used the data for the same purposes as OSM would (and
likely a lot more)<br>
<br>
and<br>
<br>
b) in my proposal I specifically address the issue of providing the
geo-coded addresses anonymously <br><span class="HOEnZb"><font color="#888888">
<br>
Simon<br>
</font></span><br>
PS: just to avoid confusion we are talking about addresses without
any attached personal information (names etc), so the data
protection issue is sole the linkage between who is doing the
geo-coding and the address. <br>
</div>
<br>_______________________________________________<br>
legal-talk mailing list<br>
<a href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/legal-talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/legal-talk</a><br>
<br></blockquote></div><br></div>