• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

An Antic Disposition

  • Home
  • About
  • Archives
  • Writings
  • Links
You are here: Home / Archives for 2008

Archives for 2008

Comedy tonight!

2008/01/25 By Rob 1 Comment

Some people think I’m funny. Maybe it is because I like to listen to sea shanties as I blog. Maybe we just live in funny times. In any case, I’d like to highlight three things that have made me laugh this week. And trust me, I have exquisite taste.

First up is Tiffany Maleshefski in her eWeek Desktop Confidential column, and her critique of the Burton Group Report, written in the form of a love letter to Microsoft.

Next is Ecma’s Magic 8 Ball, the source of responses to your NB’s ballot comments, contributed by a reader who wishes to remain anonymous.

Finally, on YouTube, a droll faux-endorsement of OOXML by FFII President Pieter Hintjens called “Six Reasons to Migrate to OOXML“.

Filed Under: OOXML

The Standards Trolls

2008/01/21 By Rob 15 Comments

It is hard to resolve the pecking order of posters in the Microsoft blogger echo chamber. So let’s just remark that all the usual suspects assisted in this one: Doug Mahugh, Stephen McGibbon, Oliver Bell, Gray Knowlton, etc. Mix together, shake, repeat, turn the crank and presto! Out comes news.

Mary Jo Foley at least poses it as a question:

What’s your take? Are IBM and Google talking out of both sides of their mouths, when it comes to their “OOXML is evil” claims? Or is Microsoft increasingly grasping at straws, as the late February ISO vote on OOXML standardization inches closer?

Eric Lai, not to be outdone, comes up with the sensational headline “Lotusphere: Whoops! IBM products support Microsoft’s Open XML doc format”, a headline made all the more remarkable by the fact that the article has absolutely nothing whatsoever to do with Lotusphere.

Well, let’s look at the “evidence” Microsoft points to and try to make some sense of it.

First up we have the Lotus Symphony support forums, where in response to a question from a user about Office 2007 support, “supportadmin3” replied “Great idea Robert!!! I will submit your feature request to the proper team…Thanks!”

I don’t know what to say about that. It is a sign of fanciful desperation to turn the courtesy of “supportadmin3” into a statement of IBM support for OOXML. It is bizarre that anyone would portray this as more than courtesy.

What else do you have?

The thundering herd also pointed out this article from developerWorks last August on how to use ODF and OOXML with DB2 9 pureXML. Does pureXML support OOXML? It sure does!!! In fact it supports any well-formed XML document or fragment, OOXML, ODF, BerniesOldTimeMedicineShowAndJamboreeML, whatever you have. DB2 pureXML can handle it all, and let you query it via SQL or XQuery. Yes, OOXML and every other XML format known to man is supported!!!

[24 January It has come to my attention that the above paragraph has caused confusion among readers who are not familiar with the term “well-formed“. This is a technical term, defined by the XML standard. It essentially means that the XML will parse, that it follows the underlying syntax of XML. It is the minimum qualification for something to be called “XML”. It does not imply any fitness for a particular purpose, or any level of quality. It certainly does not mean the XML is “easy to process by standard XML tools”.

By analogy, I could say that a novel is poorly written, boring, in bad taste and artistically without merit, but at least the author spell-checked.]

What else do you have?

Ah, yes, there is the claim that DB2 Content Manager supports OOXML. Sorry guys, that page is just noting how to add MIME types for OOXML to Content Manager. Wow, you’re moving now. With apologies to Steve Martin in The Jerk:

application/vnd.openxmlformats-officedocument.wordprocessingml.document! I’m somebody now! Millions of people look at this registry every day! This is the kind of spontaneous publicity, you’re name in print, that makes people. I’m in print! Things are going to start happening to me now.

What else do you have?

Oh yes, Document Conversion Services, in WebSphere Portal. The claim is that DCS supports OOXML. Yes, indeed it does!!! DCS, via 3rd party code, supports 100’s of file formats. So OOXML joins the elite company of supported formats, along with XYWrite (1985), VolksWriter (1982) and Lotus Manuscript (1986).

I’m elated that Microsoft thought this DCS support was worth 6 blog posts. In fact in the 5 years since I designed and wrote the DCS framework (yes, ironically, I was the architect of that component) it has never gained such notice.

