2 weeks ago, amidst all the hype surrounding the iBookstore and the business model chosen by Apple to allow people to sell iBooks on the iBookstore, I asked the following question:
When I publish something through the iBookstore, am I the copyright holder of the book’s content?
Why was this question so important? Because, If the creator of the iBook is in fact the copyright holder of the book’s content, he/she can then publish the same book in other formats to reach out to other “readers”. If not, that’s a more serious issue because then authors are “stuck” with Apple’s format and cannot publish their books in more “widely-accepted formats”.
At the time, this was not clear in the iBook Author’s EULA. Rather, the wording in the EULA suggested that Apple was not only the owner of the format of book (.iBook) but also of the book’s content.
This raised several concerns to authors (as pointed out above), which is only natural, but now Apple has decided to make the EULA quite clear and stated the following:
If the work is provided for a fee (including as part of any subscription-based product or service) and includes files in the .ibooks format generated using iBooks Author, the work may only be distributed through Apple, and such distribution will be subject to a separate written agreement with Apple (or an Apple affiliate or subsidiary); provided, however, that this restriction will not apply to the content of the work when distributed in a form that does not include files in the .ibooks format generated using iBooks Author. You retain all your rights in the content of your works, and you may distribute such content by any means when it does not include files in the .ibooks format generated by iBooks Author.
I think authors can relax now. Basically, Apple is saying: if you want to sell iBooks, you can only do it through the iBookstore. If you want to sell your own e-book (with the same content as the iBook as long as you don’t use any of the same files in the iBook) somewhere else, you’re free to do so.
Comments
There are no comments for this post yet.