Challenges: Some Ugly Truths
The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition.
Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper.
A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition.
And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5]
But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
Gary Edwards on 05 Jul 12Control vs. Creativity. As the ulitmate control freak, Ballmer was guanteed to crush the life out of Microsoft's most creative individuals and teams. Gates was focused on Windows and MSOffice, and Ballmer on control. That one-two punch made certain that Microsoft would not be a player in the next great wave of computing; The Cloud. excerpt: This is yet another example of what I like to call the Wile E. Coyote syndrome. Like the unfortunate character in the old Warner Bros. cartoons, Microsoft now seems to be a company that has long since run off the cliff but, with legs spinning for all they are worth, doesn't know yet that it is ready to drop. Yet drop it most certainly will. Microsoft Win8 Tablet Is NOT a Game Changer Adam Hartung Contributor Snapshot: Steve Ballmer Follow (93) #44 Billionaires IDC Analyst: Microsoft's Surface Sizzle Needs Win8 Steak Daniel Nye Griffiths Contributor To understand how this happens, take a look at the work of Arnold J. Toynbee, a historian who studied the rise and fall of civilizations. He argued that a civilization flourishes when it motivates insiders and attracts outsiders with its creative dynamism and culture. The civilization breaks down when its leadership loses this creative capacity and gives way to, or transforms itself into, a dominant minority. When this happens, the driver of the civilization becomes control, not attraction. And it's precisely this switch from attraction to control that is the source of the breakdown. Interestingly, Toynbee says that the consequences may not be immediately apparent. A civilization can keep up momentum because the controls it puts in place generate some short-term efficiency. But eventually it will run its course and collapse, because no amount of control can replace the loss of collective creativity. Observe this in the corporate world by looking at the example of General Motors. G.M.'s 2009 bankruptcy came at the end of a long decline dating back to the early 197
