Advanced

HI Researcher Continues OpenDocument FUD

Posted by grouch on · 16 comments
LXer Newswire; By DC Parris
Mail this story
Print this story

  LXer Feature: 14-Jun-06

Steven Titch, a Senior Fellow at the Heartland Institute, first drew my attention when I ran across an article he wrote, in which he made so many misleading statements, I called into question his abilities as a researcher. Two blog posts later, Titch still fails to address facts, to present any evidence in support of his arguments, to make any arguments relevant to the issue at hand, contradicts himself... Need I go on? One wonders if he is even in the same ball park.

The Summarized Version



Let's review. First, Titch wrote an article in which he makes some pretty sorry claims, most of which had little to do with the argument at hand, and misled his audience with respect to some crucial facts. After I called into question his credibility as a researcher, and compared his report to Welles-ian fiction, he then blogged that I had failed to address his core argument. I responded that his core argument was a non-issue since no one was arguing about that anyway. Now Titch comes back for yet another embarrassing play - even more embarrassing than Bill Buckner's error.



Here I'll simply summarize my view of Titch's blog. If you want the instant replay, you'll find it below. Suffice it to say that Titch, for all his knowledge of Bill Buckner's error, allows himself to commit the same error. Titch hasn't learned a thing from Buckner - or even his own errors - in this match. If you examine Buckner's overall record, he was an outstanding ball player - even if people never remember anything other than his famous error. Titch, on the other hand, fails to show his mettle as a researcher.



In his blog, Titch continues complaining that the Massachusetts ITD decision is about procurement, despite my specific reference to a direct quote explaining that it was a standards policy - not a procurement policy. He never once demonstrates how the standards policy is really a secret anti-Microsoft procurement policy. In fact, he never demonstrates how the policy is anti-Microsoft. He never explains how the debate is about Microsoft Office vs OpenOffice.org, which is especially absurd in light of the 32 applications that either currently support ODF or will in the near future. Titch continues to argue that the policy is anti-Microsoft in spite of the overwhelming evidence that Microsoft is capable - legally and technologically - of supporting ODF.



Failing any useful facts, Titch resorts to trollish tactics. Having just made a big deal of Microsoft vs OpenOffice.org, he then calls on the "zealots" to focus on the merits of ODF. Even though I have written in my responses how ODF is more mature and more "open" than Microsoft's own XML, Titch never even touched the merits of Microsoft's XML or ODF himself. He never addressed why Microsoft could not have contributed to OpenDocument's development. In fact, he seems to be missing whole portions of the original debate, along with the updates to those issues.



At this point, it no longer even matters whether Steven Titch is intentionally misleading his audience or just incompetent. His credibility as a researcher is a shambles. While I have corrected his errors, backed up my claims with supporting evidence, and refuted his claims soundly and profoundly, he has yet to offer any evidence that he is a competent researcher. In my view, a competent researcher should be able to analyze/discern the core issues, discover and weigh the various facts concerning those core issues, and present evidence/facts to support any arguments he or she may make with respect to those core issues. Yet Titch has attempted to make this debate about an anti-Microsoft stance while accusing the "zealots" of his own behavior. In any forum that's considered trolling.



References




The Instant Replay



This version is much longer, but is included for those who really want the play-by-play for this last inning of the game.



"As I wrote in "The Dangers of Dictating Procurement", the Massachusetts Information Technology Department (ITD) has made it policy that it will no longer procure software that does not support open standards."


Actually, he mistakenly referred to an "open source software format", not an open standard. Since I called his bluff, readers might be able to better grasp what was mandated. He then claims that the decision knocked Microsoft out of future bidding, but ignores Microsoft's choice not to meet the Commonwealth's request. This crucial fact, which Titch refuses to address, would cost any company their bidding prospects in nearly any scenario.



"That's because a major competitor to Microsoft Office is OpenOffice.org. OpenOffice is open source software that supports an open standard called OpenDocument Format (ODF). It has been incorporated into software products from Microsoft competitors, such as Sun Microsystems StarOffice."


OpenOffice.org is one example. It has also been, or is being, incorporated into at least 32 other office productivity and Internet applications. However, this point is interesting to note because Titch is trying to paint the battle as Microsoft vs the FOSS community. It is also interesting to note that Titch previously claimed that OpenOffice.org was hardly getting any traction at all in the marketplace. Come on, Titch! Which is it? Your readers want to know.



