Slashdot Mirror
Microsoft Standing Firm On OOXML ISO Vote
christian.einfeldt writes "Microsoft has responded via the industry trade group ECMA to some of the thousands of criticisms of its submission of Office Open XML as an ISO standard. Open standards advocate Russell Ossendryver takes a look at those responses to see if Microsoft has made significant changes in either the substance of OOXML or the manner in which the OOXML specification will be maintained going forward. Ossendryver concludes that Microsoft's position has not significantly changed, but only hardened in place in advance of the Ballot Resolution Meeting which is to occur from February 25 through 29 in Geneva. While no one can say for certain whether Microsoft will succeed in having OOXML win the nod from the international community, Ossendryer thinks that Microsoft's firm stance is likely to backfire."
I believe Microsoft made 5 billion in revenue from having customers worldwide locked into their proprietary office document format.
The vendor lockin from Office makes up almost half the company's yearly revenue.
Microsoft would cease to exist as we know it if the office document lockin revenue went away to an open format.
Fight? LOL! This is the type of shit Microsoft execs live for.
Fake grassroots efforts.
Standards body subversion.
Paid for media shills.
Shame studies.
Mysterious compatibility problems with the competition.
All in a days work.
MSFT has so badly screwed up ISO, I can see many parties who were going to vote yes to change it into No.
directly because of MSFT the ISO has done nothing but stumble around they can't get the majorities that they need in oder to pass standards. Everything is stagnate. Here's to hope that MSFT gamed the system so hard that it blows up in MSFT's face.
i thought once I was found, but it was only a dream.
Petition currently running at noooxml.org
http://www.noooxml.org/petition
Which OOXML most certainly isn't. There's real doubts that even Microsoft could implement it as it currently stands.
It's a scam, pure and simple.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Guarantee to me in writing that you will update Office 2007 and Office 2008 so that the version of OOXML that they use will be exactly identical to your ISO submission in every way, and then carry out your promise, and I will join the OOXML camp.
Sincerely,
ODF supporter.
The horse has left without the cart. Office already saves thousands, if not millions, of documents in OOXML - today. MS cannot change their format - the spec is in the field. I'm somewhat surprised they haven't taken some things into consideration for future releases, but frankly the reality set.
OOXML is not a standard. It cannot be used to shield any entity from MS's product changes. Also, OOXML extends into nebulous areas where other implementors or translators will be unable to replicate the viewers or editors like Office. Governments or corporations must take it or leave it.
PS
I recently received a DOCX from an MS rep and wrote back asking for a DOC format (we've not upgraded). They sent me a PDF. Moral: OOXML isn't a standard. There's no turning back - its a conversion world, not an interoperable one.
Many reasons:
1. There is already an ISO standard for this same purpose.
2. There are exclusions in Microsoft's Open Specification Promise, meaning Microsoft can sue over other parties writing implementations of some of the things that the OOXML standard references (ActiveX and VBA are examples).
3. OOXML is designed so that fully-compliant applications can only be written by Microsoft, and mostly-complaint applications can be written by other parties but only to run on a Windows platform. Therefore OOXML is not inter-operable with other applications and especially not with non-Windows platforms, and the whole purpose of making something a standard is to facilitate such inter-operation.
4. OOXML is technically very inferior to the existing standard, ISO 26300. For example, OOXML specifies three different implementations of "a table", instead of just one common to different Office applications. This means that you cannot write a "table handling class" as a library, but instead you have to duplicate equivalent functionality several times over.
5. OOXML includes deliberately mandating bugs (such as dates before 1900) just to pander to errors in Microsoft software.
6. OOXML is controlled by just one corporation
7. ISO 26300 already has many implementations by many vendors on multiple platform. OTOH even Office 2007 running on Windows Vista does not implement OOXML
8. ISO 26300 even works with Microsoft Office (up to Office 2003) using a free plugin written by Sun. Microsoft deliberately broke Office 2007 file filters so that this plugin (or any other plugin not written by Microsoft) would not work in Office 2007.
9. ISO 26300 has a compliance test suite. You can use this test suite to make sure a given application works properly with ISO 26300. No such thing exists with OOXML.
10. It makes no sense to have "choice in standards"
They actually hold multiple patents (18 currently held, or pending) that apply to OOXML. My worst fear however, is that they'll maintain the format, and change it continually, not warning anyone when they're going to make a unilateral move. Leaving everyone else who wants to read documents sent to them in that format in the dark.
It's a scam, pure and simple.
So what do we do?
That's right: whenever you receive a .docx, .xlsx and other .*x documents, send them back, asking that they be converted into a readable format.
Include a link for Sun's ODF plugin for MS Office, if need be.
Fight fire with fire.
Ignore this signature. By order.
But it does make a difference. Microsoft isn't doing this just to promulgate yet another document format. This is about the long-term viability of one of their major profit centers; the Office suite. Sure, docx is out in the wild, and sure we're all going to have to deal with until it's dumped and/or heavily modified version-by-version just as the Office 97 formats have been.
As more and more organizations, and in particular various government agencies around the world start mandating that all documents be saved in an open format, this is where Microsoft's viability in the long term comes into question. If OOXML fails at the ISO (as it appears that it has a good chance of doing) then Microsoft has got a real long-term problem. Adopting ODF means opening up Office to meaningful competition. It means OO.org, KOffice, Google Docs and who the hell knows what else is coming down the pike over the next decade are going to start to eat into Office's huge market share.
Now I think it's safe to say that in the medium term, Microsoft will continue with OOXML no matter what the ISO does, and it will, even if it adopts to some degree ODF try to mutilate by the "adopt, extend, extinguish" doctrine, and a good many government agencies, regardless of the mandate by politicians and senior bureaucrats, will roll over, but not all, and as long as a few major government agencies in North America and/or Europe refuse to recognize OOXML or whatever Microsoft comes up with next as an open format, the long-term viability of Office is in question.
We're not talking about next year, or even in the next five years, but I think over the next decade or so, if Microsoft can't fool ISO into accepting its worthless, unimplementable format, then it's going to have a real problem. The whole structure of company is built on the operating system and Office divisions keeping the money rolling in. Everything else doesn't matter, and probably loses money, existing solely in the interests of brand name placement.
The long-term solution I suspect Microsoft will move towards is some sort of rubber stamp standards commitee to compete with ISO, just like ECMA. The ultimate question is how long governments are going to let it get away with all of this. The EU seems to have a distinct hard-on against Microsoft at the moment, but the US doesn't currently give a damn one way or the other.
The world's burning. Moped Jesus spotted on I50. Details at 11.
They have partial implementations. Quit making things up. Not even Microsoft has an implemented ECMA-accepted OOXML product out there so how can you justify what you're saying.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Relying on current application behaviour is not bad per se. It is bad not to reveal what the application does. Things like autoSpaceLikeWord95 are referenced but not specified. This is objectively bad. Just think of it: I give a new screw standards paper to the ISO. It simply says that the screw can easily be driven in with my old Bauhaus 95 screwdriver. However, the spec doesn't say what the dimensions of my screwdriver actually are. Do you think ISO should make this a standard ?
Of course they are. There is, for example, only one ISO standard for paper sizes, ISO 216. http://en.wikipedia.org/wiki/Paper_size#The_international_standard:_ISO_216
This standard is used in all countries bar two. Becase there are two countries that use a competing non-ISO standard (they use an ANSI standard instead), it causes all sorts of un-necessary costs all around the world.
Actually, it is you who is misleading here, and your anti-ODF FUD is from brian Jones in 2005 (when OOXML also lacked any definition of formula syntax). ODF version 1.2, which is currently going through the approval process, has a far more detailed definition of formula syntax, known as OpenFormula, defined by an independent body. http://en.wikipedia.org/wiki/OpenFormula This is what will be formally agreed in the upcoming version of ODF, but it is backward compatible with the (admittedly vauge) syntax definition in earlier versions of ODF, and it is also what all of the ODF applications actually now use.
OpenFormula is indeed technically superior to the formula syntax of OOXML, for the following reasons: http://en.wikipedia.org/wiki/OpenFormula#OpenFormula_Attributes
No, it is not. Before it was an ISO standard, it was an OASIS standard, and Microsoft were part of OASIS. Microsoft were invited to join the development process of ODF, which began in 2002, but Microsoft refused. Apart from the solitary exception of Microsoft, however, ODF otherwise has full industry consensus. In fact, after a long review period where comments from a broad array of interested parties were invited and incorporated, the ODF specification was put to a formal vote for OASIS approval, and it was passed unanimously. Yes, as an OASIS member, Microsoft approved ODF. Further, after that vote, ODF was submitted to ISO for approval as an International standard, via the long-winded PAS process (not fast-track), and after world-wide solicitation of comment and incorporation of recommendations, it was again approved unanimously. Yes, Microsoft approved it a second time ... then refused to implement it.
It wasn't wrong for the original release of Ofice 2007. Full plugins were borked in that release. I'm pleased to see that Microsoft fixed it (now that Office 2007 has a foothold) in SP1. As for Microsoft-sponsored ODF convertors ... they are convertors, not plugins. You cannot use Microsoft's convertors to open & save as ODF ... you must have an OOXML version of your document first, and then you can import & export it as ODF. Microsoft convertors do a terrible job compared to the Sun plugin, and of course you cannot set Office 2007 as the default for .odx file extensions because Office 2007 can't open them directly (without Sun's plugin).
... all the more reason to use ODF (ISO 26300) format and not OOXML.
Anyway, now that Sun's plugin works for Office 2007
The fact that there are work-arounds for all of these things doesn't negate the fact that they were locked down in the first place.
The iTunes DRM is roughly equivalant to a false positive for piracy in Windows Genuine Advantage. They've purchased the product, but now there are these digital hand-cuffs keeping them from using it. I doubt anyone saying that "false positives in WGA aren't too bad - there are work arounds. [link]" would get modded up too far, though.