For most of us, file formats are right up there with printer drivers in terms of fun. Certainly, they're important, but not something you'd look to for excitement. And yet that is precisely what the battle between the OpenDocument Format and Microsoft's OOXML is providing. And I'm not just talking about the dry, intellectual excitement derived from comparing well-formed XML tags: this is a no holds barred, down-and-dirty mano a mano fight over the soul of document standards.
Some of this stuff is downright hilarious. For example, in Portugal neither Sun nor IBM was able to take part in a crucial national meeting to vote on whether OOXML should become an ISO standard; the reason?
The excuse for not letting them in, according to the notes, was that the room only could hold 20 people, and it was first come, first served. But when this was said, there were already more than 20 in the room. It eventually reached 25, so it seems clear there was room for Sun and IBM. There was an auditorium available they chose not to use.
Or try this one:
Previous reports from all over have indicated sudden, surprising surges of membership in National Body voting committees in multiple countries throughout the world (most recently in Sweden), and I have reported recently (here and here) that there has been a sudden surge of interest among ISO members in upgrading their privileges to "P" status, which will entitle to them (just in time) to a more influential vote on OOXML
When I first noted that I had heard concerns over upgrading at the global vote level,. only two nations had upgraded. When I wrote about it the second time, that number had risen to six. It's now only a few days later, and the number has risen to nine (bear in mind that the original number was only thirty). And there are still a few days left during which stealth countries, their votes already taken, can make the cut. Where will it all end? [Updated 8/29: The number is now forty - the most recent addition is Malta.]
None of this will surprise long-term observers of Microsoft: it's simply the way it plays. But irrespective of what you think of the morality of this kind of behaviour, there are number of interesting implications.
The first is that many more people are aware of the importance of file formats being open - something that few cared about a year ago. Microsoft has been unable to counter the line that openness here is good, and so has been forced to take the position that its own 6000-page file format is also open. This shows that Microsoft is having problems countering the openness meme, and has even been forced to play along. Although there is the danger that by doing so it will dilute the value of openness, it is clear from this that openness as a strategy is hard to beat.
The second point is that Microsoft's apparent willingness to use all and every means to get OOXML adopted as an ISO standard conveniently proves that there is no real grassroots desire for this. If there were, it wouldn't need to expend so much time and money on such methods.
These recent moves confirm that those boring old file formats really are interesting, at least in the case of documents (and probably elsewhere). There are various reasons for this, all of them bad news for Microsoft. One, obviously, is the continuing rise of ODF as a viable alternative. Another is the relative indifference of users to OOXML: Microsoft really needs its format to be recognised as an official ISO standard in order to provide Office users with an incentive to upgrade.
Finally - and perhaps most importantly - the sudden interest in file formats is an indication that cloud computing is beginning to make its presence felt. There can be no lock-in to particular desktop programs here, because there are no desktop programs (other than the browser, and fortunately Firefox has pretty much won the fight to keep Web standards open). Ultimately, file formats are not just important, they are the only thing that counts.
Glyn Moody writes about openness at opendotdotdot.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Keeping track of IP address
45 min 15 sec ago
- Roll your own dynamic dns
5 hours 58 min ago
- Please correct the URL for Salt Stack's web site
9 hours 10 min ago
- Android is Linux -- why no better inter-operation
11 hours 25 min ago
- Connecting Android device to desktop Linux via USB
11 hours 53 min ago
- Find new cell phone and tablet pc
12 hours 52 min ago
14 hours 20 min ago
- Automatically updating Guest Additions
15 hours 29 min ago
- I like your topic on android
16 hours 15 min ago
- This is the easiest tutorial
22 hours 51 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?