Creative Commons -- Now With More Science 13
The Importance of writes "Yesterday, Creative Commons announced the launch of 'the Science Commons exploratory phase.' This may eventually become a sister organization of Creative Commons that 'will delve into both legal areas (patents, data) and subject matter (biomedicine) outside the scope of [the] current organization.' In related news, the open access science publisher, BioMed Central, has adopted CC's 'attribution license' for their over 100 peer-reviewed journals."
Science doesn't need this so much (Score:5, Insightful)
Science has a rich history of "standing on the shoulders of giants". (Mathematics probably has the strongest history of that.) I don't think there's a huge need for a sea change in Science; at least it's not as severe a problem as in the software and creative industries. I suppose there's some need to stem the patent problems and such.
But I don't think it needs an organization as strong as the Creative Commons or Free Software Foundation. As a "lesser evil" I think it may be harmful taking away our attention from the more important goals we need to accomplish.
Then again, I could be (and hope I am) wrong. Perhaps the various organizations will strengthen each other by bringing the problems to the attention of a wider audience.
Re:Science doesn't need this so much (Score:5, Informative)
The issue is the outrageous cost of scientific journals, which has resulted from the increasing consolidation of the industry. Basically Elsevier (which was Galileo's publisher back when I was a young lad) has been eating up smaller presses, and jacking up their prices.
Price is a big issue. It locks poor countries out of the research world, and even in rich countries, universities are having to cut way back on their journal subscriptions.
The people who publish cookbooks and self-help manuals at least have an excuse for their prices: they have to provide extensive editorial services. Science journals, OTOH, get their editorial work done for them for free, by referees and (typically) unpaid associate editors. In my field (physics), authors normally supply their papers as LaTeX source, so the journal doesn't even have to worry about typesetting.
Re:Science doesn't need this so much (Score:3, Insightful)
The whole process of selecting and managing the reviewers, sending out the pre-prints, editing them (because there's always mistakes), and making sure the text and graphics are set well does, in fact, cost money. The publisher makes a profit, of course, but I don't think it's as much as you would expect, given their prices. They're just not very efficient (and why be efficient if you're the major publisher and have a near-monopoly)?
So E
Time to update the GPL (Score:3, Interesting)
compatible with attribution restrictions.
The old BSD license debate should be informed
by the newly available facts. A detailed
argument would be vast and misplaced, since
only RMS has actual decision influence over
the GPL, but promoting community reflection
of the inconsistencies in his principled
stance is not misplaced.
Re:Time to update the GPL (Score:3, Interesting)
The GPL needs to be updated to make it compatible with attribution restrictions.
The GPL intentionally doesn't allow this, because it became a huge problem for BSD-style licenses. The lack of attribution requirements in the GPL is a feature, not a bug.
Re:Time to update the GPL (Score:2)
One motivation for using the GPL is the identification of speech and code. (I admit
that it is not RMS' motivation, which is more subtle, obscure, and sophisticated.) Thus,
I object to your use of the word "never": Many users do in fact intend it thus.
Feature or bug depends on your worldview;)
Re:Time to update the GPL (Score:2)
The GPL needs to be updated to make it compatible with attribution restrictions.
So, write your own license. Others have. [slashdot.org]
Attribution under the GPL (Score:1)
The GPL needs to be updated to make it compatible with attribution restrictions.
The GNU General Public License is perfectly compatible with attribution requirements. Look at any GPL'd source code, and you'll see a copyright notice, which contains an attribution (for example "Copyright 2004 Damian Yerrick"). The GPL requires those who modify a GPL'd work to preserve existing copyright notices.