Hi Jonas,
Here's what I would do.
Section 3 of the license means that if BBN decides to do what you need to do to the OpenMap code, you can't claim ownership of those modifications after the fact.
If you take OpenMap code and change it to meet your needs, you have to comply with section 4 of the license, and I would rename the classes you change - put them in a different package, modify the name of the class, whatever. You can send those changes to openmap_at_bbn.com and make notes in the source code on what you changed (4a or 4c). You'd have to make the source code for that derived code available somewhere.
If you simply extend the class, you don't have to do anything for section 4. But you'd have to include openmap.jar in your application and that means you have to acknowledge that you're using OpenMap in the credits section of your app, basically doing (5a).
I think that's it.
Oh, yeah, btw, I'm not a lawyer. But I hope this helps,
- Don
On Feb 23, 2012, at 7:54 PM, Jonas Winkler wrote:
> Hello,
>
> I am in charge to work on an application for android devices, that includes a feature to export arbitrary data in Shapefile-format. I am looking forward to use components of OpenMap for this feature.
>
> Due to the specific nature of Android, I will probably need to apply minor changes to OpenMap (i.e. use the Android API for file writing). This application will get sold commercially.
>
> Is it possible to use OpenMap in such a scenario? According to the license agreement, a short notice (“Powered by OpenMap”) on a splash or about screen and a link to the website should be enough, but I am not sure.
>
> Cheers,
> Jonas Winkler
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Thu Feb 23 2012 - 22:54:00 EST