But here is something you might not know about DCS. Its main purpose is to handle the graveyard formats, the formats that you might rarely find in a document repositories,but don’t want to bother installing editors for on your clients. So instead of locating and installing dozens of legacy word processors, you simply have DCS run on the server and convert, on-demand, these legacy documents into a quick & dirty HTML rendering for viewing. So, DCS is great for handling those rare times when you run across an OOXML file.

So welcome, OOXML, to the exclusive company of “Every Document Format Known to Man” . I’m glad that you are so excited. But your desperation in trying to dredge up examples of support for OOXML, any examples, is so pitiful that I feel must offer some assistance.

Let’s start with the conformance clause for OOXML (Part 1, Section 2.5), the standards language that defines what an OOXML supporting application must be able to do, in order to claim it supports OOXML:

2.5 Application Conformance

Application conformance is purely syntactic; it also involves only Items 1 and 2 in §2.3 above.

  • A conforming consumer shall not reject any conforming documents of the document type (§4) expected by that application.
  • A conforming producer shall be able to produce conforming documents.

Or, in plain English, in order to be able to claim conformance with OOXML, an application must not crash when presented with a valid OOXML document, or must be able of producing at least a single valid OOXML document. This is not exactly a high threshold.

Some examples of applications that support OOXML by that definition:

  1. The DOS “copy” command is a conforming OOXML consumer and producer, since it can accept and produce valid OOXML documents.
  2. The DOS “del” command is a valid OOXML consumer, and one which I heartily recommend.
  3. WinZip, PkWare and every other Zip application out there are also conforming producers and consumers of OOXML.
  4. Every text editor and every XML editor and every other application that can consume text or XML also supports OOXML.
  5. Every web server and every application server, and every file system in the world can support OOXML if it can store an OOXML document without crashing or restore a valid OOXML document.
  6. A USB memory stick is also a conformant OOXML application, since it can consume and restore OOXML documents,
  7. An MP3 player is a conforming OOXML application, if it has a disk mode that allows files to be stored and restored.

Feel free to suggest your own nonsense.

By analogy to patent trolls, what we’re seeing here is the behavior of a standards troll — defining a conformance clause so vague that everything in the world is considered to support it, and then searching through competitor’s web sites in hopes of finding some place where they stumbled into supporting it, and then trying to extract some advantage from it.

The point should be to look for examples of where OOXML is supported to the highest degree, to point out the best examples of high-fidelity interchange that your standard allowed. You would think that with so many people at Microsoft with “interoperability” in their job titles, that this would be obvious. I guess not. But don’t be sad. You can always count on “supportadmin3” to cheer you up!!!

Filed Under: OOXML

You are Here

2008/01/13 By Rob 15 Comments

Within the next 24-hours, Microsoft will submit to JTC1 a set of proposals for addressing the 3,522 comments that accompanied OOXML’s failed ballot last September. We’ll no doubt hear a lot of yip-yip-yahooing on their end. Expect a major media campaign. I don’t want to take away the surprise, but I’m hearing that journalists are being flown into Redmond next week from around the world for briefings on OOXML. So, for their benefit, and yours, let’s review where we are in the JTC1 process.

What has happened so far?

OASIS OpenDocument Format (ODF) is the current ISO standard (IS 26300:2006) for XML-based word processing, spreadsheet and presentation documents. By using an open standard format like ODF, consumers avoid vendor lock-in and are able to have a choice of suppliers. ODF is widely supported by vendors, in both commercially-available and open-source software, and is seeing strong adoption world wide.

In early 2007 the European Computer Manufacturer’s Association (Ecma), after a superficial review clothed in secrecy, submitted the Microsoft-authored document format specification, Office Open XML (OOXML), to ISO/IEC JTC1 for approval as an International Standard. This provocative submission occurred only three months after JTC1 published OpenDocument Format (ODF) as a unanimously approved International Standard.

OOXML has been widely criticized as flawed standard, having been designed with only a single vendor’s objectives in mind and designed to work fully only with that vendor’s products. Also, in its rush to catch up with ODF, OOXML was submitted to JTC1 in an immature state, hastily written and insufficiently reviewed. At the time it was approved by Ecma, there were zero commercially available implementations of OOXML. The only support was in the beta version of Office 2007.

In a preliminary 30-day “contradiction period”, JTC1 member bodies were invited to raise objections if they believed that the OOXML submission contradicted existing ISO or IEC standards. Twenty countries responded in this period, most of them raising concerns over OOXML. Several NB’s raised objections to the extreme length of the proposal (over 6,000 pages) and raised IP concerns. JTC1 administrators effectively ignored all of these objections and proceeded to a 5-month ballot.