"Today, have a few drinks with an open source geek and he'll tell you, perhaps not in so many words, that while Microsoft's response to the Massachusetts directive was a clumsy swing resulting in a slow grounder to the right side of the infield, the ODF team has Bill Buckner at first base."


I don't know what open source geeks Titch is drinking with, but they must be too busy hacking code to know what's going on in Massachusetts. You see, the OpenDocument Format has already been adopted. Even if Microsoft's format is accepted by Massachusetts, ODF will still be used as well. In fact, some documents will have to be available in ODF since Microsoft's XML format and licensing may not permit other office suites to properly render the binary data included in the schema.



"Much of the controversy about the Massachusetts directive centers on the replacement of Microsoft Office with OpenOffice.org."


O.k., so now Titch just let the ball roll right between his legs. Don't you just hate when that happens? See, instead of keeping to the topic of open standards, Titch is still trying to re-cast the debate in terms of Microsoft Office vs. OpenOffice.org. It is true that many would love to see OpenOffice.org replace Microsoft Office - for a variety of political and technological reasons. It is also true that Microsoft has a vested interest in maintining its monopoly position in the marketplace. Even so, ODF is much bigger than OpenOffice.org. Recall the 32 applications mentioned above currently implementing ODF?



Here's the thing. Titch misses the ball - and not for the first time in this game - that Massachusetts mandated adherence to a standard that Microsoft could have implemented, thus saving all of us the words wasted on a stupid debate about standards. Titch fails to show any evidence at all that the battle is about OpenOffice.org replacing Microsoft Office. Titch never even touches on the fact that Microsoft could have implemented ODF in its office suite. That's because he wants his audience to believe that we're arguing about something that we're not even arguing about.



"Unlike Linux, which is a leaner, more elegant operating system than Windows, especially for servers; or Mozilla Firefox, which has had none of the security problems of Explorer, Office is a strong and popular product. It may be expensive, but users like it."


Frankly, it really seems as if Titch is trying to make up for his failure to do any research at all for his previous articles. To suggest that Microsoft Office is popular is akin to suggesting that mousetraps are popular among mice caught in them. The fact is, there are essentially two reasons people use Microsoft Office:

  • They don't know they have any other choice (often true)
  • They know the choices they have cannot reproduce the documents as effectively as the latest, greatest copy of Microsoft Office.



That last point is the crux of the matter. With a standardized document format, everyone can compete on the same terms while achieving real interoperability - or at least improving it tremendously. This actually increases competition in the marketplace.



Currently, users are enticed into using Office, and since no other office suite can implement the unpublished, non-free document formats as well, they're stuck with the hefty expenses of Office. That goes for governments as well as businesses, non-profits, and individuals. The OpenDocument Format is usable by any office suite, including Microsoft Office. This means that, as long as the office suite implements the OpenDocument Format in a usable way, I can read documents from other users, regardless of what office suite or operating system platform they use.



I have used OpenOffice.org on Windows, SUSE Linux, and Ubuntu Linux with no variation whatsoever in the document from one operating system to another. That would currently work with KOffice and StarOffice as well. I could not try that if I wanted to with Microsoft Office, which only runs on Microsoft Windows. Even when Office 2007 comes out, with the new XML format, I will likely experience problems opening the files, since the Office "Open" XML format specification allows for proprietary, binary data to be included in the documents via a binary data tag. OpenDocument, being strictly XML, is the only way to guarantee another user will be able to read your documents.



"It may be expensive, but users like it. It’s highly debatable whether a state government, which has fiduciary responsibilities to taxpayers, should be using its resources and purchasing power to provide the necessary traction for Microsoft competitors that they can’t get in the marketplace."


Titch ignores the monopoly position Microsoft currently holds in the office productivity marketplace, as well as their responsibility to meet the customer's reasonable requirements. One cannot call a few copies of Wordperfect "competition". It is the government's fiduciary responsibility to taxpayers that led the Commonwealth of Massachusetts to ensure that any business, Microsoft included, has the opportunity to compete, based on open standards that any vendor can implement.



It is Microsoft that has a fiduciary responsibility to its investors - and users - to implement open standards, or risk the loss of business that would inevitably result from any vendor's refusal to meet its customer's requirements. Even Titch acknowledges that Massachusetts' requirement is a legitimate one. What he fails to acknowledge is Microsoft's refusal to support the requirement, despite the fact that it could easily do so. Ironically, current Office users would have even less reason to switch vendors if Microsoft supported ODF.



