<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Yes, if a Derivative Database was created in the first place, and
that is not clear at all, see:</p>
<p><i>“Derivative Database” – Means a database based upon the
Database, and</i><i><br>
</i><i>
includes any translation, adaptation, arrangement, modification,
or any</i><i><br>
</i><i>
other alteration of the Database or of a Substantial part of the</i><i><br>
</i><i>
Contents. This includes, but is not limited to, Extracting or</i><i><br>
</i><i>
Re-utilising the whole or a Substantial part of the Contents in
a new</i><i><br>
</i><i>
Database.</i></p>
<div class="moz-cite-prefix">Essentially the question is if the
envelopes of the extracted points are a substantial extract of our
data (because they represent the residual information/data from
OSM), while it is obviously possible to construct cases were this
would be the case, in the typical relatively sparse POI scenario I
don't quite see that. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I don't particularly like engaging in
these discussion because they tend to end up being arguments about
how many angels can stand on a pin and are not answerable outside
of the detailed specifics of the actual use case (which are
typically not available).<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Simon<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 12.12.2019 um 20:05 schrieb Nuno
Caldeira:<br>
</div>
<blockquote type="cite"
cite="mid:CAK5cRsoFeOjj-toLXuN4L5KLcLVn9Ta_EB_pprE1emsis-ev2w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto"><a
href="https://opendatacommons.org/licenses/odbl/1.0/index.html"
moz-do-not-send="true">https://opendatacommons.org/licenses/odbl/1.0/index.html</a>
<div dir="auto">the license is quite clear and 4.2 applies to
the case you mention. any use of OSM data (over 100 nodes)
combined with proprietary data results in more open data under
ODbL. </div>
<div dir="auto">we are here to create more open data, not to
feed proprietary data than is lock under their TOS. </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 12 Dec 2019, 18:53 ,
<<a href="mailto:matthias.straetling@buerotiger.de"
moz-do-not-send="true">matthias.straetling@buerotiger.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">> From a
practical point of view, boundaries in OSM rarely originate
from surveys,<br>
> you might be lucky to be able to identify the original
source (most likely open data)<br>
> which may have a more liberal license than ODbL (check
the history and changeset<br>
> source tags / object source tags).<br>
<br>
But I neither want to merge OSM data or add it to my data. I
just want to use it to<br>
select points of my dataset.<br>
<br>
_______________________________________________<br>
legal-talk mailing list<br>
<a href="mailto:legal-talk@openstreetmap.org" target="_blank"
rel="noreferrer" moz-do-not-send="true">legal-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/legal-talk"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/legal-talk</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
legal-talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/legal-talk">https://lists.openstreetmap.org/listinfo/legal-talk</a>
</pre>
</blockquote>
</body>
</html>