Group items tagged

This is amazing stuff. With all the talk about OpenOffice ODF compatibility problems with existing MSOffice productivity environments and documents, this comparison is stunning. I stumbled across this Compatibility Comparison reading this article: ThinkFree Set to Launch The First Complete Android Office Suite. Documents To Go is currently the only provider of Word and Excel documents on Android. The ThinkFree Office comparisons to OpenOffice cover a number of familiar compatibility issues, with layout at the top of the list. ThinkFree Write 3.5 vs OpenOffice Writer 3.0 ".....When using a word processor to create documents, you really shouldn't have to worry about whether your client will be able to see the document as you intended." ".... However, if you use a low-cost solution like OpenOffice, you should be prepared for frustrations and disappointments....."

Interoperability through antitrust - is there a legal foundation in place capable of pulling this off?  This article is a lengthy study and comparative analysis of the legal foundation in the USA and Europe.  Microsoft is of course the target. Excerpt: Microsoft has incorporated products, such as browsers and media players, into its operating system, behavior that again amounts to technological tying. It has also improved its server software by heightening the degree to which servers employing that software can interact. By raising the level of interaction among servers equipped with its software, Microsoft has so integrated work group servers as to enable groups of small servers to approach the capacities of mainframe computers. The European competition-law authorities see both matters as problematic. The integration of the media player has been condemned as tying; and the heightened server interaction has been faulted for failing to provide the interoperability that rival server software requires in order to participate on an equal footing with Microsoft server software in Windows work groups. Microsoft’s integration (at least in the view of the European antitrust authorities) also raises issues of essential facilities, and of the role of antitrust in achieving interoperability. . We have now reached a moment in time in which both the American and European laws are sufficiently developed to warrant reflection and comparison. That is the task approached in this article.  Three part study:  Part I -The European approach.  Part II-USA decisions regarding Microsoft tying.  Part III-comparison of USA and European approaches to product integration (tying).

"Microsoft has attacked the UK government's decision to adopt ODF as its standard document format, saying it is "unclear" how UK citizens will benefit. The Cabinet Office announced its new policy yesterday, whereby Open Document Format (ODF) is immediately established as the standard for sharing documents across the public sector, with PDF and HTML also acceptable when viewing documents. SERGIGN - FOTOLIA The decision was a rejection of Microsoft's preference for Open XML (OOXML), the standard used by its Word software, which remains the dominant wordprocessor in government. "Microsoft notes the government's decision to restrict its support of the file formats it uses for sharing and collaboration to just ODF and HTML," said a spokesman for the software giant in a statement to Computer Weekly. "Microsoft believes it is unproven and unclear how UK citizens will benefit from the government's decision. We actively support a broad range of open standards, which is why, like Adobe has with the PDF file format, we now collaborate with many contributors to maintain the Open XML file format through independent and international standards bodies," it added"

There are the technical arguments for ODf vs. EooXML.  Then there are endless discussions concerning the discovery and disclosure of volumes of contradictions between ODF and EooXmL  And how about all those legal-patent-licensing-DRM restrictions on EooXML which shatter in comparison to the truly open and un encumbered ODF.  Even the comparison between ECMA the great rubber stamp standards for sale org vs OASIS, the everyman's consensus community standards mill where ODF flourishes.  All interesting.  but this blog is about the reality of migrating information and information processes to ODF.  It's not easy!

There are the technical arguments for ODf vs. EooXML. Then there are endless discussions concerning the discovery and disclosure of volumes of contradictions between ODF and EooXmL And how about all those legal-patent-licensing-DRM restrictions on EooXM

There are the technical arguments for ODf vs. EooXML. Then there are endless discussions concerning the discovery and disclosure of volumes of contradictions between ODF and EooXmL And how about all those legal-patent-licensing-DRM restrictions on EooXM

Marbux nails it again in the comments section of this obscure review. In particular, he sites Shah, Rajiv C. and Kesan, Jay P., Lost in Translation: Interoperability Issues for Open Standards - ODF and OOXML as Examples (September 2008), Link to paper on SSRN (compatibility fidelity comparisons of ODF implementations testing only a very small set of word processing features). "...Switching documents, I go through similar travails with the published ODF 1.1 specification, using both the PDF and ODT versions. Bottom line: I can't get either document into WordPerfect X3 or X4 using any rich text format. So I convert the document to plain text using Symphony and get my work done. That is the real state of ODF interoperability. There is no such thing. But that does not stop the vested interests from claiming that there is. E.g.:"

"Over the past week, I've been blowing the virtual dust off more than a decade's worth of annual reports from Microsoft, Apple, and Google. My goal was to follow the money and figure out how each company's business has changed over the past decade. Consider this a follow-up to my February post, "Apple, Google, Microsoft: Where does the money come from?" My tally starts with financial results for 2002, the year after Microsoft signed a historic consent decree that settled the U.S. v. Microsoft antitrust lawsuit. It was also the first full year after the introduction of the iPod, which was the first step on Apple's transformation from a PC company to one that revolutionized mobile computing and communication. The earliest annual report I could find for Google was from 2003, the year before its big IPO. In Microsoft's case, the question I was most interested in was "How dependent is the company on Windows?" The Windows monopoly began crumbling as soon as the settlement was signed (although it's debatable how much influence that lawsuit had on the market). Over the past 10 years, Microsoft has shifted its reporting structures a few times, making it hard to draw perfect comparisons over time. But the chart below, which shows revenue from the desktop versions of Windows and related products, is close enough."

Want to know the real reason why IBM and Microsoft are going at it hammer and tong over document formats?  Here it is.  Lotus Notes is getting clobbered by the Exchange/SharePoint juggernaut. 

The article is old, but the point is well taken.  Today the Exchange/SharePoint juggernaut i sover 65% marketshare.  IBM is struggling to protect the Lotus Stack against an impossible foe.

The thing is, Microsoft E/S will ALWAYS have better integration with the MSOffice - Outlook desktop monopoly base (550 M and counting).  Most of this "integration" is due to the high fidelity exchange of documents in Microsoft's proprietary XML mode known as MS-OOXML.   Forget the charade that MS-OOXML is an open standard called Ecma 376.  MSOffice and infamous XML Compatibility Pack Plug-in do not implement Ecma 376.  The Pack implements MS-OOXML.

One key differnece between MS-OOXML and Ecma 376 us that MS-OOXML is infused with the Smart Tags components.  These are for metadata, data binding, data extraction, workflow, intelligent routing and on demand re purposing of docuemnt components.  In effect, MS-OOXML :: Smart Tags combines with proprietary .NET Libraries, XAML and soon enough Silverlight to replace the entire span of W3C Open Internet Technologies. 

Can you say "HTML"?

Okay, so why does this matter to IBM and the future of Lotus Notes?

The end game of the document format wars is that of a stack model that converges desktop, server, devices and web information systems.  The MS Stack uses MS-OOXML as the primary transport of accelerated content/data/multi media streams running across the MS Stack of desktop, server, device and web application systems.  It's the one point of extreme interoperability.

It's also a barrier that no non MS applicatio or service can penetrate or interoperate with except on terms Microsoft dictates.