"Had the ITD focused on its specific user requirements, it would have had much stronger case. Instead, it allowed the issue to be hijacked by the rabid anti-Microsoft set, who were not shy about turning the directive into a drive to replace Microsoft at any cost, just to see if it could be done in an IT operation the size of Massachusetts’."


Unless Mr. Titch has any evidence at all to back up such a claim, it can be safely dismissed as more pure fiction. Mr. Titch is obviously not a researcher, but a paid creative writer. Unfortunately, his fiction isn't really all that creative and relies solely on whether one trusts his ability to conduct research. Since Mr. Titch's research has been sorely lacking throughout this debate, one wonders why he bothers with the "senior research fellow" label at all. "Novelist" is much more suitable to his efforts here. His credibility is critical, since he claims to be a researcher from an "independent" spintan..., um, I mean, thinktank.



"This scared lawmakers. Pulling the plug on Microsoft would cost the state millions in the short term for future benefits that were, at best, vague."


Still lacking evidence to refute my previous demonstration of the cost savings that Massachusetts has to look forward to from migrating to ODF-compliant applications, he goes way out on a limb to try to show how everyone revolted at the thought of ODF. Still, once the smoke cleared, guess what? ODF is now an officially sanctioned format in Massachusetts. After review by the ITD, the lawmakers, and others, ODF remains an open standard usable in the Commonwealth of Massachusetts. The lawmakers could surely have overturned the decision. But they did not. Naturally, Titch passes over that.



"Microsoft has said the ITD policy is anti-competitive because the rule, in essence singles it out alone."


Critics have rightfully dismissed this as whining because Microsoft nor anyone else has proven that the rule singles out anyone. Microsoft was asked to support the same standard that every other vendor - competitor or not - is being asked to support. How does that single them out? Please, someone - anyone - show me some facts pointing to Microsoft being singled out. I'll be happy to weigh your evidence. But no one shows any because there isn't any to show.



"Although ECMA has existed since 1961 and has developed a number a communications, computer language and media standards that have been adopted by the International Standards Organization (ISO), it’s not good enough for some."


Titch goes on to quote a letter from a Sun executive encouraging the Commonwealth to only accept formally defined standards that are implementable by anyone as evidence that the open standards debate is really not about open standards. Ironically, the very quote highlights the importance of open standards. It is interesting that Microsoft has never supported such a standard in the way that Sun does here. Cargill's letter actually argued that Massachusetts should wait until Microsoft's competing format has been formally standardized, as opposed to eagerly accepting empty promises - something for which Microsoft has a well-established reputation.



"Andy Updegrove, a more level-headed open source advocate, in blogging on Open XML, pretty much admits that, open standards or not, the goal of the Massachusetts ODF effort isn’t about choosing what’s best for the state as it is about enforcing a pocket industrial policy."


Titch has a right to raise questions about Updegrove's assessment, but fails to offer any refuting evidence. He never states how Microsoft's XML format will foster competition. Does this mean Titch doesn't know? I have yet to see any evidence that the developers of Abiword, a GPL'ed word processor available for a number of operating systems, will be able to implement the Microsoft XML schema without violating the terms of their own license. Nor is there any indication that Abiword users running a GNU/Linux desktop system will be able to properly render a document created in Microsoft Office on Windows. Yet, this very issue raises questions about the openness of Microsoft's XML schema and license.



"The Massachusetts directive is a bad idea because it intentionally stacks the deck principally on the basis of market share."


Again, Mr. Titch fails to support his argument. There is no evidence in his article to support his thesis that the deck is being stacked against Microsoft. This very claim, as I have demonstrated repeatedly, flies in face of the facts. They were asked to support a standard - the same standard that every other vendor seeking to do business in Massachusetts will have to support. Titch continues to ignore Microsoft's refusal to support OpenDocument. He mentioned it, but never addressed why they refused. He never addressed how Microsoft would be hurt by implementing OpenDocument. In short, he continues to swing at high balls while ignoring the real questions at hand.



"They can make it a discussion about the merits of ODF... or they can continue their wild-eyed crusade against Microsoft."


Say, wasn't it Titch that pitched this debate in terms of Microsoft vs OpenOffice.org? I wish that, just once, Titch would address the merits of ODF. Even though I have done exactly that in at least three articles now, Titch has yet to address a single fact regarding ODF itself. He has yet to argue, let alone demonstrate, that Microsoft's XML format is somehow superior to ODF, or that ODF should be rejected. Instead, he stays in the peripheral of propaganda, an area that has little at all to do with facts or the merits of ODF.



