Is this Textbook Really Smarter than Your Prof?

I read this morning Lawrence Summer’s editorial in the New York Times with a mixture of fascination and horror.  Entitled “What You (Really) Need to Know,” the piece contains some motherhood-and-apple-pie truisms — the world is changing rapidly, students need to be “engaged” through “dynamic” educational practices, collaboration is a Good Thing, etc., etc., etc.  But I was stopped short by these two paragraphs:

New technologies will profoundly alter the way knowledge is conveyed. Electronic readers allow textbooks to be constantly revised, and to incorporate audio and visual effects. Think of a music text in which you can hear pieces of music as you read, or a history text in which you can see film clips about what you are reading. But there are more profound changes set in train. There was a time when professors had to prepare materials for their students. Then it became clear that it would be a better system if textbooks were written by just a few of the most able: faculty members would be freed up and materials would be improved, as competition drove up textbook quality.

Similarly, it makes sense for students to watch video of the clearest calculus teacher or the most lucid analyst of the Revolutionary War rather than having thousands of separate efforts. Professors will have more time for direct discussion with students — not to mention the cost savings — and material will be better presented. In a 2008 survey of first- and second-year medical students at Harvard, those who used accelerated video lectures reported being more focused and learning more material faster than when they attended lectures in person.

To begin first with Summer’s last point here:  do we really believe that “accelerated video lectures” are superior to attending lectures in person?  Or could it be, just maybe, that the other activities in which students engaged alongside the video lecture (small group discussions, for instance) were what actually made this a better learning experience, and that these were sufficiently effective to make up for the stultifyingly dull experience of watching a video lecture?

The irony of advocating passive video lecturing (and thank goodness he doesn’t “mention the cost savings,” because that of course has no bearing on his argument, right?) in the same editorial in which “Active learning classrooms” are lauded seems lost on Summers.  I can well imagine how a digital lecture, fully integrated with interactive and dynamic elements and features, might produce an excellent learning experience, but that’s not quite the same thing as plunking students down in front of a video of a talking head (however brilliant a head it may be) discussing the causes of the American Revolution.

However, I primarily want to address Summers’ first point about textbooks, which he suggests have been “written by just a few of the most able” pedagogues and scholars.  To begin with, I’m far from sure that this is really an accurate characterization of the way in which textbooks have been produced, but for the moment I’ll accept the premise that current practice is to rely upon the “excellence” of our textbook authors and editors so as to free ourselves up for other “more important” things.

Summers is clearly thinking about, even if he doesn’t directly mention, the new iBooks Author application from Apple;  a link within the paragraph refers readers to an index of NYT stories on that tool.  As is suggested by his segue to video lectures, Summers believes that the “old model” of textbook production is a good thing:  let’s have the “most able” in our disciplines produce the texts, just as we should leave our lecturing to the best lecturers.  Now, however, the “most able” can create these textbooks in iBooks Author, and thereby produce more engaging and interactive texts for our students.

This approach, this acquiescence to the notion that we should let the “most able” build our textbooks for us, seems to me to miss out on an important element of the potential power of iBooks Author, or at least of what that tool represents.

How many of us are truly happy with our textbooks?  I take some care to choose anthologies for my course that are the best available (bearing in mind, however, cost to the student as well), but I still find myself in the not-infrequent position of apologizing to the class for the text.  An error here, an omission there, and on occasion a glaringly awful misprint — I’ve had to direct students’ attention to all of these.  On one memorable occasion, my students were thrown into confusion because a very popular textbook we were using had managed to run parts of two Seamus Heaney poems together, producing a sort of inadvertent monstrous poetic pastiche.

And of course there is the question of availability: I often have to drop from a syllabus a literary text that I’d love to teach simply because it is not available in a cheap modern edition.

Surely part of the appeal of easy-to-use tools like iBooks Author is that they can, in theory, allow us to create our own customized teaching texts?

By this, I don’t mean to suggest that we need to reinvent the wheel every time we teach a course:  I am, by and large, still pretty happy with the Broadview Anthology of Restoration and 18th-Century Literature as the core text for my survey course covering that period, despite some serious cavils here and there.  But what would be really great is an easy way to build on such core textbooks with custom-built texts that allow me to teach literary works or contextual materials not otherwise easily available.  It would be wonderful to enable a more engaging, complete, and dynamic contextualization of the ones that are already in the prefabricated textbook.  So, if I want to teach Daniel Defoe’s The Shortest Way with Dissenters (and I do), or John Dryden’s “Preface” to Fables, Ancient and Modern, neither of which are in the Broadview Anthology, I can do so by creating my own eText versions of these, complete with any media or contextual materials that I think might be worthwhile. Increasingly, textbooks are being offered to us in “modular” form by publishers; what I am suggesting is that we can build some of these modules ourselves.

Such an approach to course texts would, of course, demand a fair amount of work from instructors, and would, as things currently stand, disadvantage those who lack the technical skills to produce their own digital texts. But what I think that iBooks Author potentially represents is a significant move towards a day when there are cheap and easy-to-use tools available to build just such custom modules.  Imagine, for instance, a web site into which someone with the most basic technological knowledge could simply input text and multimedia content, click “Submit,” and receive an ePub-compliant HTML5-encoded text (and maybe XML too) as output?

We’re not there yet, but surely iBooks Author gives us glimpses of a future in which we can all become as smart as our textbooks, because our textbooks are built by us.


Apple iBooks Author vs. ePub3: What If We Let the Tail Wag the Dog Just This Once?

