Podcast: The Myth of Single Sourcing
December 21st, 2009 | Posted in Podcasts 8 Comments »
Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.
Download MP3
Length: 38 min.
In his controversial post, The Myth of Single Sourcing, Michael Hiatt explains:
Single-source publishing is a zombie idea that revives itself periodically and refuses to stay dead. Its zombie supporters chant its purported benefits as a “write once, publish to many” promise and ploddingly follow it as their ultimate goal for mechanized authoring and machine translation. As an object-oriented writing methodology, it is as human as present-day robot technology—good only for conveyor belt assembly or specialized tasks, and always very expensive to implement. Single-source publishing lacks purpose in today’s world of information turnover and the dynamic nature of the Web 2.0 moving to Web 3.0 landscape.
In other words, single sourcing your content across the enterprise is an idea that simply doesn’t work. I responded to the post and had a lively exchange in the comments, so I decided to interview Michael for a podcast.
In this podcast I talk with Michael about single sourcing, collaborative authoring, mashups, help authoring trends, and other topics. You can follow Michael’s blog at Mashstream.com.
(Note: We had a brief Skype issue at the start. The audio gets noticeably better at around the 5 minute mark. It’s actually a great example of the clarity that the double-ender recording technique provides instead of just using Skype to record.)
Sponsors
Tags: help authoring, mashups, michael hiatt, myths, single sourcing
If you liked this post, keep updated with new content: Subscribe to I'd Rather Be Writing.
Both comments and pings are currently closed.
Mark Baker (5)
DiSc (3)
Jen (3)
Neal (3)
Richard Hamilton (3)
Ellis Pratt (2)
Jenny (2)
Sarah Maddox (2)
Sarah O'Keefe (2)
Stefan Kleineiken... (2)
That was an incredible interview. Thanks to Tom for conducting it, and to Michael for sharing his insights.
It’s probably fair to say that Michael thinks a lot farther outside the box than I do. He and I both see the “cloud” full of information, and we both recognize the need (and the opportunity) for synthesizing that information.
Here’s where we differ: I see all of this happening within the old “single-sourcing” paradigm. He’s saying that the old paradigm has to yield to a new paradigm. The old wineskin can’t hold this new wine.
Now that I have a better grasp of what Michael is saying, I think that he’s probably right.
Larry, thanks for taking the time to give me feedback and respond to the podcast. I think the whole term “single-sourcing” tends to be slippery and mean a lot of different things to different people.
I am also musing on what single sourcing means and its role in the future. I am disenchanted with large-scale implementations, but still see a need for topic-based articles and reuse of objects at some level. I’m still looking for it’s rightful position in structuring my own content internally yet publish externally with highest quality. I’m still looking for some kind of object-oriented base-class-with-extended objects type of approach. This is still a big question for me.
What I do believe is this (at least for today):
–web services and info is where apps and doc will be single sourced. Semantic markup will identify content and ontologies will be built to connect and deliver.
–no proprietary platforms. This means MS Word and FM files, Vasont CMS database records, or Madcap/Robohelp files for documentation. As services go to the cloud, so goes content. Programmers are using web APIs to mash functionality; writers need to use XML and semantic markup to mesh information.
–In the near future, customers aren’t coming to your book, application, or website. You need to go to them and fit into their places of congregation and virtual interaction.
Michael provides a first-rate discourse on the failed promise of single sourcing in theory and practice. Some (STC, etc.) made a cult of it but the dynamics of the marketplace moved faster.
Single sourcing can work where the content repeats, but so much material and the larger world (the marketplace, software, applications…and people) has dictated that custom content seems to trump single sourcing most times, IMHO.
(And Tom…very focused questions. Good job.)
[...] me of followup comments via e-mail « Previous Post Next Post [...]
I wonder if you could include a transcript with your podcasts? It would help people like me who aren’t inclined to listening to podcasts. I prefer reading because it’s faster (for me), plus I have the flexibility of skimming and of going back and forth between paragraphs.
I keep thinking it would be great if all podcasts and videos could have an “interactive transcript” feature like the TED talks website. For an example, see http://www.ted.com/talks/nick_veasey_exposing_the_invisible_1.html
While I agree there is usually a greater quantity and even quality of documentation “out there” on the web the solution is not to create a link repository which points to all those other resources.
Depending on external content to still be there in a month, year, etc is foolish.
The external content needs to be gathered and stored in a central repository owned by the subject group. The ongoing search for external content should continue but the result should be a copy of that material stored in the central repository with a capable documentation manager spending the time and effort to monitor it all.
Time log of the interview.
00:00 Introduction (mashstream.com, idratherbewriting.com)
01:52 Michael Hiatt’s background
04:18 Summarize why single-source is not viable.
08:09 Clarification: personal content reuse v. enterprise content reuse
10:10 Single-source can be a workable solution for specific cases
11:30 Integrating information from several sources
– pulling from the Cloud or Semantic Web
– dealing with disparate formats
– providing context and links
19:40 What is linked data? (Adobe’s help that polls a variety of sources?)
23:12 Tool vendors’ evolution of tools that make linked data available
25:00 A new roll: the information-content manager or content strategist
– education’s roll
– students’ roll
– the in-house writers’ roll
32:00 Blog: mashstream.com
33:45 The hired-hand writer and the controlled message
35:40 Conclusion