OOXML paralyzes ISO
About a month and a half ago , a burning problem was vigorously discussed here : ODF vs OOXML. Now you can summarize the interim results. We will leave the question of technical superiority aside (this is a separate issue), but from the point of view of organization, OOXML can celebrate a victory.
As anticipated by the Microsoft standard “ refreshing infusion of new blood ” led to what it was supposed to lead to: the work of the ISO / IEC JTC1 SC 34 committee was paralyzed .
The thing is that in order for the standardization committee to be able to make any decision, at least half of the “full members of the committee” (P-members) must take part in the vote. But this committee was not created to discuss two standards. He discusses things like the development of Relax NG, Schematron, PDF, and other “irrelevant little things.” All of this is not of interest to the “new blood”: out of 11 “new participants” only one took part and that only in one vote (out of the three that took place last month). Moreover, it is not even required that they consider the issue on the merits! It is enough to send the decision “we abstain from voting” (vote “Abstain”). And that’s it. However, for "extremely interested" new members of the committee (who, we note, for the most part, they did not forget to vote “for” OOXML in the appropriate vote), even this requirement turned out to be overwhelming. Even after they have been explicitly pointed out to this (pay attention to the passagePlease remember that abstention is a valid vote and will help the committee continue its progress ).
Of course, you can continue to believe that the "new blood" is interested in something, in addition to Microsoft "stroking their heads" (this does not have to be a bribe to officials - you can also promise completely legal discounts), but somehow then it’s becoming harder and harder to believe.
PS Note that ODF did not cause such a storm of emotions or such a surge of activity and, of course, did not lead to paralysis of the corresponding ISO subcommittee ... So at this point OOXML wins dry ... Doubtful, true, victory is obtained ...
As anticipated by the Microsoft standard “ refreshing infusion of new blood ” led to what it was supposed to lead to: the work of the ISO / IEC JTC1 SC 34 committee was paralyzed .
The thing is that in order for the standardization committee to be able to make any decision, at least half of the “full members of the committee” (P-members) must take part in the vote. But this committee was not created to discuss two standards. He discusses things like the development of Relax NG, Schematron, PDF, and other “irrelevant little things.” All of this is not of interest to the “new blood”: out of 11 “new participants” only one took part and that only in one vote (out of the three that took place last month). Moreover, it is not even required that they consider the issue on the merits! It is enough to send the decision “we abstain from voting” (vote “Abstain”). And that’s it. However, for "extremely interested" new members of the committee (who, we note, for the most part, they did not forget to vote “for” OOXML in the appropriate vote), even this requirement turned out to be overwhelming. Even after they have been explicitly pointed out to this (pay attention to the passagePlease remember that abstention is a valid vote and will help the committee continue its progress ).
Of course, you can continue to believe that the "new blood" is interested in something, in addition to Microsoft "stroking their heads" (this does not have to be a bribe to officials - you can also promise completely legal discounts), but somehow then it’s becoming harder and harder to believe.
PS Note that ODF did not cause such a storm of emotions or such a surge of activity and, of course, did not lead to paralysis of the corresponding ISO subcommittee ... So at this point OOXML wins dry ... Doubtful, true, victory is obtained ...