[Osmf-talk] [OSM-legal-talk] New license proposal status II

Mike Collinson mike at ayeltd.biz
Thu Dec 3 12:19:40 UTC 2009

At first reading, I think the answer is as follows.

- "Unfriendly Map Corp" is obligated to and does release their data under ODbL

- Whether friendly or unfriendly, they never have any obligation to merge in their data improvements into our database.

- However, you or I can.

Does that make sense?

The key will be clause 1 of the Contributor Terms[1] allowing you or I to do.  Is the ODbL license itself explicit permission from them? I'll bring it up for review at an License Working Group in the light of your question.


[1] http://www.osmfoundation.org/wiki/License/Contributor_Terms

At 12:49 PM 3/12/2009, James Livingston wrote:
>On 03/12/2009, at 6:12 AM, Mike Collinson wrote:
>>We have now fully updated the "OSM Contributors agreement" section of the main proposal. I hope that meets concerns about clarity of the change-over process.
>A while ago on the legal-talk list I mentioned that the contributor terms didn't quite sit right with me, although I know why we want them to help lessen the pain of re-licensing in the future. Thinking about it again after reading the above, I think I've figured out what was sticking in my craw.
>The reason (well, my version) for a share-alike licence is that people who use OSM data have to release theirs, we can merge that in, and everyone benefits from the extra data going around. ODbL help that because (I'm serious hoping) that we could combine two ODbL-licensed data sets together into a new ODbL-licensed data set. However I think that requiring the contributor terms would prevent that from working properly.
>Consider "Unfriendly Map Corp" which fulfils it's legal obligations, but doesn't go out of their way to be nice to us, and that they combine OSM data with their own to produce something they distribute. They release the combined data as required by the ODbL, however unless they agree to the contributor terms (which they don't have to), we can't take that combined data and bring it back into OSM without giving up the ability for easy re-licensing.
>Am I missing something here?  From what I can make out, using the ODbL to force people to release combined data doesn't mean we can do anything with the result.

More information about the osmf-talk mailing list