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 25 Aug 12excerpt: "Is your 802.11n router not keeping up with your 100Mbps downpipe, dropping HD video streams and copying files at mindboggingly slow speeds? We've got 10 remedies that will help. By Sandro Villinger, ITworld | May 09, 2012, 4:44 PM - The first 801.11ac chipsets are coming soon, but 802.11n is likely to stick around for many years to come -- both in the business world and our homes. Unfortunately, the 300Mbps (megabits per second) that the n-standard promises rarely delivers anything even close and proves to be a massive bottleneck in the days of 50/100Mbps (or more?) broadband connections, 1080p video streaming, massive backups and so forth. On the business side of things, even menial tasks such as remote desktop or real-time collaboration suffer from a poor Wi-Fi-connection."
