Hi,
> I don't think this distinction of >whether you can keep your database
>updated or not is anywhere in the >ODbL. If it was the way you explain
>it, it would be really easy to make a >dataset containing all the
>useful data and not bound by the >limitations a Derived Work bears.
>You could eve
Richard Weait writes:
>>Surely this is two separate steps:
>>
>>- begin offering a licence to the whole database under ODbL,
>>- stop offering a licence under CC-BY-SA.
>>
>>They might happen at the same time but they don't have to.
>I suspect that proceeding with two active databases would be
>
On 21 May 2010 14:47, Oliver (skobbler) wrote:
>>"Share-Alike: If you publicly use any adapted version of this database,
>>or works produced from an adapted database, you must also offer that
>>adapted database under the ODbL."
>>
>>(I am trusting/hoping the human readable terms match the legalese
On Fri, May 21, 2010 at 1:03 PM, Ed Avis wrote:
> Mike Collinson writes:
>
>>- When enough contributors have agreed, we cut over to licensing the current
>>database under ODbL, (And a static snapshot of the database is also made
>>forever
>>under CC-BY-SA). If for some reason this event never h
Mike Collinson writes:
>- When enough contributors have agreed, we cut over to licensing the current
>database under ODbL, (And a static snapshot of the database is also made
>forever
>under CC-BY-SA). If for some reason this event never happens, the fail safe is
>that licensing of all contribu
Oliver,
Oliver (skobbler) wrote:
> I think the "updatability" is key when distinguishing between Derived and
> Produced Work.
That concept is completely new and has never been brought up in the
discussions around ODbL. It might work and it might not. It would be
good if it worked because that
>What you're saying, basically, is that making a cake loses the (or some)
>properties of the ingredients, thus a produced work; making a car
>doesn't, thus not produced. (Of course making a car also entails
>irreversible actions but let's ignore that for the moment.)
>
>Transferred back to the map
Hi,
Oliver (skobbler) wrote:
> Consider a "produced work" of something that cannot be reproduced because
> disassembling is not possible. Take a "cake" for example (kitchen wise, just
> for understanding the concept). You cannot produce a another cake from the
> first cake or alter it because you
>"Share-Alike: If you publicly use any adapted version of this database,
>or works produced from an adapted database, you must also offer that
>adapted database under the ODbL."
>
>(I am trusting/hoping the human readable terms match the legalese.)
>
>So...my question is: how _useful_ does the der
>1. Is it clear that a "map tile" is an "image" within the definition of a
"Produced Work"--a work (such as an >image...) resulting from using the
whole or a Substantial part of the Contents?If not, what is the most
>typical example of a Produced Work in the map context?
Consider a "produced
10 matches
Mail list logo
