<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
I think you are clearly illustrating why we are wary of opening the
can of worms bending the definitions of the ODbL creates. <br>
<br>
So now we not only have to take the leap of faith that geo-coding
creates a produced work*, we have to expand the definition of
substantive to allow essentially complete country extracts to be
non-substantive.<br>
<br>
The later naturally makes the former unnecessary, so we might as
well simply propose that geo-coding creates a non-substantive
extract (which has been suggested btw in a different forum and is in
discussion in the LWG). In a way I would actually support this if
geo-coding was a clearly and tightly defined process, which, as I've
pointed out earlier, it isn't. <br>
<br>
Simon<br>
<br>
* I'm not convinced that this solves anything since derivative
databases used to produce a publicly used produced work are subject
to SA<br>
<br>
<br>
<div class="moz-cite-prefix">Am 27.09.2015 um 23:54 schrieb Alex
Barth:<br>
</div>
<blockquote
cite="mid:CABxUzDtrwEmuEysXUPFUNigFNsCdXPkwp1BSG1RFDRAsQ=DV7g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Sep 22, 2015 at 7:38 PM, Paul
Norman <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:penorman@mac.com" target="_blank">penorman@mac.com</a>></span>
wrote:<br>
<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">
<div style="overflow:hidden">On 9/22/2015 4:26 PM, Alex
Barth wrote:<br>
<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">Overall,
I'd love to see us moving towards a share alike
interpretation that applies to "<span>OSM</span> as
the map" and allows for liberal intermingling of
narrower data extracts. In plain terms: to
specifically _not_ extend the ODbL via share alike to
third party data elements intermingled with <span>OSM</span>
data elements of the same kind. E. g. mixing <span>OSM</span>
and non-<span>OSM</span> addresses should not extend
ODbL to non-<span>OSM</span> addresses, mixing <span>OSM</span>
and non-<span>OSM</span> POIs should not extend the
ODbL to non-<span>OSM</span> POIs and so forth.<br>
</blockquote>
<br>
Turning this around, when do you think share-alike
should apply in a geocoding context?</div>
</blockquote>
</div>
<br>
<div class="gmail_extra" style="font-size:12.8px">If you
methodically use a geocoder to reverse engineer the
OpenStreetMap database, share alike would kick in. "Reverse
engineering OpenStreetMap" would need a better definition
and it would have to cover two dimensions:</div>
<div class="gmail_extra" style="font-size:12.8px"><br>
</div>
<div class="gmail_extra" style="font-size:12.8px">1.
Comprehensiveness (not just a "narrow extract" like
addresses, buildings or businesses, but rather a
comprehensive extract of the most important OpenStreetMap
features together)</div>
<div class="gmail_extra" style="font-size:12.8px">2.
Geographic size (e. g. a country)</div>
<div class="gmail_extra" style="font-size:12.8px"><br>
</div>
<div class="gmail_extra" style="font-size:12.8px">We could
establish these limits with an update to the community
guidelines for what's Substantial.</div>
</div>
<div class="gmail_extra"><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
<br>
</body>
</html>