The ability to inspect, comment, and modify a scientific publication doesn't mean much if the underlying work is unavailable.
The ability to inspect, comment, and modify a scientific publication doesn't mean much if the underlying work is unavailable.
And that, in itself, is a problem. How can others identify flaws in the paper if they can't see the data you used?
Open Source software includes all the code you need, not just the final binary executable. Any proposed "Github for Science" needs to do the same.
And any arguments that "the data is expensive to collect and proprietary" can be countered with "code is expensive to write and proprietary, yet open source still works".
In fact, almost all medical trials or epidemiological studies use data that can't be shared outside the study.
e.g. We don't know who this guy is, but we do know that every measurement of him was linked to this same enormous random string.
When doing data linking I can usually identify one person in a dataset of almost 1 million from three innocent seeming pieces of data. Pseudonimisation doesn't really work.
These two are absolutely not equivalent. I'm all for open science, but the comparison with open source code is absurd. With the former you have to invest actual money: infraestructure, materials, suppliers, etc. and of course you have to deal/coordinate those elements. OS is... just time. There is a cost, but it is just an opportunity cost.
There are famous examples of widely-used open-source software having bad bugs (for example, OpenSSL) which no-one found, because although it was so widely used, no-one was performing careful enough analysis of the codebase. And programmers are actually paid to look at code all day. No-one working in a research institution is paid or recognised for trying to verify someone else's data or check that their research makes sense - this was the job of peer review. (Even peer review is unpaid and unrecognised at many institutions.)
The solution to this problem is not iteration and revision.