The Fellowship / Fellows / ciaran / Ciarán's free software notes

Ciarán's free software notes

Ciaran O'Riordan's irregularly kept software freedom journal

Limit entries displayed: [ 2 ] [ 4 ] [ 6 ] [ 8 ]

What to do with ISO and OOXML?

So, FSFE is concerned about the ISO process, but the ISO process is not over, and the ISO process is not the only process. First, ISO endorsement does not automatically lead to endorsement by national governments. Second, there are still two months during which the ISO votes can be contested - and there are already a lot of allegations of voting irregularities.

The national level

Sometime in the future, separate to the ISO vote, each country will make its own decision to accept/reject the ODF and OOXML standards. Many countries have already accepted ODF.

Voting irregularities

OOXML needed 22 votes out of 32 to be approved. It got 24 because a lot of countries changed their vote in the last few days. Now there are numerous complaints about those votes. If 3 of those "approve" were changed back to "disapprove" in the next two months, then OOXML would be denied ISO certification.

UPDATE: Computerworld is carrying an article saying that the European Commission started investigating Microsoft's participation in February, and this story is also on CNet.

Noooxml.org also have a page of irregularities, and more stories will surely appear on Groklaw.

Related press releases

And, for what it's worth, here's a list of some press releases from organisations who were also against OOXML.

-- 
Ciarán O'Riordan,
Support free software: Join FSFE's Fellowship

What's wrong with OOXML anyway?

ISO has now approved OOXML. In FSFE, as our press release title says, that makes us concerned about quality of standardisation process; but if you're like most of the world and haven't followed every OOXML blog entry from Andy Updegrove, noooxml.org and Groklaw, you may be wondering: what's wrong with OOXML anyway?

I'll try to summarise points from those blogs and FSFE's previous writings on the issue. Because this news is unfolding fast, I'll put this blog entry online section by section as I write it.

Patents

When people pointed out the danger of Microsoft's patents, Microsoft published an "Open Specification Promise" saying that they won't use their products against your project "to the extent it conforms to" the OOXML specification. However, Microsoft's own word processor does not fully comply with the OOXML specification, so if you try to make software compatible with their word processor, they can still use their patents against you. (This was pointed out FSF Latin America)

Further problems with their promise have been detailed in SFLC's document No Assurance for GPL.

Technical

wreck
Archive your data here?

It is known that the OOXML specification contains hundreds of problems. The Grokdoc website lists many, and the national standards bodies submitted more than 1,100 in September 2007. When these were discussed in Geneva at the end of February, it was concluded that there was nowhere near enough time to discuss all the problems. A bulk vote was proposed on the Thursday and on Friday a 6:4 vote approved, without discussion, Microsoft's suggestons for 900 problems.

ISO not up to the task

It seems ISO was not up to the task of making a technical decision under pressure, and failed to fix their process when the cracks became obvious. ODF remains the only open standard. There are claims of voting irregularities in United Kingdom, Germany+Croatia, Norway, Poland and others.


[ RSS Feed ]

Right menu

Fellow Events

<< May 2008 >>
Mon Tue Wed Thu Fri Sat Sun
  1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
Selected Day Today


FSFE Card


DRM.info
© FSFE