Going to OOXML great lengths

Going to OOXML great lengths

Summary: SOMEWHERE IN THE PACIFIC--The LCD monitor inside the Northwest Airlines flight that I'm taking says we're 36,000 feet above this vast ocean. I'm on my way back to the Philippines after taking a side trip to San Francisco from a press coverage in Washington, United States.

SHARE:
TOPICS: Microsoft
1

SOMEWHERE IN THE PACIFIC--The LCD monitor inside the Northwest Airlines flight that I'm taking says we're 36,000 feet above this vast ocean. I'm on my way back to the Philippines after taking a side trip to San Francisco from a press coverage in Washington, United States.

My itinerary says it will take our aircraft about 11 hours to reach Japan's Narita airport, from San Francisco. After a three-hour layover, another four-hour trip will finally bring me to Manila.

A few days back, a fellow journalist from the Philippines and I took a slightly different route going to the United States. We landed directly at the Seattle-Tacoma airport to attend a press briefing by software giant Microsoft, in the nearby cities of Kirkland and Redmond.

Why am I telling you this? Well, I'd like to think that Microsoft is going out of its way to reach out to technology journalists from the far corners of the world, to argue its case in what has become a very contentious issue in the IT industry.

The case at bar is Microsoft's promotion, on behalf of its partners supporting it, of a document format called Office Open XML (OOXML). I'll try to explain the significance of this thing in the way I understood it.

Right now, if you create a document, say, in Microsoft Word and save it as a Word document, there's no way for you to open that file--and retain the document's original formats--except using Microsoft Word, which is part of Microsoft Office suite. It is encrypted in such a way that if you try to open it usingNotepad, for example, you'll get a garbled and useless heap of characters.

With OOXML, one can use Notepad or just about any productivity software like Microsoft's rival OpenOffice, to open a file that's saved in Microsoft Word document. OOXML, Microsoft says, is backward-compatible and future-proof...meaning, it can open all previous and future versions of Microsoft document formats.

Microsoft developed the OOXML format and submitted it to ECMA, the European ICT standards body, which then approved it.

But to make it truly a global standard, the format was sent for approval by the ISO and IEC (International Organization for Standardization and International Electrotechnical Commission). This is where the process hit a snag, with the OOXML failing to get the required number of votes to be ISO-certified.

The Philippines is one of the countries that voted "no", which partly explains why we were invited to attend the press briefing.

The main argument against OOXML is that there's already an existing document format called ODF (Open Document Format), which is primarily pushed by open source supporters such as IBM and Sun Microsystems, and adopted by governments including Malaysia and Japan.

Microsoft countered, however, that the ODF does not guarantee future support for documents made in Microsoft format. This, the company says, isn't quite fair since the bulk of documents today are created on Microsoft Office format.

Besides, there shouldn't only be one document format, says Microsoft. In the technology world alone, multiple standards exist or have existed...JPEG and TIF, VHS and Betamax, HD-DVD and Blu-ray, and so on.

What ought to be done, the software vendor stresses, is to let the market decide which format is better in addressing the needs of the consumers. The operative words that Microsoft uses to define OOXML are "choice" and "interoperability"--traits that cannot be said of the ODF, the software giant points out.

In that press briefing in Kirkland, I have never seen Microsoft so passionate about collaborative work--quite different from the industry behemoth that is so used in having its way.

I mentioned earlier that Microsoft lost the initial round of balloting at the ISO/IEC level. However, there's still a final round voting to be carried out in February, that will ultimately decide its fate.

Although Microsoft is trying hard to have the ISO/IEC ratify the format, the company says an adverse ruling on the issue will not change its position to use and push it as the de facto standard since most documents are already in OOXML format, through Microsoft Office, anyway.

Well, it seems that this thing is still far from over. It would be interesting to see how this issue will unravel come February.

Just a last word on this...

While I admire the work done by the open source community in influencing Microsoft to take this collaborative approach, I believe the latter has also made a good stand in advocating the need to allow the industry to choose the format that they deem best for their needs.

Topic: Microsoft

Melvin G. Calimag

About Melvin G. Calimag

Melvin G. Calimag is currently the executive editor of an IT news website in the Philippines. Melvin has been covering the local IT beat for the last 13 years. He is currently a board member at the IT Journalists Association of the Philippines (CyberPress), and also serves as a charter member with the Philippine Science Journalists Association.

Joel D. Pinaroc

About Joel D. Pinaroc

Joel has been a media practitioner since 1996, starting off as a reporter and eventually becoming editor of a pioneering IT trade newspaper in Manila. He is currently one of the content producers of a Manila-based developmental website.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

1 comment
Log in or register to join the discussion
  • There are two other differences between ODF and MSOOXML, aside from "ODF is already an ISO standard":
    1) ODF was developed by the community, and as a result has a lot of user input. MSOOXML was developed by Microsoft, and has no input from any potential users.
    2) ODF is truly open in its standards, and the standards are not controlled by one corporation. In order to use MSOOXML, you need proprietary protocols, and the standard is controlled by Microsoft, who can change the standard at its whim.
    3) Right now, there are at least 30 different programs out there that use ODF, with more on the way. They are usable across platforms, including OS X and Linux. The only application that even tries to use MSOOXML is MSOffice 2007, currently only available for Microsoft Windows.
    anonymous