View Single Post
Old 02-07-2005, 04:55 AM   #1
Colin Dunstan
Is papyrophobic!
Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.Colin Dunstan ought to be getting tired of karma fortunes by now.
 
Colin Dunstan's Avatar
 
Posts: 1,926
Karma: 1009999
Join Date: Aug 2003
Location: USA
Device: Dell Axim
OpenBerg e-book reader supports OEBPS 1.2

The OpenBerg e-book reader, part of the OpenBerg project, can now open and display books in uncompressed OEBPS (OpenReader) 1.2 format, as well as follow hyperlinks. Note that this is a great forward leap in an open source implementation of OpenReader. Who will be the first to release an e-book reader for PDAs supporting OEBPS 1.2? My bet would be: Plucker.

Jon Noring, member of the OpenReader Consortium, explains:

Quote:
OEBPS 1.2 (and most other publication frameworks built upon XML) represent digital publications using multiple resources (files). Obviously, for distributing ebooks and similar types of digital publications (newspapers, periodicals, documents, etc.), we want to distribute a publication as a *single* file. Thus, we have to somehow encapsulate an OEBPS 1.2 Publication into some sort of "wrapper" file for distribution/sale purposes.

This is what the OpenReader format is intended to address. Currently, the OpenReader format has not yet been finalized -- at this stage it is still conceptual with a preliminary list of requirements. A technical working group needs to be assembled to finalize 1) the "requirements" list (e.g., "the OpenReader format must do this, that, and the other thing") and then 2) come up with the format spec details that sufficiently meets the list of requirements.

OpenBerg addresses the issue of *how to render* (display) an OEBPS 1.2 Publication, while the OpenReader format addresses *how to move* an OEBPS 1.2 Publication from the publisher to OpenBerg and other OEBPS rendering engines. OpenBerg and OpenReader are not in competition, but rather complement each other.
Colin Dunstan is offline   Reply With Quote