[OSM-legal-talk] Updated geocoding community guideline proposal

[Alex Barth]

Also if we assume geocoding yields Produced Work the definition of
Substantial doesn't matter.

Taking a step back here. What do we want? From conversations around
dropping share alike my impression was that there was a consensus around
unlocking geocoding - even among share-alike advocates.

Just like how CC-BY-SA created a grey area around the SA implications for
the rendered map which wasn't good for OSM, ODbL does the same with
permanent geocoding. To make OSM viable for geocoding we can't have its
ODbL infecting the datasets it's used on.

There are tons of geodatasets out there waiting to be geocoded and we
should have clarity around the legal implications of doing that. More use
of OSM for geocoding means more incentives to keep and maintain geocoding
data (addresses, POIs, admin polygons) in OSM.

Alex



On Mon, Jul 14, 2014 at 11:34 AM, Paul Norman <penorman at mac.com> wrote:

>
> On 2014-07-14 8:15 AM, Martijn van Exel wrote:
>
>> On Mon, Jul 14, 2014 at 8:44 AM, Alex Barth <alex at mapbox.com> wrote:
>>
>>> This is also how I'm reading this. Obviously the sticky point is the
>>> definition of what's a database in this sentence: "systematically recreate
>>> a database from the process". You can't abuse geocoding to recreate
>>> OpenStreetMap without triggering share alike.
>>>
>> The definition of 'substantial' is key here, isn't it? In one of the
>> examples I added, the result of OSM-based geocoding actions would
>> potentially be stored on a client in a collection of 'favorites' together
>> with other favorites that may be the result of tainted geocoding. There's
>> really two questions here - 1) is this collection of favorites
>> 'substantial' and 2) does this mixed storage trigger share alike in an of
>> itself?
>>
>
> Given that any database of geocoding results is going to be clearly based
> upon the Database [OpenStreetMap], and that any interesting uses of OSM are
> probably going to substantial, I don't see the definition of it mattering.
>
> In most of the cases raised in the wiki page, there's a derivative
> database of geocoding results and some other non-derivative database of
> something not taken from OSM, e.g. non-OSM POIs with just an address. You
> then take this collection of data sources and create a produced work, e.g.
> a page showing what the user has showed.
>
> Once you start taking actual POI information from OSM, not just addresses,
> then your POI database will also be a derivative of OSM.
>
>
> _______________________________________________
> legal-talk mailing list
> legal-talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/legal-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/legal-talk/attachments/20140714/a9928857/attachment.html>