Quote:
Originally Posted by Anak
Correct, but Adobe is de facto the standard on e-readers. That won't change when 3pub replaces epub2.
A renderer should simply follow the epub3 specification.
Which renderer is used is not that important as it is basically a page rendering engine plus a DRM solution. Kobo could also use the Adobe renderer and use there own kDRM solution or the Access renderer and Adobe DRM schemes.
A reader should use one page renderer that recognizes the format (epub or kepub) and apply the appropriate DRM scheme.
Access should license the Adobe DRM scheme and offer it to their customers. Best of both worlds? Easier to maintain by Kobo? Other?
|
At this time, Datalogics who are the current maintainers of the Adobe RMSDK are member of the Readium Foundation and have stated they will be basing their epub3 software on the final Readium code with the latest Adobe DRM grafted on -- you can download DL Reader to get an idea of the direction that are going into given that the big item with their latest release is the hardened DRM though they have implemented some of the text direction from epub3. As for following the epub3 specification? I suggest checking out how different web pages can look in various browsers which implement the same standards. The renderer does matter since no minimally complex standard has ever been implemented that does not have some spots where the implementor can make choices especially in the area of "optional" items.
ACCESS does not supply the DRM scheme used by Kobo. That is a Kobo addition which does avoid the licensing fees. There is also a DRM scheme which Kobo has had some input into which has been proposed for use by Readium which would give us yet another DRM scheme.
Regards,
David