open-discussion
open-discussion > RE: AAAS: Your Paper MUST include Data and Code
Mar 11, 2011 07:03 PM | Luis Ibanez
RE: AAAS: Your Paper MUST include Data and Code
Originally posted by Torsten Rohlfing:
This is a very good point,
and the answer is that we MUST demand data to be made available
under the licenses created by the Science Commons:
http://www.kitware.com/blog/home/post/72
and the code to be available under Open Source licenses:
http://www.opensource.org/licenses/index...
--
That said, the dirty secret of data is that there is no legal ownership of data,
other that the emotional attachement that researchers feel towards the fruit
of their labor.
Data is not copyrightable: because it is not the outcome of a "creative" act.
A scientist who claims that his data is copyrightable, is telling us that he
manufactured the data, or made it up, and therefore you proably should
stay away from such person and his data.
Data is not patentable: because it is not an invention
Scientific data is factual and therefore is pre-existing in nature.
The only legal restriction to distribution of data is set by the contractual terms
of confidentiality that typically exist between employers and employees.
(These confidentiality laws date back to the Roman Empire and are related
the rules forbiding to use a slave to extract information about his master).
--
Once data is distributed, the originator of the data has no right to futher
restrict the use of that data.
Despite that fact, the litigious nature of today's technical environment is
such that the only way to make possible to consume data with peace of
mind is to require data producers to make the data available under the
Open Data Licenses:
http://www.opendatacommons.org/licenses/
---
The editorial of Science also made the point that to address the case
of data hosting that you mention, the Journal makes arrangements
with the authors to host the data in third party data repositories.
Originally posted by Luis Ibanez:
Another question I think is not getting enough attention here is, under what terms such data (and code) are available. In particular, what happens if the rights to the data are not held by the paper authors? Say, I write a paper using slightly modified brain images from the IBSR repository (just as a random example of a shared data resource). I cannot distribute those images to anyone because the IBSR use conditions prevent me from doing it. I can give the modified images back to IBSR and ask them to make them available on my behalf, but they are not obligated to. If they do choose to distribute the modified data, they could impose conditions on them that some may consider unreasonable. Are these data then still formally available? The same goes for any other data repository that imposes non-proliferation conditions upon data users (which is pretty much every such resource that I am aware of).
“Science policy for some time has been that ALL
DATA NECESSARY to
understand, assess, and extend the conclusions of the manuscript must
be available to ANY reader of Science (see
www.sciencemag.org/site/feature/contribinfo ) “
understand, assess, and extend the conclusions of the manuscript must
be available to ANY reader of Science (see
www.sciencemag.org/site/feature/contribinfo ) “
Another question I think is not getting enough attention here is, under what terms such data (and code) are available. In particular, what happens if the rights to the data are not held by the paper authors? Say, I write a paper using slightly modified brain images from the IBSR repository (just as a random example of a shared data resource). I cannot distribute those images to anyone because the IBSR use conditions prevent me from doing it. I can give the modified images back to IBSR and ask them to make them available on my behalf, but they are not obligated to. If they do choose to distribute the modified data, they could impose conditions on them that some may consider unreasonable. Are these data then still formally available? The same goes for any other data repository that imposes non-proliferation conditions upon data users (which is pretty much every such resource that I am aware of).
This is a very good point,
and the answer is that we MUST demand data to be made available
under the licenses created by the Science Commons:
http://www.kitware.com/blog/home/post/72
- Public Domain Dedication and License (PDDL) — “Public Domain for data/databases”
- Attribution License (ODC-By) — “Attribution for data/databases”
- Open Database License (ODC-ODbL) — “Attribution Share-Alike for data/databases”
and the code to be available under Open Source licenses:
http://www.opensource.org/licenses/index...
--
That said, the dirty secret of data is that there is no legal ownership of data,
other that the emotional attachement that researchers feel towards the fruit
of their labor.
Data is not copyrightable: because it is not the outcome of a "creative" act.
A scientist who claims that his data is copyrightable, is telling us that he
manufactured the data, or made it up, and therefore you proably should
stay away from such person and his data.
Data is not patentable: because it is not an invention
Scientific data is factual and therefore is pre-existing in nature.
The only legal restriction to distribution of data is set by the contractual terms
of confidentiality that typically exist between employers and employees.
(These confidentiality laws date back to the Roman Empire and are related
the rules forbiding to use a slave to extract information about his master).
--
Once data is distributed, the originator of the data has no right to futher
restrict the use of that data.
Despite that fact, the litigious nature of today's technical environment is
such that the only way to make possible to consume data with peace of
mind is to require data producers to make the data available under the
Open Data Licenses:
http://www.opendatacommons.org/licenses/
---
The editorial of Science also made the point that to address the case
of data hosting that you mention, the Journal makes arrangements
with the authors to host the data in third party data repositories.
Threaded View
Title | Author | Date |
---|---|---|
Luis Ibanez | Mar 10, 2011 | |
hongtu zhu | Mar 13, 2011 | |
Luis Ibanez | Mar 13, 2011 | |
Matthew Brett | Mar 13, 2011 | |
Isaiah Norton | Mar 13, 2011 | |
Torsten Rohlfing | Mar 10, 2011 | |
Luis Ibanez | Mar 11, 2011 | |
Daniel Kimberg | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |
Torsten Rohlfing | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |
Torsten Rohlfing | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |
Torsten Rohlfing | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |
Matthew Brett | Mar 10, 2011 | |
Pierre Bellec | Mar 10, 2011 | |
Luis Ibanez | Mar 11, 2011 | |
Matthew Brett | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |
Torsten Rohlfing | Mar 10, 2011 | |
Daniel Kimberg | Mar 10, 2011 | |
Cinly Ooi | Mar 10, 2011 | |