Juliet wrote:
David H. Rothman wrote:
It's the best of all worlds: open source for programmers and a powerful free reader for users--and e-book standards similar to existing ones for publishers. Plus, dotReader can handle other XML/CSS-related formats as well.
If dotReader can handle XML/CSS-related formats, then many of the more recent PG books are already available for it, since they have been produced in xhtml. Most of the output from DP these days comes with an xhtml version.
The first vocabulary supported by OpenReader, called the "Basic Content Document 1.0" (BCD) is a structurally-oriented subset of XHTML 1.0, and compatible, as best as possible, with XHTML 2.0 currently being developed by W3C. It is also quite compatible with OEBPS 1.2. The draft BCD spec is located at: http://openreader.org/spec/bcd10.html We plan to create an "Extended Content Document" vocabulary by simply adding XLink support plus some OpenReader namespace tags to markup important things that XHTML does not natively support, such as page breaks and boundaries and numbering (e.g., for preserving where page breaks occurred in the original paper book), line breaks as occurred in the original (<br/> is not sufficient for this as I could talk about another time), other noteworthy "mile markers", inline indexing information (so OpenReader "readers" can assemble a people- authored index on the fly), etc., etc. Anyway. Feedback on BDD from those in DP who produce XHTML versions of books is more than welcome! Of course, looking for those willing to do a careful vetting of the BCD spec (and anyone who does becomes a contributor to be added to the list of contributors in the spec.) Thanks. Jon Noring OpenReader Consortium