after reading all the documents/wiki/mailinglist I am still confused:
what forces producers to publish a derivative database and not just
produced work?
usecase:
a user takes a substantial part of osm db, hand modifies it (eg changes
name of a street to correct one, make a new hiking route ...) a
On 04/03/13 16:53, Michal Palenik wrote:
after reading all the documents/wiki/mailinglist I am still confused:
what forces producers to publish a derivative database and not just
produced work?
Clause 4.6 of the ODbL, which says if you publish a produced work you
must make the database it was
may i add a question into faq/use cases:
Q: I want to publish a slippy map/printed map based on OSM data.
Is it a produced work or derivated database?
A: The slippy map itself is a produced work, however the database you
used has to meet the same requirements as published derived database or a
I've tried to put extra information on several wiki pages:
http://wiki.openstreetmap.org/wiki/Open_Data_License/Produced_Work_-_Guideline
http://wiki.openstreetmap.org/wiki/Open_Data_License/Use_Cases#When_is_something_a_Derivative_Database_when_is_it_a_Produced_Work_and_can_it_be_both
(please che
On Thu, Mar 07, 2013 at 03:22:56PM +0100, Tadeusz Knapik wrote:
> Hello,
>
> > generally the answer to question "is it produced work or derivative
> > database?" is "doesn't really matter, even if it were produced work, you
> > are obliged to published the underlaying derivative database"
>
> > h
On 15/07/13 08:47, Michal Palenik wrote:
On Thu, Mar 07, 2013 at 03:22:56PM +0100, Tadeusz Knapik wrote:
Hello,
generally the answer to question "is it produced work or derivative
database?" is "doesn't really matter, even if it were produced work, you
are obliged to published the underlaying
