Re: MEDILIG project with OdBL + GPL License - Discussion

Hi there,
I read both your FAQ and the full text of ODbL. I would like to highlight a
few points based on the application of ODbL to the MEDILIG project.
http://medilig.org
So the easiest way to do this is with Q&A. You will read my personal
opinion. I am not an expert on licensing. My answer might be far from right
or perfect and therefore please do comment.

1) Why do you apply two licenses ODbL and GPL for the MEDILIG project ?
MEDILIG project is a software product/service and it also includes a
database. The use of the database cannot be covered with a GPL license.

2) Software is normally covered by software licenses. Why did not you apply
only GPL license ?
Because as far as I know GPL does not tell you anything about who controls
the database and what are the rights of the user on the database.
For example consider the deployment scenario where the software is open but
the database is locked!
Does the user have the right to unlock the database, does he have the right
to export or import his data from/to the database and in what extent? Can he
create a derivative database or use the existing one collectively as part of
other system developed?
This is where OdBL comes to grant rights to the user!!! It is section 3.0
and 4.0 of the full license that brings revolution to the open software
community and that has NOT been stressed emphatically on your site I believe
 Yes, perhaps you can find a lot of open and free software out there but
not open and free databases. In fact your license protects user's data as
the user has the right to ask full permission and access by any means on the
database resources. There are too many implications on that issue and I will
not go deeper. HEALIS supports open standards and open access to the data.