Re: [OSM-legal-talk] Importing from an application's user generated content

2016-01-28 Thread Frederik Ramm
Michael, On 01/28/2016 07:42 PM, Michael Ledford wrote: > I believe that > updating the OSM database upholds share-alike. Share-alike means that you have to make your derived database available under ODbL on request. If you regularly make sure your database contents go into OSM then you could po

Re: [OSM-legal-talk] Importing from an application's user generated content

2016-02-03 Thread Michael Ledford
On Thu, Jan 28, 2016 at 6:25 PM, Frederik Ramm wrote: > Share-alike means that you have to make your derived database available > under ODbL on request. If you regularly make sure your database contents > go into OSM then you could potentially say, if such a request occurs, > "it's all in OSM", bu

Re: [OSM-legal-talk] Importing from an application's user generated content

2016-02-03 Thread Simon Poole
Am 04.02.2016 um 04:07 schrieb Michael Ledford: > ... >> Worst case, if the data you upload contains copyrighted material and we >> cannot easily enough identify which of your data is tainted and which is >> ok, then *all* data you uploaded might have to be removed again. > And this is why I am a

Re: [OSM-legal-talk] Importing from an application's user generated content

2016-02-05 Thread Michael Ledford
On Thu, Feb 4, 2016 at 2:33 AM, Simon Poole wrote: > > Frederik has already touched on most of the points, however > > - in the business model you outlined it is your data and it is your > responsibility to be able to identify the individual sources of > contributions, the wholesale removal would