Well, ODC data licenses include *both* copyrights and database rights.
So you dont give up your claims for having made a creative work...

Víctor

El 24/07/2013 10:38, Tom Heath escribió:
Just seen this thread, apols for the slow response Barry...

Of course IANAL and all that, but I disagree with Victor's conclusion.

I would argue that the individual mappings are creative works (as you
say), and therefore a CC license would apply (better still, why not
apply a public domain waiver so they're totally open?).

The collection as a whole would probably qualify as a database, at
which point Victor's points about a DB license would be relevant.

As others have mentioned, the data created by the execution of these
mappings is another issue altogether, which you seem to have covered.

My 2p worth -- hope it helps :)

Tom.


On 12 July 2013 21:38, Víctor Rodríguez Doncel <[email protected]> wrote:
Barry,

My opinion is the following:

1. Code license NO. A computer program is (WIPO): "a set of instructions,
which controls the operations of a computer in order to enable it to perform
a specific task"
2. Intellectual Property. I'd say no in this case. Some databases are
protected by IP law. They are if they can assumed to be "collections of
literary or artistic works such as encyclopaedias and anthologies which, by
reason of the selection and arrangement of their contents, constitute
intellectual creations, are to be protected as such, without prejudice to
the copyright in each of the works forming part of such collections".
So, if you have made your mapping automatically, they are NOT under the
umbrella of IP laws.
3. Database law. YES (where it applies). Relaxing the requirements, a sui
generis rights is defined in Europe to protect your database if you have
made an investment (in time or money) when making the database. Rights
(extraction and reutilization) are kept for 15 years and are not recognized
in USA and many other countries.

--> Conclusion. Instead of using CreativeCommon licenses (excepting CC0
which is ok), use Data Licenses (for example ODC), which include in their
text a reference to the European database law.

Regards,
Víctor

El 12/07/2013 21:30, Barry Norton escribió:


Incidentally, to clarify, I meant to ask a more fundamental question about
mappings: are these creative works, deserving themselves of a CC license, or
executable code, deserving of a code license?

Whichever way, I'd like to make them as encumbered as possible.

Barry


On 12/07/13 13:20, Barry Norton wrote:


I'd like to publicly release R2RML mappings for the MusicBrainz dataset.
DBpedia has shown interest in including the subset that can be used to
create a linkset.

Any idea what (kind of) licence could/should apply? (To be clear, to the
mappings, as opposed to the dataset)

I'd also like to attach, since R2RML is RDF, a licence and attribution on a
per rr:TriplesMap basis. (The mappings are hosted on github and
contributions will be accepted as I'm never going to get through all of the
MB Advanced Relationships, a moving target, myself and I'm being a
bottleneck.)

The question's also been raised on whether a given licence can in turn
impose conditions on the triples that are created using it (as derivative
works)? Does that sound feasible?

Any input appreciated.

Barry





--
Víctor Rodríguez-Doncel
D3205 - Ontology Engineering Group (OEG)
Departamento de Inteligencia Artificial
Facultad de Informática
Universidad Politécnica de Madrid

Campus de Montegancedo s/n
Boadilla del Monte-28660 Madrid, Spain
Tel. (+34) 91336 3672
Skype: vroddon3




--
Víctor Rodríguez-Doncel
D3205 - Ontology Engineering Group (OEG)
Departamento de Inteligencia Artificial
Facultad de Informática
Universidad Politécnica de Madrid

Campus de Montegancedo s/n
Boadilla del Monte-28660 Madrid, Spain
Tel. (+34) 91336 3672
Skype: vroddon3

Reply via email to