Slashdot Mirror
Plagiarizing Wikipedia For Profit
An anonymous reader sends word of a dustup involving the publisher John Wiley and Sons and Wikipedia. Two pages from a Wiley book, Black Gold: The New Frontier in Oil for Investors, consist of a verbatim copy from the English Wikipedia article on the Khobar Towers bombing. This is the publisher that touched off a fair use brouhaha earlier this year when they threatened to sue a blogger who had reproduced a chart and a table (fully attributed) from one of their journals.
Although the author of the linked page says he wrote much of the disputed text and released it into public domain, the license governing Wikipedia is GNU FDL, as can be seen by a link at the bottom of every page. The combined work, because it includes work by others, is covered by that license.
:)
If Wiley published this text without citing the FDL, they're in violation of it. Seems pretty clear. Further, the license says that if the work is modified, the resulting document must also be released in FDL, according to section 4. This is where it gets interesting.
Because GDFL allows copying only if you allow the work to be freely copyable, and release the work it is included in under the GDFL.
If this is the case, then the whole book that this text is in becomes freely copyable, as long as it's source is attributed. If the publisher chooses not to conform to this license, then it becomes in breach of copyright (as the works on Wikipedia are covered by copyright law, they're simply globally available on a license backed up by copyright law).
Copyright doesn't require proof of damages, but damages could be calculated from the sold copies of the book.
Patents Drive Free Software as Hurricanes Drive Construction Industry
No, that's just silly.
Bingo, got it in one.
However, the prize for most shameless copyright infringement goes to The Times Of India.
XML is like violence. If it doesn't solve the problem, use more.
There are (or were) at least two articles in Wikipedia that are my texts (from my site) with slight variations on sentences. So whoever visits those Wikipedia articles (or did so in the past) and then my pages must come to the conclusion that I stole the stuff from Wikipedia without giving credit. I can't even prove that because I don't have a public version history, and archive.org is spotty when it comes to my site.
In this case (Wiley book) the articles were there way before the book, so the case seems to be clear, but in general, I recommend to keep an open mind about who copied where.
They're not giving ANYTHING away. They're licensing a copy of their product to you, under certain conditions.
They neither wanted nor did that, the Wikipedia text is under the GFDL which requires attribution of source. The WP author mentioned released his contribution to the public domain, but the wider Wikipedia community has the right to be outraged that this writer a) plagiarised Wikipedia and b) didn't credit the authors of the text that he plagiarised. He claimed the words as his own, which is unlawful in many copyright jurisdictions regardless of any licence that the original author may have used. If the publisher sells that book in Finland, then they could find themselves in hot water. And I don't mean a nice invigorating sauna.
In addition to what Phil has pointed out in another reply, it's worth pointing out that there are many different Creative Commons licenses, and they vary in what they permit. Some of them do not permit commercial use, some of them require attribution, some of them are more permissive.
Please, if you are going to make claims about what something does and doesn't permit, at the very least you should be vaguely familiar with it yourself. Creative Commons is a brand name for a bunch of different licenses, not a license itself.
Bogtha Bogtha Bogtha
*even if they remove the offending pages from future copies*, since the entire book is now contaminated.
This is untrue. First, because the license doesn't automatically become FDL, it becomes a license violation which should be dealt with through law. Second, because there is nothing that states that once something is released using FDL it always has to be released in that license. The author is free to release his portion of the work using any license he/she chooses, in the same way that software publishers can dual license their software.
If the license did automatically become FDL, then the author would still be able to publish the book under a different license without those portions. Those who received the original release that was forced FDL (if this hypothetically did happen), could redistribute the work under the FDL, but those who purchased the other version would not have received it under the FDL and thus could not redistribute it.
- except it was an application included on a CD in David Pogue's Palm PDA book:
http://www.oreilly.com/catalog/palmpilot/
- my client's simple license clearly stated 'no distribution on media without permission,' but it was included...
- i never busted o'reilly's chops about it, 'cause i met him one time at a Perl conference in Monterey and he was very nice to me...