John Gruber has an interesting new post on Daring Fireball in which responds to criticism of Apple’s new iBooks Author file format by Daniel Glazman, Co-chairman of the W3C CSS Working Group.  Glazman dislikes the fact that Apple has extended the CSS for that format beyond the standards set by ePub3:  “All in all, Apple has worked entirely behind the curtains here. If someone tells you that iBooks format is EPUB3, don’t believe it. It’s not EPUB3, it’s only based on EPUB3.”

The result — and I’ll take his word for this, as I don’t myself have access to the iBooks Author tool — is that “[b]ecause of these extensions, editing or browsing the html documents with a regular wysiwyg editor (BlueGriffon or DreamWeaver for instance) or a browser (Firefox, Chrome or even Safari) shows a total mess on screen. It’s not readable, it’s not usable, it’s not editable. Just forget it, Apple (re-)invented the Web totally incompatible with the Web.”

Glazman enumerates the nature of the particular extensions to CSS (and hence to ePub3):

  1. Template-based layout including special areas (gutter)
  2. Extended underlining
  3. Ability to control the size of each column and column gap in a multi-column layout
  4. something equivalent to Adobe’s Regions and Exclusions.

Now, again, I don’t have iBook Author, so I can’t speak with much assurance about what these extensions “mean,” except to say that they sound like rather good things.

Gruber’s response to Glazman is pretty unsympathetic, but both logical and reasonable.  Glazman feels that Apple should have proposed these extensions to the W3C CSS Working Group before implementing them — an unsurprising opinion coming from Co-chairman of that committee.  Gruber responds that

. . . if Apple had taken this route, the books generated by iBooks Authortoday wouldn’t have any of the layout features Glazman cited above. The iBooks format isn’t different just for the sake of being different, it’s different for the sake of being better — not better in the future, after a W3C review period and approval, but better today, in the textbooks you can download and read in iBooks right now.

Now, I’m a strong believer in open standards, and in standards compliance.  And I don’t particularly like, even if I understand, the thinking behind changes to standards that make a particular format proprietary rather than open.

That said . . . Apple has apparently produced a beautiful product here that employs format features that are better than could be produced through rigid compliance with ePub standards.

So what would happen if, instead of merely complaining about Apple getting the jump on standards-compliant eBook publishers or undercutting the attempt to produce such standards, the co-chair of the W3C CSS Working Group had additionally said something like:  “But wow.  They shouldn’t have done it this way, but we’re glad they did, because now we can see that these are extensions that should be added to the ePub specifications!  We can all benefit from Apple’s decision to innovate and push the envelope here!”

Even better — what if those creating the open standards for things like ePub3 were to take the same kind of imaginative approach, and had the same kind of concern for the overall excellence of interface design, that Apple’s designers and engineers apparently have?  What if the w3C CSS Working Group were itself producing these kinds of forward-looking innovations, and in so doing making it more attractive to be standards-compliant?

Wouldn’t that be cool?

The 10 Reasons Why I Will Not Be Creating Textbooks with Apple’s iBook Author

I’m going to admit that I am as intrigued as anyone about the new iBook Author app announced by Apple today.  It sounds as though it is an enormously powerful tool with which to build exciting and dynamic textbook content.  Apple being Apple, I expect that it will be beautifully designed, intuitive, and fun to use.  I look forward to playing with it — in one of my university’s computer labs.

Kathleen Fitzpatrick’s remarks in The Chronicle of Higher Education, “Reflections on the Apple Education Event,” seem to  me reasonable, carefully considered, and thoughtful.  I particularly liked her point about the lack of interconnectivity between users (i.e., students) built into the iTextbook format.

I’d like now to  explain why I won’t be rushing to use this tool myself to create new textbooks, despite the fact that it will assuredly do a fine job of just that, and will likely produce a much “better” product in some regards than I am capable of creating on my own.

1. Because, while I do have an iPad, I don’t own a Mac desktop, and have no intention of buying one just to run this app on it.

2. Because I have no desire to become an unpaid marketer for Apple Inc.  Nor will I effectively require that my students shell out hundreds of dollars, not merely for a tablet computer, but for a particular make of tablet.

3. Because Apple has been known to censor, rather unapologetically, apps containing content that it deems “inappropriate.” I teach, at both grad and undergrad levels, a course in 17th-century libertine literature that contains much material that is jaw-droppingly obscene. I don’t want Apple telling me, in effect, that I shouldn’t be teaching such things. And, in general, I just plain don’t like censorship.

4. Because I agreed with Stephen Ramsay when he tweeted that “We are so deeply and sincerely screwed if we allow an American mega-corporation to ‘help us reinvent the curriculum.'”

5. Because the new format for these iTextbooks does not support the ePub 3 open standard, and so is not only restricted to a proprietary platform, but is actively working to undermine open standards for digital texts.

6. Because I am already paid (by my university) to research and publish, and don’t want to commercialize what I produce more than is absolutely necessary.

7. Because I don’t want to become a chesspiece in Apple’s game of imperial domination. While I have no particular sentimental attachment to the current publishers of textbooks (and in some case, quite the opposite), I have no interest whatsoever in serving as a weapon in the late Steve Job’s proposed campaign to “digitally destroy” the textbook industry.

8. Because I want what I produce to be freely available to anyone, and usable on as wide a variety of platforms as possible, and not just on an iPad.

9. Because I dislike closed-source tools, and want to know what’s under the hood of such tools as I do use, and also what may be getting quietly embedded within such content as I produce by means of said tools.

10. Because, while I am quite happy to use tools to make the process of creation easier, I also enjoy coding and designing resources myself, and don’t necessarily want to have it all done for me.