Titch never did say how ITD's decision amounts to a procurement policy. He never refuted in any factual way my previous contention that there was no procurement policy, but a policy of standards. He claimed, but offered no proof, that ditching Microsoft Office would cost taxpayers big bucks. Titch never once offered any information to counter my claim that OpenOffice.org commands a much larger market share than he initially claimed. Titch never refuted my claim that some developers or vendors might be excluded from competing on Microsoft's XML format, due to the licensing issues.

  Nav
» Read more about: Story Type: Editorial, LXer Features; Groups: Community, Microsoft

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (16)

moron

his arguments are so childlike I think he is retarded. I am surprised you and me even waste the time responding.

I would like to see his stock portfolio and see any activity around the time he posts this nonsense.

all he needs to do is address why microsoft does not want to support it. but he knows the answer and that is why he will never answer that question.
I find it amusing that he is a 'researcher' and a 'senior fellow' yet he cannot walk the walk and only talks the talk. This fact alone...that he refuses to address FACTS that are WELL KNOWN...makes him naive and worse yet...stupid because he has to know that he's being naive.

Mr. Titch, if you read this...be a man, not a mouse. Quit hiding behind nonsupported statements...Come out with Supporting FACTS instead of nonsensical blabber. You argue so poorly that a high school debate team member could trounce you in sub 20 seconds. The only course of action to a highly touted 'senior fellow' such as yourself would be to save face...remember, you're only a researcher and there is no possible way that you would be able to know everything. Apolgize and move on. Or don't and look like an ass.
I think he's already chosen the latter, dev.
I would seriously hate for him to engage in a debate here. He would be waxed in the first response. Frankly, I just hope he sold his credibility at a high price.

two nits

dcparris,

Two nits to pick.

The first is yours. Microsoft Office is also available for Mac OSX. Microsoft always threatens Apple with end of life on the product to keep them on their toes, but it is available. MS has not committed to a version that will handle Open XML for the Mac, but they have not completely ruled it out either.

The second is with Mr. Titch. You point out many flaws in his arguments, but he also refers to Andy Updegrove as a '...a more level-headed open source advocate...'. I don't believe I have ever read Mr. Updegrove advocating Open Source over proprietary. He seems pretty neutral, and accepts both as facts of life in IT. Andy Updegrove is a strong advocate of well documented publicly developed standards.

Thanks for the well written rebuttal.
Thanks for the feedback. I just recently read where MS was pulling Office off the Mac, or something to that effect. And I agree with you on his picking on Updegrove. That was pure stupidity on Titch's part.
Just another innaccuracy or a try to undermine Mr. Updgrove's reputation with MS Fancois?

With Titch it could be anything.

Microsoft used to deliver new features to Mac users before they came to the Windows version of Office, but Office has been available in a pure gui form to mac users for a few years before Windows was stable.

Currently MS Office for Mac feature Entourage, the planned replacement for the much maligned outlook client: http://www.microsoft.com/mac/products/entourage2004/entourag...

I don't have a mac any longer, but OSX is sweet. I may pic up a mac mini to play with someday.
//Microsoft Office is also available for Mac OSX.//

Yes, but even on Mac OSX it still depends on proprietary, secret MS technology. ActiveX is one example, OLE is another.

Given that all MS Office formats (the current formats and the new Open XML formats as well) depend on secret proprietary OS technology from one vendor alone (Microsoft), then the formats are not future-proof. There is no guarantee that in the future anyone will be able to write software that can decipher the formats.

With ODF, being a fully documented, open and unencumbered format, there is that guarantee. Even if every single one of the ODF-compliant applications and platforms on which they now run is not available in (say) twenty years time, it would still be possible given the ODF specifications to write a new application which would be able to read a document saved today in ODF format.

You cannot say the same about any one of Microsoft's formats.

Therefore, none of Microsoft's formats meets Mass. requirements.
Microsoft Office for the Mac is not completely compatible with Microsoft Office for Windows. I have a letterhead document with embedded logo in .wmf. Works fine in Word for Windows (and OpenOffice.org on WIndows, Linux and Macintosh and NeoOffice for Macintosh), but the logo just gets unusably scrambled in Office for the Mac. Ouch!

My Comment to Mr. Titch -

Hey Rev --

