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

[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 asking as it seems like this might be a good
> method to improve some data inside of OSM while also gaining benefit
> from it myself. In this I'm trying to help OSM and not hurt it. It's a
> shame that one could potentially improve the data and not be able to
> actually contribute that back to OSM. I don't foresee people obtaining
> an OSM account so that the POIs could be uploaded directly.
>
> So am I to assume that I should stay away from this line of thinking?
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 only apply if you cannot do
that. Naturally you should actually contemplate how you would
remove/revert such a contribution if the need arises (not "somebody else
will clean it up" that is so popular).

- non-legal: from a project perspective, OSM works best for contributors
that experience first hand that what they just contributed is actually
useful (contrary to being told by people with a vested interest that
what you've done was useful, which you may or may not believe depending
on how gullible you are, but I digress). It is an important part of
getting hooked. At least it should be clear where their contributions
are going to end up and integration with OSM proper should be as fast as
possible.

Simon 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/legal-talk/attachments/20160204/27165268/attachment.sig>