On September 2nd, 2007, after a 5-month review period by ISO/IEC JTC1 national bodies (NB’s), the ballot to approve DIS 29500 Office Open XML (OOXML) failed, not reaching the required 2/3 approval by JTC1 P-members. This ballot was tainted by many documented irregularities. Over 3,500 comments were submitted by NB’s with this ballot, documenting specific errors, ambiguities and omissions in the OOXML proposal.

What is next for OOXML?

JTC1 procedures allow a proposer of a failed standard the opportunity to respond to the ballot comments submitted, in hopes of persuading members to change their vote from disapproval to approval.

This procedure occurs in several steps. In the first step, the formal proposer of the standard, Ecma in this case, writes a Proposed Disposition of Comments report, in which they recommend their proposed resolutions for each comment from the September 2nd ballot. This is the document that is due on January 14th.

We’ve seen draft versions of these proposals resolutions, but they were provided in a rough form, impossible to review, as 3,000+ separate PDF files, amounting to over 5,000 pages, ordered alphabetically by the country that made the underlying technical comment. This is not exactly a convenient arrangement for seeing, for example, all comments related to spreadsheet date serial numbers, or for doing any other topical review. So it will be good to finally have Ecma’s full Proposed Disposition of Comments report, which presumably will be in a more usable format.

Note that the Ecma submission on January 14th will be non-binding, merely a set of proposals. Ecma does not have the power to change a single line in OOXML, since the proposed standard is under JTC1 control. Ecma can propose solutions to comments, as can JTC1 members themselves, as they did in in great numbers in the proposals that accompanied ballot comments on September 2nd. No changes are actually made until approved by the Ballot Resolution Meeting (BRM). This fact should be kept in mind as Ecma reviews with some NB’s a draft of their Proposed Disposition of Comments Report. This is just a proposal at this stage.

What about the BRM?

The BRM, or Ballot Resolution Meeting, will occur February 25th-29th in Geneva. All NB’s who voted on the September 2nd ballot are able to attend, and approximately 35 NB’s are planning on sending delegates, with attendance expected to fill the hall to capacity, 120 people. Ecma can attend, but they cannot vote.

The BRM, preferably by consensus, though formal votes are also possible, will agree on a set of changes to the text of OOXML. Proposals for changes may come from Ecma’s Proposed Disposition of Comments report, as well as from NB ballot comments. Resolutions may be debated, amended, substituted, approved, rejected, etc., according to a vote of the meeting. Or at least that’s my understanding. The actual documented BRM process in JTC1 Directives is entirely inadequate, with a lack of detail that is better suited to the by-laws of a Ladies Over-60 Bowling League than it is to ISO. The Convenor of the BRM, Alex Brown has the unenviable task of consulting bird entrails or performing whatever other divinations are required to turn JTC1’s vague scratchings into a working meeting. We wish him luck !

At the adjournment of the BRM we will have be an agreed-upon set of editing instructions for the Ecma Project Editor to apply to OOXML. Only changes approved by the BRM may be made to the standard. Note that the BRM does not indicate approval or disapproval of the OOXML standard itself. Its purpose, its technical role, is merely to make changes to the text of the standard.

What occurs after the BRM?

After the BRM adjourns (February 29th) there will be a 30-day “reconsideration” period in which those NB’s who voted on the September 2nd ballot will be able to change their vote. They can change their vote in any direction, from approval to disapproval, approval to abstention, abstention to approval, abstention to disapproval, disapproval to approval, or disapproval to abstention.

Note that the criteria for the vote is the same as on September 2nd – Should DIS 29500 Office Open XML be approved as an International Standard? It is not a vote on the BRM, nor is it a vote on Ecma’s Proposed Disposition of Comments. The question on February 29th is the same question as Sept 2nd — Is the DIS 29500 proposal acceptable?

Filed Under: OOXML

A Brief History of Open

2008/01/03 By Rob Leave a Comment

Circa 1700 BC, the Babylonian king Hammurabi ordered the laws of his kingdom be engraved on a black stone slab and displayed in the city center for all to see. This was mostly for show, since the number of people who could read Akkadian cuneiform were probably as small then as now. But the symbolism was clear: the Law is fixed (indeed carved in stone) and not improvised at the whim of the magistrate. Of course, the Law was not popularly determined, and certainly all were not treated equal, but still this was progress.

1215 A.D., along the Thames in Surrey, at the meadow called Runnymede, a group of English Barons joined their powers together to force their monarch, King John, to affix his seal to Magna Carta, establishing that even the King himself was bound by the Law.

