More on the OpenXML discussion: the CompTIA view on future-proofing IT and standards
Just after my blog post I met the NZOSS President Don Christie during a event here in Wellington, and he told me I was in the wrong side of the fence on this one. But we agreed that we have to find a side and stick with it anyway...
Since then Standards New Zealand decided to cast NO to the OpenXML standard, but Standards New Zealand has created an advisory group to meet for five days in Geneva to discuss concerns raised during the voting. The participants in this group are Internet NZ, NZ Open Source Society (technical), NZ Open Source Society (strategist), IBM NZ, Microsoft NZ, Microsoft NZ partner, Archives New Zealand, State Services Commission and the NZ Computer Society.
Now I have received a copy of a document written by CompTIA's Michael Mudd, and I am reproducing the document here because it pretty much reflects my way of thinking on this matter.
The CompTIA is a global trade association representing the business interests of the information technology industry. For more than 25 years CompTIA has provided research, networking and partnering opportunities to its 20,000 plus members in 102 countries. The association is involved in developing standards and best practices, and influencing the political, economic and educational arenas that impact IT worldwide.
Future-proofing IT Policy – is it possible, or desirable?
By Michael Mudd
I imagine you’re enjoying this article on your Kenbak-2000 personal computer, or secretly wishing you were the richest man in the world, John Blankenbaker. This easily could have been the case if in 1971 the Kenbak-1, subsequently considered by the Computer History Museum as the world’s first ‘personal computer (PC),’ had been recognized as the sole standard for the future development of the PC.
Think; no 1977 Trinity (Apple II, TRS-80, and Commodore PET) or IBM 5150 in 1981, which arguably set the scene for the entire PC era, making household names of previously niche players such as Intel and Microsoft. Thankfully, while certain patents were awarded to the Kenbak-1, we can thank IT industry policy-makers of the time for seeing how much more innovation and invention was left in the PC industry. Even more importantly the market needed more time to reward the companies who were delivering systems that could best meet their needs. This ability to create an environment where innovation flourished, while intellectual property was still credited and protected means that today nearly two billion PCs have been sold, versus the 40 Kenbak-1 PCs that made it off the production line.
The ability to allow continuous market-driven innovation, rather than creating standards and policies based on an early view of what the world of tomorrow might look like is central to business success – it means that you’re not deciphering this article from Morse code, or driving to work in a Model-T Ford.
Why is Innovation Important - Open Innovation versus Closed Innovation
The advent of the Internet has fundamentally changed the way the businesses define business models and harness innovation. Henry Chesbrough in his book “Open Innovation, the New Imperative for Creating Profit from Technology” refers to the time before and after the Internet, as ‘Closed Innovation’ and ‘Open Innovation,’ respectively.
Before the wide adoption of the Internet, innovation used to be a closed process, undertaken with a silo-mentality. Business leaders used to think that to profit from research and development that, like John Blankenbaker, they had to be first to market. They would have to directly hire people to make discoveries, develop and market the discoveries themselves and then use tools such as patents to control this intellectual property so that competitors could not share in the spoils.
Chesbrough notes that today’s Internet-powered competitive business landscape makes closed innovation increasing hard to achieve. Incredibly fluid employee availability and mobility, the proliferation of small market-driven technology businesses (e.g. today small businesses accounted for over 99 per cent of all businesses), outsourcing, off shoring and the proliferation of new market-driven sources of innovation means that with great product choice and faster innovation cycles that customers increasingly want product interoperability, rather than a rigid, pre-defined single-standard.
Document Standards – Why Should Businesses Care?
There is an interoperability versus single-standard debate raging at the moment, which has a direct impact on business – should the Open Document Format (ODF) be the sole standard for business documents, or should Office Open XML (OOXML) also be allowed a choice for businesses and document users?
Data formats have been around as long as computing. They reflect the varying capabilities and functions of different computing systems and have evolved as those computing systems have evolved. Punch cards were once commonplace, but you wouldn’t think to use them today. In the decades since their use, a wide range of formats (TXT, PDF, HTML, and DOC, to name a few) have become popular because they meet specific user needs and tap into new computing capabilities.
Two years ago Microsoft submitted Office Open XML to Ecma International, an international association founded in 1961 and dedicated to the standardization of information, to go through the process to make it an open standard. A growing list of companies, including Microsoft, Apple, Novell, Xandros, Linspire, TurboLinux, Corel and Dataviz recognized the desire of users of their software to work with multiple formats and are giving those users the tools they need to do so. However, despite industry belief that customers would be happy to choose, there is a chance in March next year that some national body members of the ISO may not approve OOXML as a document standard. In a preliminary vote last September, 51 national bodes voted yes, but under the consensus system of the ISO this was insufficient.
We should expect the creation of new formats in the future as technology evolves (e.g. Uniform Office Format, or UOF, under development in China, also a group of former ODF supporters have broken away from the ODF standard and are now promoting another document format standard called CDF), and as has always been the case, users should be able to choose the formats that work best for them, especially if they are fundamentally different formats that meet different needs in the marketplace, as is the case here.
OOXML sceptics argue that OOXML contains Microsoft-specific legacy formats which can cause interoperability problems, and will serve only to strengthen Microsoft's domination in the office productivity software market. OOXML is already being used in the 2007 Microsoft Office system, making it easier for people to use the software suite that creates the vast majority of the world’s business document to create and share documents, regardless of the platform or application.
Customers who want to work with multiple formats can do so now and into the future through the use of tools called ‘connectors.’ However, the simple fact is that OOXML should be agreed as an interoperable standard along with ODF (and whatever other standards meet the criteria) to allow the market to choose which one they will use to achieve what they need with their business documents.
Standards and policy – when the market decides, we all win!
Suppose Charles H. Duell, Director of the U.S. Patent Office had shut it down following his 1899 proclamation that ‘everything that can be invented, has been invented.” When people take a narrow view of what is achievable through technology, innovation is the inevitable collateral damage – especially dangerous at a time when the governments of Asia are looking to ICT as a major value-add to economic outputs and creating jobs.
I recently attended a meeting in Malaysia where there was a clear statement from the Honourable Dato Dr. Jamaludin Jarjis, Malaysia’s Minister of Schience, Technology and Innovation, that the country should adopt an open innovation model and that this should be market driven. CompTIA supports industry standards and strongly believes that standards such as OOXML are good for any countries in the region that want to pursue Open Innovation approaches. I’m not necessarily saying that the market would choose to use OOXML, but the market needs the opportunity to decide, otherwise we could be building an environment that stifles, rather than encourages innovation.
If Mr. Duell had done that in 1899, I might still be wearing a fashionable Victorian knee length frock coat and a top hat.
Michael Mudd, Director of Public Policy, Asia-Pacific, CompTIA.
Mike Mudd is the Director of Public Policy for Asia Pacific and has responsibility for running CompTIA’s Public Policy initiatives for the region encompassing Japan to Australia and China and India. This region, home to half the worlds population is also amongst the most dynamic and challenging for the ICT industry in the 21st century.
I agree with its basis that a standard doesn't need to be a single unique entity, but it can be multiple agreed codes.
For full disclosure I must inform you that I found this document with the help of Microsoft New Zealand. Of course if the NZOSS or any other commenter wants to send me something similar I am happy to write about it too. Or just comment below.
Other related posts:
Some New Zealand companies don't like user feedback
What is wrong with TiVo in New Zealand?
What mobile device to get?
Comment by foobar, on 22-DEC-2007 13:42
Before I forget it: It's almost amusing to see that some people would claim that OOXML is about 'choice for users'. Nothing could be further from the truth. We know why it was created: So that Microsoft could stay in accounts which now demand documents to be stored in open standard formats. Before that demand came up, Microsoft wasn't interested in publishing their doc-format as a standard. Now they had to do something, though. So they write up something that is too complex and relies on patented Microsoft technology to be implemented properly, and have the audacity to claim that this should be an open standard?
It's all about keeping accounts with Microsoft technology, and therefore furthering the vendor lock-in that the users there have.
OOXML is just another building block in Microsoft's strategy to limit (!) the choice of users and prolong lock-in. The complete opposite of technical progress and user choice.
Comment by Frank Daley, on 22-DEC-2007 14:07
The flaws of OOXML have been widely documented, but perhaps even more importantly is the fact that Microsoft is using OOXML as part of its embrace, extend, exterminate strategy.
How does this work? Simple.
A future version of Microsoft Office will be able to read and write OOXML (although no current version of Microsoft Office can do this!). However the default save from future versions of Microsoft Office will be OOXML + proprietary extensions. Therefore, while potentially competitive programs will be able to read and write OOXML format files, they still won't be able to read or write Microsoft's default proprietary extended OOXML file format. So what if Corel Office or Novell Office can read and write OOXML, they will still effectively be locked out of the bulk of the Office market since they won't be able to read or write the files that are created by most users.
Hence OOXML is a smoke screen effort by Microsoft to pretend it is interested in standards when in fact it is a mere facade attempting to hide its true intentions.
Comment by Nigel Parker, on 22-DEC-2007 14:55
foobar wrote... "it can only be implemented by Microsoft."
I think you meant to say... "it can only be implemented by people that choose to implement it."
Linux/Java interoperability with Open XML - http://channel9.msdn.com/ShowPost.aspx?PostID=292752
OpenXML4J - Open XML library for Java - http://sourceforge.net/projects/openxml4j/
On another note how was the Python user group in Mt Eden last week?
Have you checked out http://pythonnet.sourceforge.net ?
If you are looking for a new crusade you could try HDMI http://en.wikipedia.org/wiki/HDMI .
Did you know that Vista is the only OS that supports HDMI today!?
Hitachi, Matsushita Electric Industrial (Panasonic/National/Quasar), Philips, Sony, Thomson (RCA), Toshiba, Silicon Image, Fox, Universal, Warner Bros, and Disney might need a bit of blog lovin from you in the new year :)
Comment by foobar, on 22-DEC-2007 19:27
@Nigel: No, I meant to say exactly what I said. You cannot implement the OOXML standard fully, without having to use Microsoft proprietary stuff. Take a look here, for a short list:
http://en.wikipedia.org/wiki/Ooxml#Criticism
And here are some statements from Google about it:
http://www.odfalliance.org/resources/Google%20XML%20Q%20%20A%20(2).pdf
To quote: The continued use of binary code tied to platform-specific features;
So, you can implement it only if you license stuff from Microsoft.
Also, there are a lot of inconsistencies in the so-called 'standard'. Unless you are Microsoft and magically 'known' what you meant when you wrote it, you cannot implement it 'correctly', because of those inconsistencies and contradiction. Any attempt to do so is 'best effort', at the most.
HDMI is for the DRM-crippled transmission of video. Since no other OS cares about that DRM madness, no wonder that only a DRM-malware like Vista implements it.
I wasn't able to make it to the Python user group meeting, sadly...
Comment by foobar, on 22-DEC-2007 20:39
@freitasm: If Nigel and I were incorrect and Apple implements HDMI as well, then I must sincerely apologise and extend the bashing to Apple, too: BASH! There. Yes, iTunes is DRM malware as well. We all know that. In fact, didn't we have exactly that exchange over on my blog the other day? http://www.geekzone.co.nz/foobar/4265
Anyway, I already explained there why the bashing predominantly is directed against Microsoft: They use DRM as a way to lock customers in on the Microsoft platform, by providing the ubiquitous platform for which media companies will produce content. Apple is not (yet) an issue here, because it is used by a relatively small number of people (compared to Windows). Apple is in the content market much more so than Microsoft. That's their (very bad) excuse for the DRM in iTunes. Microsoft, however, doesn't have any excuses. Their tactic is geared towards vendor lock-in and prevention of open systems as valid competition in the desktop market. That's a whole different story than Apple's.
But I already tried to explained that in our exchange over on my blog.
How did we get on this subject? Wasn't this a post about OOXML?
Comment by Matthew Cruickshank, on 23-DEC-2007 09:04
I *wish* we were all going to meet in Geneva to talk about this. It would a convoluted way of going about this but I generally agree with your notion that there should be more jetsetting-playboy-types in the standards development process ;)
(To clarify, the BRM process involves sending delegates from the group. The entire group aren't going to the Geneva BRM.)
Freitasm, my personal view on OOXML is that it needs to be documented (the gaps need to be filled in - both for technical and legal coverage requirements of the OSP), that it shouldn't favour Microsoft Windows over Apple OSX and Linux, and that where it externally references (and indeed requires) undocumented file formats it should allow other popular standard formats too (eg, clipboard types should allow PNG, SVG, etc.). Legal coverage for these external formats would be appreciated too.
Maybe if we could talk about the technical quality of the standard (whether it does infact describe Office 2007s files) rather than this high-level values then this would be a better discussion, and we could reach some middle ground?
We're in the same town, but I guess we don't run the in the same circles. If you do happen to see me around town please do stop me and we can have a detailed chat about this stuff.
Cheers
Comment by Nigel Parker, on 23-DEC-2007 09:37
@foobar wrote "HDMI is for the DRM-crippled transmission of video. Since no other OS cares about that DRM madness, no wonder that only a DRM-malware like Vista implements it."
Really? I thought poor old Vista had to compete against proprietary set top box computers?
I read this comment on Russell Brown's forum...
"The thing to remember is that the MySky box is not owned by the consumer, which means Sky can push software updates into the market any time they like. This means (for instance) they can require all high definition content to pass through a HDMI connector which is fully copy-protected, and they can switch on the broadcast flags that would not allow you to record content, or would impose other limits.
Look at it from Sky's point of view; why should they allow you to record that All Blacks match and play it back any time you like, when they could charge you for the same thing via pay per view?
Having a personal PVR is a fine thing ... but having a corporate-controlled PVR may not bring the level of control everyone assumes."
And this http://computerworld.co.nz/news.nsf/tech/98797DBD856D488DCC25738A006947EA in computerworld...
"The HD boxes have a new operating system"... i wonder if this new OS is Linux?? My guess it is :)
Comment by Don Christie, on 3-JAN-2008 10:30
Hi Mauricio
Happy New Year.
My coherency may have been slightly impaired when we met. I am not sure that this is really a case of "taking sides". It is more about getting the standards process and resulting standards right.
Certainly Microsoft have accepted just about every criticism that has been made about the OOXML proposed ISO standard and appear to be in the process of a complete redraft. Surely this is an indication that those who bothered to review and critique the proposed standard were and are doing so with good reason.
Unfortunately the time to review the resulting draft is now ludicrously short.
I am confused by Mudd's points. They seem to be that standards are bad because they stifle innovation.
Done correctly, nothing could be further from the truth. Having good, well documented open standards have the opposite effect to stifling innovation. They allow software developers to build on platforms that already exist (e.g TCP/IP), to interoperate and to integrate. Nothing is developed in isolation these days.
The standards *process* allows for changes and innovation. The bodies that develop standards don't just give up and say "job done" once they get accreditation. They continue to capture enhancements, document and debate what is worthwhile and what is not. Generally this is an open and inclusive process which produced valuable results.
Add a comment
Please note: comments that are inappropriate or promotional in nature will be deleted.
E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.
Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments.
If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.

Comment by foobar, on 22-DEC-2007 13:32
It is sad to see by how much some people miss the point. Completely. Mr. Mudd's argumentation only showcases this in his case.
I don't know from where he would get the idea that OOXML critics are against new standards, or a choice of standards, or the progression of technology by artificially restricting us to one standard. This is absolutely not the issue here and flat out wrong. Why does he muddle the water with claims like this? His argumentation is not only wrong and useless, but also inflammatory to top it off.
At issue is solely the fact that OOXML is deeply and fundamentally flawed as a standard. In fact, it doesn't even deserve to be called 'standard', since it can only be implemented by Microsoft. Microsoft knew that this would not stand as a standard on its own, so it went ahead and influenced the voting on a massive scale (which is thoroughly documented elsewhere).
Mr. Mudd says that OOXML should be agreed upon as an 'interoperable standard'. Sadly, it is neither interoperable nor a standard. If he doesn't see this, and instead goes on about the benefits of multiple standards to distract from the real issue, then I'm afraid he has disqualifief himself completely. His professional credibility suffered greatly through a writeup such as this.
Don't associate yourself with short-sighted or (worse) deliberatly misleading opinion pieces like this, Mauricio.