我正在寻找一些方法来保护我的内容不被复制,然后我得到了 epub3。
我正在使用 Html5 + js + CSS 开发移动应用程序,我可以使用 js + html 使用 epub3 zip 文件吗?如果是,我如何在其中添加 epub 阅读器。
我的问题可能是错误的 b/c 我对此了解不多。
需要专家的意见。
谢谢
我正在寻找一些方法来保护我的内容不被复制,然后我得到了 epub3。
我正在使用 Html5 + js + CSS 开发移动应用程序,我可以使用 js + html 使用 epub3 zip 文件吗?如果是,我如何在其中添加 epub 阅读器。
我的问题可能是错误的 b/c 我对此了解不多。
需要专家的意见。
谢谢
我认为这不会起作用,原因有几个:
IDPF 已经指定了一个用于 ePub3 的开源轻量级 DRM,称为 LCP,但我们仍在等待它在 Readium SDK 中的实施。完成后,您将免费获得解决方案。
If you make it readable, it cannot be also secured too from reading. Furthermore DRMs are not very effective. Streaming content is now the state of the art of content serving, and it is not immune to copying.
Is closing contents the key for your business? Maybe you can reimaginate your business process in a more profitable way.
Currently only Adobe supplies anything close to an industry-standard for encrypting epub files (see Adobe Content Server). It's very expensive, and proprietary. The epub spec does offer guidelines on how to use encryption, but it would require creating your own brand of DRM, which would then only work on your own reading system.
Epub 2 and 3 are web-friendly - they are usually HTML in a zip file. Epub 3 supports a subset of HTML 5 and some scripting capability. If you offered an online reading system, you could implement some sort of client-side decryption as the recently relaunched Mega upload service has done. It would be easily cracked, just so you know, unless you required the user to supply file-specific encryption keys that no one else knew.
Currently the best approach is to avoid DRM for epub files. Some publishers are imprinting the user's email address in the epub file as a deterrent to piracy, and others are putting files behind logins (access control). Both are better, IMHO, than paying Adobe's very high fees for the use of their proprietary content server.