… and radio! Mary Laplante and I will be on the MyTechnologyLawyer.com radio show this Thursday, discussing the upcoming Gilbane San Francisco conference. We’ll be on the air live for an hour starting at 4:00 Eastern, and will be discussing a wide range of topics about the conference, with some focus on the sessions I am coordinating. The host, Scott Draughon, is a great guy and really does an excellent job interviewing his guests on a wide variety of topics. Mary and I have done the show before (this time last year as well) and it was a pleasure. Be sure to tune in!
Author: Bill Trippe (Page 8 of 23)
Amazon’s front page today is announcing that the Kindle is back in stock. They also provide a link to Jeff Bezos’ annual letter to Amazon shareholders, which is dedicated to his thoughts about the Kindle. Nothing earth shattering, though I do think he tries to get to the heart of the question about why someone would buy a Kindle when they already own both a Blackberry and a desktop or notebook computer. After the obligatory reference to Gutenberg, Bezos writes:
Lately, networked tools such as desktop computers, laptops, cell phones and PDAs have changed us too. They’ve shifted us more toward information snacking, and I would argue toward shorter attention spans. I value my BlackBerry–I’m convinced it makes me more productive–but I don’t want to read a three-hundred-page document on it. Nor do I want to read something hundreds of pages long on my desktop computer or my laptop. As I’ve already mentioned in this letter, people do more of what’s convenient and friction-free. If our tools make information snacking easier, we’ll shift more toward information snacking and away from long-form reading. Kindle is purpose-built for long-form reading. We hope Kindle and its successors may gradually and incrementally move us over years into a world with longer spans of attention, providing a counterbalance to the recent proliferation of info-snacking tools.
This is an interesting way to position Kindle or any eBook reader–the competition isn’t the other devices per se but the habits these other devices have accommodated. This is true, I suppose, but I still think that devices will emerge that support both kinds of information consumption–the short form and the long form. What’s missing in Kindle, interestingly, are some features that would make “information snacking” also possible–and useful. As David Guenette pointed out, the Kindle could have readily added MP3 support (“It has the ICs and jacks for playing MP3 files, but no playlist management, nor–absurdly enough, considering that Amazon is set up to sell things like music–any iTunes-like music downloading.”) Plus the idea of paying to read a blog that is otherwise free on the Web is just silly.
So we are still left with, as David calls it, the “additional device conundrum.” I have been using an eBook reader lately, and enjoying it, but there are limitations with that one and what I can read on it. I want to be able to read, at minimum, books, magazines, newspapers, blogs, general web sites, and a wide range of personal content including but not limited to Word, HTML, PDF, and XML formats. I want it to be brain-dead easy to download and access new content. As David points out, I also want multimedia. And I want a level of interactivity to include links, forms, and feedback. I want it to be cheap, powerful, and sturdy, and I want the reading experience to be superior to my notebook computer in terms of size, weight, portability, and readability. In other words, I want something like the Kindle in form factor that behaves much like a really good notebook computer.
Is that too much to ask?
I’ve been intrigued by MadCap Software and their aggressive push into the documentation tools space. We just got an in-depth series of presentations on their products, and I certainly came away impressed. Mary Laplante is quoted in a related article over at EContent Magazine.
Click here to find out.
The ever-helpful Jon Noring has formed a new discussion group on Yahoo, EPub Community, with a goal of furthering discussion and collaboration around the IDPF specifications which underlie EPub (OPS/OPF/OCF).
As part of the review I was doing of the eBookWise-1150, I played some with their publishing tools. The device maker, eBook Technologies, Inc. (ETI), has some tools for publishers, and I tried both a batch processing tool and an interactive one. I say “played” with them because I only tried a few things, and there were many features, especially to the interactive tool. The tools looked very solid. I have also played around some with the Kindle Digital Text Platform. I do this to learn the tools, but also to keep myself honest. We advise clients on these devices and also the workflow surrounding eBook creation. Our clients don’t expect us to know every bell and whistle, but they do expect us to understand what is possible and not possible.
The more eBooks become attractive options for publishers, the more issues of publishing to multiple formats and platforms become important for publishers. Our experience so far has been that the most typical requirement for publishers is the need to produce eBooks in many different formats and not just one (this despite sensible solutions like IDPF’s EPUB format). And they need to do this efficiently. This is a practical reality of the marketplace today as no one eBook format has won the format war, no one channel is dominating sales, and indeed no one channel is typically worth doing on its own. The revenues simply are not there yet. (Indeed, even if you decide that you will only do, say, PDF-based eBooks, the similarities from one channel to the next end with the PDF extension, necessitating technologies like codeMantra’s Universal PDF).
Adobe is one of the vendors supporting EPUB, and their Digital Editions developer site has some good resources. They just added an EPUB Best Practices Guide (in, not surprisingly, EPUB format, so you can download Digital Editions if you want to get right to reading it).
Andy Updegrove is keeping a running tally over at Standards Blog.
UPDATE: Updegrove is now reporting OOXML will pass the vote, and Slashdot has a roundup that includes reports of irregularities in the voting.
Some news from the W3C:
The XSL Working Group has published the First Public Working Draft of Extensible Stylesheet Language (XSL) Requirements Version 2.0. This document enumerates the collected requirements for a 2.0 version of XSL Formatting Objects (XSL-FO), not for XSLT. XSL-FO is widely deployed in industry and academia where multiple output forms (typically print and online) are needed from single source XML. It is used in many diverse applications and countries on a large number of implementations to create technical documentation, reports and contracts, terms and conditions, invoices and other forms processing, such as driver’s licenses and postal forms. The XSL Working Group invites people to help prioritize the feature set of XSL 2.0 by completing a survey until the end of September 2008.
I talk to developers who have ideas about improving XLST. Now is your chance.