Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-07-08 Thread Peter K
Hi there, I would like to have clarification on this subject as well (but be aware that I'm just in the process of understanding the OSM license -> see the other thread). What I do not understand with the OSM license is the following (constructed) example: * I have a separate geo coder applicat

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-24 Thread Jonathan Harley
On 14/06/13 07:09, Michal Palenik wrote: On Thu, Jun 13, 2013 at 03:58:22PM +0200, Olov McKie wrote: Geocoding and license implications Manual geocoding of an entity that a person has prior local knowledge of, is the same process as adding a new entity to the OSM, and as such the person geocod

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-17 Thread Jukka Rahkonen
Robert Whittaker (OSM lists writes: > > I'd still very much like to hear of potential use cases, where > regarding the "inputted search data plus returned coordinates" as a > derivative database (which may be part of a collective database with > other proprietary data in it) would actually caus

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-14 Thread Martin Koppenhoefer
2013/6/14 Olov McKie > I would suspect that if a license dispute about OSM ever end up in court, > we will not be able to argue for more copyright protection than what we > gave to those contributors who did not want the license to change. I would > also like to argue that, when a question comes

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-14 Thread Andreas Labres
On 07.06.13 11:07, Martin Koppenhoefer wrote: > At least for the "substantial" part of your question I believe if a > professional geo service provider like map box would decide to use OSM to > satisfy its geocoding needs, it is obvious that this use would be > "substantial", or you could use it on

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-13 Thread Michal Palenik
On Thu, Jun 13, 2013 at 03:58:22PM +0200, Olov McKie wrote: > Geocoding and license implications > Manual geocoding of an entity that a person has prior local knowledge of, is > the same process as adding a new entity to the OSM, and as such the person > geocoding the entity retains their full co

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-13 Thread Martin Koppenhoefer
On 13/giu/2013, at 15:58, Olov McKie wrote: > All other geocoding results in a Produced Work, IMHO it results in a Derivative Database, as long as the amount of data geocoded is not too small. Cheers, Martin ___ legal-talk mailing list legal-tal

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-13 Thread Robert Whittaker (OSM lists)
On 13 June 2013 14:58, Olov McKie wrote: > Manual geocoding > A person using an OSM map to find the latitude and longitude coordinates > associated with a point or an area, normally by clicking, drawing or > similarly marking where that point or area is on a map. As an example, the > process of

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-11 Thread Oliver K
2013/6/7 Alex Barth > > Over the past months, we've tried to get legal advice on this question. > This is difficult as the lack of existing case law makes it hard to get > official legal opinion on the document and the license is very complex. But > here is what we have heard back informally: > >

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-07 Thread Robert Whittaker (OSM lists)
On 7 June 2013 01:56, Alex Barth wrote: > With two State of the Map conferences coming up now and plenty of > opportunities for face time, I'd like to restart our conversation around > clarifying the ODbL's implications for geocoding and get to a result. Over > here at MapBox we're hoping to use O

Re: [OSM-legal-talk] Clarifying Geocoding and ODbL

2013-06-07 Thread Martin Koppenhoefer
2013/6/7 Alex Barth > 2. The ODbL is too vague in the definition of its terms, requiring > additional clarifications by licensor. This is most importantly the case > around the terms "derivative database" and what constitutes a "substantial" > extraction of data [3]. At least for the "substant