Philadelphia, the hot summer of 1787, representatives from 12 of the 13 American states met in Convention, at first with the aim of enhancing their current loose affiliation, but eventually agreeing upon a much more ambitious Federal form of government in their proposed Constitution. This document was far from perfect and needed ten major additions before it was considered ready for use (thus the Bill of Rights). Over the next 200 years additional problems were detected and fixed (via further Amendments) according to an process that emphasized openness and participation of all concerned parties.

These of course are three examples of the progress of openness. All can be called “open” but they are not all of the same degree of “openness”.

For example, the Code of Hammurabi was open in a sense, since it was publicly documented for all to read. But this openness is of small consequence to the builder’s son who could be legally stoned to death if a house his father built collapsed and killed it’s owner’s son. The Code was “open” but still allowed crimes committed by one person to be judicially imputed onto another party.

Similarly, the U.S. Constitution was even more open, since it was publicly documented and also well-deliberated and formed as part of a consensus process. But it still allowed slavery and denied the majority of its population the right to vote.

At the risk of falling into a teleological argument that sees all of human history leading inexorably to modern America, it does seem that the general flow of history has been:

  1. A move from undocumented or improvised laws to laws that are fixed and publicly documented.
  2. A move from laws created by a single entity to laws formed as part of a deliberative, multilateral, consensual process.
  3. A move toward increasing inclusiveness as to whose interests are considered.

So we should never stop at a claim of “openness” and say that with the mere application of this label that all diligence has been performed. You need to ask yourself always, whose interests have been taken into account? All? Many? Few? One?

There seems to me to be a natural parallel here with the “open standard” moniker. Is it a single fixed and unitary concept that admits of no degrees? Or are there a wide range of standards which share the concept “open” to one degree or another? How thinly can the concept be diluted? Can it be homeopathically prepared, with one drop enough to inoculate gallons?

I think the key is to move away from the mere consideration of the process of standardization and to also consider the content of the standard. Just as a Constitution that held that women could not vote was far from open, even though it was drafted in an open committee process, a standard that does not facilitate use by competitors is not open, regardless of the process that created it. We need to move beyond strictly process-oriented definitions of openness and bring in considerations of content and results. A standard can be per-se non-open if its content violates important principles of openness.

Filed Under: Standards

The Piemen of Erie

2008/01/02 By Rob 13 Comments

An interesting historical anecdote to relate, from our nation’s industrial adolescence, a tale with relevance today when we discuss standards.

The year was 1853 and the place was Erie, Pennsylvania, a town at the junction of two incompatible rail gauges. This gauge incompatibility was inefficient and frustrating, but the citizens of Erie loved it, and resisted every attempt to join the emerging common standard gauge in what would be called the Erie Gauge Wars. Why? Let’s find out more in the words of industrialist and historian James Ford Rhodes from a passage quoted in extenso from his 1895 History of the United States from the Compromise of 1850 to the McKinley-Bryan Campaign of 1896 (Vol III Pages 18-23). I will follow this by some additional thoughts.

For the prosperity of 1846-57 there were several contributing causes, either special to that period, or then for the first time effective. The greatest of these (whose influence, continuing with ever-increasing momentum to our own day, is still transcendent, and will pervade the future to a degree to which no philosopher can now set bounds) were railroad transportation, beginning its first great era, and the coming into general use of the electric telegraph. We may mark the year 1849 as the commencement of railroad extension. Having less than 6,000 miles January 1, 1849, the country had at the end of 1860 30,635 miles. In 1850 it was impossible to go by direct railway from New York to either Albany or Boston; in 1860 New York had continuous lines reaching beyond the Mississippi. In 1850 Chicago had one short road; in 1860 that city was a great railroad center, her main lines “reaching hundreds of miles — east, west, north, south. In 1850, Ohio, Indiana, and Illinois were open fields; in 1860 they were crossed and recrossed many times.” “I arrived here last night,” wrote Emerson from Pittsburgh in 1851, “after a very tedious and disagreeable journey from Philadelphia, by railway and canal, with little food and less sleep; two nights being spent in the rail-cars, and the third on the floor of a canal-boat.” Not until the end of 1860 did the railway system between the East and the West approach unification and give promise of that consolidation of separate railroads and branches into systems which in our own day has characterized this development.

