Re: CC-ND waver/license and data 'reuse'

No Derivative Works — You may not alter, transform, or build upon this work.

Doesn't sound like building on the shoulders of giants, doesn't it?

But the question is: does it refer to an information artifact (e.g. an image) or its content?

Best,
Andrea

Apologies for typos, Sent from an iPhone

On 30/gen/2013, at 15:58, Jerven Bolleman <me@jerven.eu> wrote:

> Hi All,
> 
> We (uniprot) are working on changing this to be more permissive. But
> are waiting on the CC4 process.
> If you want to know more please write to help@uniprot.org as I do not
> know specifics.
> 
> Regards,
> Jerven
> 
> On Wed, Jan 30, 2013 at 4:44 PM, Michel Dumontier
> <michel.dumontier@gmail.com> wrote:
>> 
>> UniProt uses this restrictive non-open license
>> 
>> ftp://ftp.uniprot.org/pub/databases/uniprot/current_release/rdf/README
>> 
>> m.
>> 
>> On Wed, Jan 30, 2013 at 5:52 AM, Susanna Sansone <sa.sansone@gmail.com>
>> wrote:
>>> 
>>> Hi all,
>>> calling on your expertise, please.
>>> I am looking for real experiences and examples showing if and how a CC-ND
>>> waver/license for data files and related experimental descriptors limits its
>>> reuse (as derivative works won't be allowed, e.g. data mush-ups, linked
>>> data).
>>> Beside the official CC pages on CC-ND and several sites echoing the same
>>> text and theory, does any of you/working groups have direct experience on
>>> this matter? Also pointers to articles and white papers is very much
>>> appreciated.
>>> Many thanks in advance,
>>> Susanna
>>> 
>>> --
>>> Susanna-Assunta Sansone, PhD
>>> uk.linkedin.com/in/sasansone
>>> 
>>> University of Oxford e-Research Centre
>>> Principal Investigator, Team Leader
>>> isacommons.org | biosharing.org
>>> 
>>> Nature Publishing Group
>>> Consultant
>>> Data Products
>>> --
>> 
>> 
>> 
>> 
>> --
>> Michel Dumontier
>> Associate Professor of Bioinformatics, Carleton University
>> Chair, W3C Semantic Web for Health Care and the Life Sciences Interest Group
>> http://dumontierlab.com
> 
> 
> 
> -- 
> Jerven Bolleman
> me@jerven.eu
>