The chart shows different types of publisher content organized in a two dimension graph with potential for reuse on the X axis and content complexity on the Y axis.

I like the chart for a number of reasons:
- It smashes the myth that content reuse is only for long-lived STM or educational content.
- It reframes the debate from black & white to gray. Too many times, I've heard people say content type X is or isn't reusable. In reality, it's a matter of degree.
- It shows that certain types of non-STM, non-educational content are indeed highly reusable -- e.g., reference, tourism, and cooking.
Today, with e-books on the rise and the need to deliver book content in multiple e-book and non-traditional book (e.g., large print) formats, trade publishers are increasingly moving towards XML. But, they shouldn't be focused just on content delivery; they can be equally -- if not more -- focused on content repurposing and reuse.
Suppose you had a collection of travel guides which contained information on hotels and restaurants in a number of French cities. You should like XML because:
- You want to deliver content to multiple formats easily: print books, e-books, the web, iPhones, etc.
- You are already reusing content of necessity and would like to make changes only once. A great restaurant might be in both the Brittany and the Best French Restaurants guides and when its phone number changes, you want to change it only once (and approve those changes only once) in your contentbase.
- You want the opportunity to cherry-pick and/or slice-and-dice your content to create new products quickly. For example, you might grab the 20ish cities in which the 2009 Tour de France stops and create a Tour de France 2009 guide. Or, if you had recipe content, you might want to slice the recipes that require less than 30 minutes into a Quick Meals cookbook, or those with less than 500 calories into a Light Meals cookbook. Or, perhaps do both with Light Quick Meals or, while we're at it, Light Quick Vegan Meals or Light Quick Mediterranean Meals?

4 comments:
Hi Dave, I very much enjoyed your post on [...]
I’m sure you know of this, but in case you don’t: Offbeat Guides shows a good example of chunking not-so-chunkable travel content.
Best,
Dan
I got the prior comment from a friend via email and posted here myself /dk
Thanks, both for investing the time with the research paper and highlighting this part of the report.
got this over email but sharing with everyone:
You could add that there is an additional benefit to putting travel guides in XML: it makes the content ready for the mobile device. Here is the idea: your iphone (or any other GPS enabled device) tells the publisher that you are near the Eiffel Tower. The mobile application can now pull content about other places of interest nearby like the Ecole Militaire, or if the application also detects that it is lunch time in France suggest some nearby restaurants that the guide recommends. Once the content is in XML format these applications are easy to develop. Customer benefit: you can leave the paper guide at home and travel light. Business benefit: you differentiate your travel guides from the competitors in a major way.
Post a Comment