The primitive ideas in regard to railway travel prevailing in the decade of 1850-60, are well illustrated by what was then known as the Erie Railroad War. The traveler who goes from New York to Chicago in our day is not obliged to set foot from his train, for he is provided with the comforts and conveniences of a hotel. Far different was it in 1853. The traveler could, indeed, then go from New York to Albany in four hours; but there he must change to another road and another train which carried him from Albany to Buffalo, and he esteemed himself fortunate to be able to cover so great a distance in the same car. If he made the western connection at Buffalo it was considered good-luck. The tales of those days are full of complaints of trains behind time, of connections missed, of tedious delays. From Buffalo the traveler had a short run to the station on the line between New York and Pennsylvania, called State Line, where, on account of a difference in gauge, a transfer was necessary. On the broader gauge he could travel twenty miles to Erie, Pa., when he must change again to a road of the Ohio gauge. The train on this railroad carried him to Cleveland; but on the way, if at all late, he was subject again to the anxiety of missing connections. At Cleveland he must hurry to the river, where a scow, carrying at most a dozen passengers and sculled by a weather-beaten mariner, was used as a ferry to take passengers to the Toledo railroad station. In this open boat travelers suffered from exposure to rain and snow; at times the waves ran high and the crossing was attended with danger. If the eastern train was crowded or a few minutes late, haste was necessary to secure passage in the first trip of the scow, for it was well known that the Toledo train started on schedule time and waited for neither train nor boat. At Toledo the traveler made the last change, and — if not more than five minutes behind time — found the Michigan Southern train awaiting him; otherwise he had a tedious delay, which, if his arrival at Toledo happened on a Saturday, might extend to thirty-six hours. The traveler from New York who missed no connections and arrived at Chicago on time had a marvelous story to tell.

The railroad managers of the lines between Buffalo and Erie, eager to improve their route, decided to alter the six-foot gauge of the railway between State Line and Erie to four feet ten inches — the gauge of the roads east of State Line and west of Erie — so that passengers could go from Buffalo to Cleveland without change. The railroad ran a distance through the streets of Erie. The Erie municipal authorities refused to give a permit for making the alteration unless the railway company would agree to stipulations to which its directors, considering them unreasonable, declined to accede. In the contest which followed, a color of law and reason was given to the position taken by Erie; but no one was deceived as to the real ground of the trouble. Erie objected to the change of gauge because the transfer of passengers and freight was deemed important to the borough’s prosperity. The wait involved brought custom to her eating-houses; the transfer of freight and live-stock gave work to her people. The populace ignored the legal points and the pretended grounds of demur, but they keenly appreciated the vital objection.

On December 7, 1853, the railroad company began at State Line the work of changing the gauge. The news came quickly to Erie. A cannon was fired to call out the citizens. A large mob assembled, tore up the track, and cut down the railroad bridge in the borough. The infection spread to Harbor Creek, a Pennsylvania town seven miles east of Erie, and that evening its citizens held an orderly meeting and resolved to remove the track of the railroad running on the public highway. The resolution was the next day carried into effect. Two days later (December 10) the track of the new gauge was completed to the borough limits of Erie. That night rioters at Harbor Creek tore up the track, destroyed the bridge, and ploughed up part of the grade of the road. War had begun in earnest. The mayor and the sheriff at times directed the mob, while the local militia, arrayed for service, swelled its number. Even the governor of the commonwealth seemed to sympathize with the Erie people. Certainly they had the sentiment of the whole of Pennsylvania on their side. The United States Circuit Court then granted an injunction restraining all persons from interfering with the railroad company. An Erie justice of the peace pronounced the injunction null and void, and the populace, believing the later decision to be the better law, refused to respect the order of the court. Two days after Christmas, the Harbor Creek bridge was torn down for the fourth time.

The contest attracted the attention of the country. In Buffalo the excitement was intense. Cincinnati held an indignation meeting presided over by Thomas Corwin, to protest against the conduct of the Erie citizens. The New York Tribune said: “Let Erie be avoided by all travelers until grass shall grow in her streets, and till her piemen in despair shall move away to some other city.” The press of Philadelphia espoused the cause of Erie. The City of Brotherly Love held a large public meeting to express sympathy with the borough at the other end of the commonwealth. It was declared that “the only protection Erie has to prevent her own ruin is to require the break to be made within her boundaries.”

