• Print

Open Publishing Distribution System — an Open-Standards Catalog Format

It’s no secret we’re big fans of the iPhone/iPod reading app Stanza. While the Kindle App has overtaken Stanza for the top-spot among free book apps in iTunes, Stanza offers a much better reading experience than the Kindle App (for example, by supporting standard formatting like tables and whitespace-preservation) (Update: You can use the latest version of mobigen.exe to get better whitespace-preservation (from <pre> and friends) on the Kindle.) And I’m not the only one who feels that way: “Stanza is hands-down the best e-book reader for the iPhone and iPod Touch, and its free. Go. Get it now.” (Wired.com).

But more than the quality of the software, the major reason I’m so bullish on Stanza is their willingness to experiment. When our own Keith Fahlgren suggested they use the standard Atom format for their catalog system, they responded:

We wound up taking your advice and implemented support for Atom for Stanza’s catalog format. Thanks for the suggestion! Using the Atom standard is much better than using our own custom format (although we may need to eventually extend the custom format with our own tags).

And when we proposed using Stanza to create a standalone book app (for iPhone: The Missing Manual), they were eager to dive in head first, and we both learned a lot in the process.

That Atom-based Online Catalog feature turned out to be an interesting prototype for a distributed digital discovery and ecommerce system, and it’s awesome to see them willing to embrace the potential for such a system well beyond the boundaries their own product, and to join with Peter Brantley and the Internet Archive in laying the groundwork for what’s being called the Open Publication Distribution System:

Users of compatible Reading Systems, in addition to being able to access content they have previously acquired or acquire via other means, are also able to access a catalog (list of online sources of content). Typically, the catalog offers a number of free titles, which may be hosted by the Reading System vendor and/or other sites, as well as the opportunity to purchase or borrow paid content from stores and libraries. Additional stores and libraries may be added by the user to their personal catalog. The mechanism through which compatible Reading Systems access the distributed catalog has three components: eBook content, XML catalog metadata, and an HTTP transport for the catalog. The remainder of this document will discuss each of those components in turn.

One of the reasons we’ve thrown our support behind the Bookworm online ebook reading system as part of O’Reilly Labs is to help support the development and testing of new standards like this one, and we’re excited to contribute to this new initiative. It’s also great to see Adobe support this as well, and is a nice follow on to our work with them on EPUB output for the open-source DocBook XSL stylesheets.  

tags: , ,

Comments: 2

  1. great, yet another “standard” that’ll be pushed down our throats,
    developed in part by adobe, with all the trendy x.m.l. claptrap…

    why didn’t y’all _start_ with a plan which included all this stuff?

    you’re coming up at one obstacle at a time, and working on it,
    without any concern for the workflow as a whole, and the result
    is a frankenstein monster. where is the insight? the overview?

    the internet archive is drowning in their high-resolution scans
    and their bloated x.m.l. output, and they can’t keep their head
    above water long enough to do even the slightest o.c.r. cleanup.

    indeed, i had to crab at them for years — literally _years!_ —
    before they stopped dropping the em-dashes from their o.c.r.

    look at some of the stuff they did — right up to mid-2008 —
    and see how readable books are when missing the em-dashes.

    and that’s _assuming_ you weren’t bothered by _thousands_
    (literally!) of o.c.r. errors in the typical book they “digitize”…

    it’s appalling. as if a person would bother reading that crap.

    and adobe? geez, they can’t even get their .epub viewer-app
    to work correctly. a rich company that must have thousands
    of programmers at its disposal, and it can’t even get it right…

    and stanza? well, not a bad little viewer-app on the iphone.
    but the desktop versions have totally stagnated — at a level
    where not even their chapter-jumps menu works correctly!

    and hey, the cats at stanza came a long way in the last year,
    but that’s how long they have been thinking about e-books…
    (and a lot of that time was spent coding rather than thinking.)
    so do we really want them to be who is making the rules now?

    i’ve been thinking about electronic-books for 30 years now
    — that’s 3 _years_ for every _month_ stanza has notched —
    and i’ve been honing my thoughts against the sharp edge
    of programming, where code doesn’t tolerate no bull-crap,
    it either runs and does exactly what it should, or it doesn’t
    do what it should, or it doesn’t even _run_ in the first place.
    the feedback is immediate, and is adamant and inexorable.

    i’ve demonstrated that simple easy-to-understand systems
    that _work_ can be assembled, and that’s the right way to go.

    so either build a simple system, or have me throw rocks at you.
    those are your choices. i sincerely hope you make the right one,
    because, as good as i am at it, i’m really tired of throwing rocks.

    but i’m also tired of you technocrats messing up what could be
    — what should be! — simple. books are supposed to be simple.
    that’s the beauty of the codex, you fools, it’s drop-dead simple.


  2. Amazon has a monopoly on ebooks. Many times, the only way to get a non-paper book is kindle format. In my apartment, I do not have room and I cannot search across books. The books I buy are for my personal use. Get non-paper books out of the grip of Amazon.