As I said last time, all Titch cares about is creating the message that the ODF standards will cost Massachusetts money without any benefit in return. All of the tech talk is simply a way to create the basis for saying there are two points of view and reasonable people can differ, so why throw the state into expensive chaos.

The only response that really matters is that ODF will create opportunity for Massachusetts' people and for its business. It is a hammer that must be used over and over and over, just as Mr. Titch uses his hammer. This is PR, not debate.

For your edification, the comment I posted to Mr. Titch:

Well, Mr. Titch, I see your crusade against the people and businesses of Massachusetts continues.

You campaign for a company on the other side of the country while brushing aside the opportunities that ODF will create for a Massachusetts tech economy that hasn't been too healthy in recent years. You quote Updegrove as a way to discount the fact that ODF's clear and open standards open the door for programmers (and the businesses that employ them) to do things with documents.

Mr. Titch, that ability is called opportunity. In case you haven't noticed, Massachusetts is home to both the Harvard Business School and MIT, not to mention many other fine colleges and universities. It is utterly inconceivable that Massachusetts will not benefit from a move to ODF, unless, of course, you think Massachusetts students, business, and engineers are somehow substandard. And let's not forget -- ODF is an ISO standard, which means local companies that get a kick-start from the state requirement will have a head-start on the world business stage.

As to Microsoft -- If they are true to their word, they will be part of the party! If their OpenXML standard really and truly is open -- which has yet to be determined -- they will have no problem whatsoever. You see, from the beginning, the xml data format was designed to be transformed. It even has it's own transformation language, xsl, based on transformation stylesheets. A truly open OpenXml, one without hidden trapdoors, one that is not merely an open container for secret binary formats, will be easily transformed to and from ODF.

If Microsoft doesn't want to do it, the state can contract with a local company and get the job done -- maybe launching a few local students into the next tech startup to make it big.

Frankly, Microsoft's biggest problem with ODF will be that ODF permits people other than Microsoft to introduce The Next Great Thing. That means money going to Red Sox fans that could have gone to rooting for the Mariners.
grouch Story submitter ·
dinotrac:

Excellent!

Cynical ol' me thinks maybe the reason MS has recently decided to give away a bunch of MS software in MA schools and universities is to attempt to counter the effects of part of MA's government using an open standard document format.
grouch:

Cynical ol' you is right on the money -- and money is the operative factor here.

The whole debate is secondary. Titch is repeating (and repeating) a one-note message: this thing gonna cost you money and mess things up.

He can dismiss the entire debate with a "Clearly reasonable minds can differ on this issue. I don't pretend to have all the answers."

Which leads to the inevitable, "If so much is uncertain, should we be taking such a radical and risky step?"

binary data tags in Open XML

I would like to see the proof of the binary data tags. Brian Jones in his blog (http://blogs.msdn.com/brian_jones/archive/2005/10/17/481983....) refuted every theory about the binary data tag he could find, as well as most other complaints commonly given about Open XML (in entries spread over several months), if you take everything he says at face value. I am an ODF advocate, but after reading his blog it is hard for me to know how to argue with Microsoft die-hards.
grouch Story submitter ·
That blog talks about a mythical "binary key that you need to unlock the Microsoft Office XML formats". That is NOT the same as the tag in the schema that allows inclusion of binary blobs of MS Word and MS Excel data.

See, for example, http://www.groklaw.net/article.php?story=20051020193905892&m...

"Microsoft’s disclosure of the WordprocessingML and SpreadsheetML schema is inadequate for interoperability because it omits critical information necessary for full interoperability. While these schema may or may not be complete, there is a fundamental limitation in that some of the items stored in the fields of the schema are Microsoft-proprietary data, and Microsoft has not disclosed the information necessary for others to interpret and use those data."

I suggest you also read David A. Wheeler's analysis of Microsoft's letter to Massachusetts, also at Groklaw: http://www.groklaw.net/article.php?story=20051029212458555&m...

Note particularly the section titled "Open":

"The difference now is that patents are involved. Microsoft has patented some aspects of its new XML format; if these patents are truly valid, the law makes it illegal to use Microsoft’s XML format except under the terms Microsoft has created."

It's very easy for me to argue with "Microsoft die-hards"; the facts of the matter are sufficient.
Nothing 'open' about MS XML unless they disclose and GPL the whole thing.
grouch Story submitter ·
Andy Updegrove pointed out some other problems with MS XML in his blog entry, "First Public Draft of Open XML is Published by Ecma" -- http://www.consortiuminfo.org/standardsblog/article.php?stor...

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post