Open Sauce Software
Tasty titbits from people using Linux and other open source software in business.
Tuesday 7 October 2008, 10:45 AM
ISO's SC34: the Large Standard Collider
Like that other Swiss science project, standards maker ISO has accelerated ODF and OOXML on two separate paths, and now it is colliding them, in a small space: the SC34 committee. What unknown particles will emerge?
ISO's "takeover" of ODF, it turns out, isn't unwelcome, even to ODF editor, Patrick Durusau. There will surely be more viewpoints, but at the moment, what I'm hearing is that ISO SC34 just wants to treat the standards equally, so neither Ecma (which submitted Microsoft's OOXML), or Oasis (which submitted ODF) gets a free ride. ISO says this ensures standards users - including national governments - get standards that are stable, and have defects dealt with promptly.
There's a question begged there, of course. Stability is not the same thing as quality. ISO got off to a shaky start and a blaze of poor publicity (to say the least) with OOXML, but even if it nails it all down to make something solid, will it be practical, will it be implemented, and will it be used? I can't help remembering the very stable - and little-implemented - OSI network protocols of years ago.
At least fifteen countries have adopted ODF as a Government standard, according to the ODF Alliance, and we're coming up to the second International ODF Workshop in South Africa. On one level at least, I wonder why ODF people need to worry.
The answer to that is - this is politics. Alex Brown, for instance, seems to speak for both standards (at least within the ISO world) but is slated as an OOXML booster. Patrick Durusau is editing ODF, but widely criticised as an OOXML supporter.
On the other side, IBM has plenty of people promoting ODF - and, we're told, its criticism of standards bodies is spite against OOXML. IBM's threat to absent itself from standards bodies is apparently more than a threat, with empty seats at the Korean meeting of SC34.
ISO's "takeover" of ODF, it turns out, isn't unwelcome, even to ODF editor, Patrick Durusau. There will surely be more viewpoints, but at the moment, what I'm hearing is that ISO SC34 just wants to treat the standards equally, so neither Ecma (which submitted Microsoft's OOXML), or Oasis (which submitted ODF) gets a free ride. ISO says this ensures standards users - including national governments - get standards that are stable, and have defects dealt with promptly.
There's a question begged there, of course. Stability is not the same thing as quality. ISO got off to a shaky start and a blaze of poor publicity (to say the least) with OOXML, but even if it nails it all down to make something solid, will it be practical, will it be implemented, and will it be used? I can't help remembering the very stable - and little-implemented - OSI network protocols of years ago.
At least fifteen countries have adopted ODF as a Government standard, according to the ODF Alliance, and we're coming up to the second International ODF Workshop in South Africa. On one level at least, I wonder why ODF people need to worry.
The answer to that is - this is politics. Alex Brown, for instance, seems to speak for both standards (at least within the ISO world) but is slated as an OOXML booster. Patrick Durusau is editing ODF, but widely criticised as an OOXML supporter.
On the other side, IBM has plenty of people promoting ODF - and, we're told, its criticism of standards bodies is spite against OOXML. IBM's threat to absent itself from standards bodies is apparently more than a threat, with empty seats at the Korean meeting of SC34.
Sunday 5 October 2008, 10:36 PM
ISO's OOXML committee in ODF takeover bid?
The standards world continues to surprise us - this time with what has been described as a "coup". Those in charge of OOXML are, we are told, actually trying to take over the rival ODF standard.
It's all a bit opaque, but the OOXML standard from Microsoft is maintained by a committee set up by ISO/IEC. called SC34. This is the group tasked with fixing flaws in OOXML, that remained following the Ballot Resolution Meeting, despite OOXML's enshrinement as ISO/IEC 29500:2008.
This committee has now - if I understand it right - offered to help Oasis, the source of the rival ODF standard (accepted as ISO/IEC 26300: 2006) to maintain that standard too.
Is that a good idea? Well, Pamela Jones at Groklaw doesn't think so. Eight of SC34's 19 members are Microsoft employees, and two are from ECMA. And Oasis already has a group maintaining the standard, she points out.
"Considering that ODF is already in use around the world, and OOXML is still being pulled together into a workable shape, why would ODF leave OASIS and go to the home of a "standard" that isn't done yet?" asks Jones' "logical brain".
I'm sure I'll hear other answers on this, too.
And indeed I have: There is another, and very interesting, viewpoint within ISO, which I'll be posting here later today.
It's all a bit opaque, but the OOXML standard from Microsoft is maintained by a committee set up by ISO/IEC. called SC34. This is the group tasked with fixing flaws in OOXML, that remained following the Ballot Resolution Meeting, despite OOXML's enshrinement as ISO/IEC 29500:2008.
This committee has now - if I understand it right - offered to help Oasis, the source of the rival ODF standard (accepted as ISO/IEC 26300: 2006) to maintain that standard too.
Is that a good idea? Well, Pamela Jones at Groklaw doesn't think so. Eight of SC34's 19 members are Microsoft employees, and two are from ECMA. And Oasis already has a group maintaining the standard, she points out.
"Considering that ODF is already in use around the world, and OOXML is still being pulled together into a workable shape, why would ODF leave OASIS and go to the home of a "standard" that isn't done yet?" asks Jones' "logical brain".
I'm sure I'll hear other answers on this, too.
And indeed I have: There is another, and very interesting, viewpoint within ISO, which I'll be posting here later today.
Previous
