Re: [OSM-legal-talk] produced work vs. derivative db

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

Re: [OSM-legal-talk] produced work vs. derivative db

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

Re: [OSM-legal-talk] produced work vs. derivative db

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

Re: [OSM-legal-talk] produced work vs. derivative db

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

Re: [OSM-legal-talk] produced work vs. derivative db

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

[OSM-legal-talk] produced work vs. derivative db

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

Re: [OSM-legal-talk] "Produced Work" guideline working

On Fri, May 22, 2009 at 11:01 PM, Frederik Ramm wrote: > Mike Collinson wrote: >> "If it was intended for the extraction of the original data, then it >> is a database and not a Produced Work. Otherwise it is a Produced >> Work. >> >> We can clearly define things that are USUALLY Produced Works: .

Re: [OSM-legal-talk] "Produced Work" guideline working

Hi, 80n wrote: > Actually I think the duck test http://en.wikipedia.org/wiki/Duck_test is the > simplest way of approaching this problem. If someone treats something as a > database then its a database. Otherwise its a produced work. > > They can call it whatever they like when the publish it.

Re: [OSM-legal-talk] "Produced Work" guideline working

Actually I think the duck test http://en.wikipedia.org/wiki/Duck_test is the simplest way of approaching this problem. If someone treats something as a database then its a database. Otherwise its a produced work. They can call it whatever they like when the publish it. The duck test kicks in wh

Re: [OSM-legal-talk] "Produced Work" guideline working

Hi, Mike Collinson wrote: > "If it was intended for the extraction of the original data, then it > is a database and not a Produced Work. Otherwise it is a Produced > Work. > > We can clearly define things that are USUALLY Produced Works: .PNG, > JPG, .PDF, SVG images and any raster image; a map

[OSM-legal-talk] "Produced Work" guideline working

Following up from the discussion on this mailing list, the License Working Group have come up with the wording below and at http://wiki.openstreetmap.org/wiki/Open_Data_License/Produced_Work_-_Guideline This is a str

Re: [OSM-legal-talk] Produced Work

Hi, Jukka Rahkonen wrote: > Thus it would be allowed to to take > less than 100 features or area of less than 1000 inhabitants and make PD, > Share > alike or commercial derivatives from that without any restrictions. Is my > interpretation right? There's the problem of the reverse-engineering c

Re: [OSM-legal-talk] Produced Work

Frederik Ramm writes: > > Hi, > > SteveC wrote: > > And we'd like help similarly with building a practical definition of > > Produced Work. Here's how the license RC1 defines it: > > Obviously this goes hand in hand with the definition of a (derivative) > database; everything you make from

[OSM-legal-talk] Produced Work

On 7 May 2009, at 02:36, SteveC wrote: > Hi > > We've put together a practical definition for the OSMFs point of view > on what a substantial extract is, or isn't > > http://wiki.openstreetmap.org/wiki/Open_Data_License/Substantial_Defined > > And we'd like help similarly with building a pr

Re: [OSM-legal-talk] Produced Work

Hi, SteveC wrote: > And we'd like help similarly with building a practical definition of > Produced Work. Here's how the license RC1 defines it: Obviously this goes hand in hand with the definition of a (derivative) database; everything you make from our data which is not a produced work will

[OSM-legal-talk] Produced Work

Hi We've put together a practical definition for the OSMFs point of view on what a substantial extract is, or isn't http://wiki.openstreetmap.org/wiki/Open_Data_License/Substantial_Defined And we'd like help similarly with building a practical definition of Produced Work. Here's how