About this time Horace Greeley had occasion to go West. He wrote to his newspaper that he was obliged to ride the seven miles from Harbor Creek to Erie in an open sleigh “through a cutting storm of wind, snow, and sleet…. Let Erie have her way,” he continued,” and all passengers and freight must change cars before her pie-shops…. The whole world is to be taxed, as in the days of Caesar Augustus, in order that Erie may clutch a sixpence for every dollar of expense she imposes on others. Is it strange that so mean and selfish an exaction should be enforced by mobs, arson, devastation, and ostentatious defiance of judicial mandates?”

With the new year the excitement grew. The Erie people became vindictive. They warned the president and director of the railroad company, living at Erie, to leave the borough. Women joined the rioters and assisted in the work of destruction of the bridges. The New York Tribune called upon President Pierce to interfere, and suggested that he issue a proclamation and call out troops in order that the laws might be executed. “Had a runaway negro,” this journal said, “been somehow mixed up with the matter, we should have had half of the United States army in Erie a month ago.” The trouble brought into view the rivalry between New York and Philadelphia, between New York State and Pennsylvania. The Commonwealth of Pennsylvania was declared an accomplice with the Erie rioters and bridge-burners, for the purpose of diverting business from the West to the seaboard through her territory and to her port by a projected line from Erie to Philadelphia, and an appeal was made to the West to frustrate her purpose. It is possible that the sentiment of the West had some influence in bringing about a settlement; but in the early part of January, 1854, the minds of Northern men became engrossed with the proposed repeal of the Missouri Compromise, and the Erie war ceased to attract attention. An act of the Pennsylvania legislature, by a fair compromise, brought the trouble to an end. The railroad company, having consented to confer certain desired advantages upon Erie and Pennsylvania, was allowed to complete the change of gauge and run its trains through Erie without molestation.

So, what do we have here? Two, incompatible standards meet in Erie. Maintaining the two standards is wasteful, inefficient and expensive to the railroad owners, and causes great inconvenience to the travelers who pass through Erie. Everyone knows this. However, the shopkeepers and laborers of Erie benefit from directly from these circumstances. This situation is common. We don’t all benefit from the same things. Some people benefit from other people’s misfortune. War is good for arms dealers. Hurricanes are good for the glazier. Tuberculosis is good for the undertakers. And two incompatible rail gauges are good for those whose livelihood depends on jobs manually loading and unloading goods at the junction, or providing refreshments to those who must wait for connecting trains. In any change, there are winners and losers, those who benefit from maintaining the status quo, no matter how inefficient it is, and those who will benefit from change.

So what do you do? Choose a commercial interest? Line up behind either the rail barons or the teamsters? Not necessarily. In the end the competing commercial interests don’t amount to a hill of beans compared to the interests of the travelers, the consumers and the public at large. They are the ones who were absorbing the cost of maintaining two rail gauges, in shipping costs and frustration, and they are the ones who benefited from the convergence on a single standard. Sure there were two commercial interests vying for supremacy, but there was also a choice that was clearly better for the public.

So whenever anyone tells you that two office document format standards is a good idea, that plugins and convertors can deal with shuffling data back and forth between two formats, ask yourself some basic questions:

  1. Who benefits from having two standards? Who are the “pieman of Erie” that will make money off of the inefficiency that results?
  2. Who has the most to lose if Erie becomes just another railroad town, one of many?
  3. How far will the piemen of Erie go to protect their monopoly? What technological advances and innovations will they prevent or actively destroy in order to preserve their exclusive access to their customers?
  4. And most important, what about the interests of the public at large? What is good policy?

If Microsoft were fighting the Erie Gauge War, they would portray it as a fight between the good townspeople of Erie and the rail barons. The big bad mean old rail barons are forcing their single gauge standard on people who don’t want it. Why not give them the choice of gauges? Only the old broad gauge is 100% backwards compatible with the cars that were designed for it. In fact legislation should be passed for force all railroad towns to support both gauges so everyone can have the choice. Piemen of the word, unite !

That is the distortion you get if you look at a standards war through the narrow blinders of commercial interest. But if you look at the full market impact, the simple economics of it, it becomes a lot clearer. What brings greater efficiency, greater fidelity, greater innovation and lower costs? Having two incompatible document format standards? Or having a single harmonized document format standard? Fighting against economics is like fighting against gravity or the 2nd Law of Thermodynamics. You are going to lose in the end. The piemen of Erie, and their modern counterparts, are on the wrong side of economics, and history,

Filed Under: Standards

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 8
  • Page 9
  • Page 10
  • Page 11
  • Go to Next Page »

Primary Sidebar

Copyright © 2006-2026 Rob Weir · Site Policies