[OSM-legal-talk] License clarification question
Sebastian Kurfürst
sebastian at kurfuerst.eu
Sat Dec 20 09:40:36 GMT 2008
Hello,
thanks for your responses!
>> There's a license FAQ [1] which I think should answer your question.
>> whether your POI data is derived work would depend on whether you use
>> OSM data to place those POIs. I presume you have them already in some
>> database however and just wish to use OSM as a backdrop, in which
>> case
>> that would be considered a separate dataset.
Well - yes and no. On one hand, you are right, on the other hand it
should be possible for the users to place the POIs by clicking onto
the map.
:-/ I currently feel that this is quite a weird situation... In case I
have my coordinates from somewhere already, it's no derived work - but
in case people click on the map, it _is_ derived work... That feels
quite strange.
Btw - the additional data displayed at a POI (in some kind of "popup
bubble") however would definitely _not_ fall under the CC-BY-SA
license, right?
> What about if users are finding errors in the POI data that are
> shown on top of
> OSM data and they are suggesting corrections? After first
> correction somebody
> will claim that your POI data is derived from OSM. I don't know what
> would
> happen if you build another system for user feedback. Perhaps
> somebody will say
> that even your feedback system itself does not show OSM data, the
> error was
> maybe still noticed by comparing POIs with OSM data. It would be
> better to have
> some other procedure that is separated from map application for
> updating the POI
> data, even it may feel lunatic.
:-/ Do you have any ideas how this could be realized? The most natural
way is to click onto a map - and I still think it is quite strange
that such a subtile difference makes such a huge difference in terms
of licensing.
Just a general note - in case we use the new license - do the things
you wrote above still apply?
Greets,
and thanks for taking your time and answering,
Sebastian
More information about the legal-talk
mailing list