ISO Rejects OOXML Protest Appeals
snydeq writes "ISO and IEC gave OOXML the greenlight after organization leaders rejected appeals from four countries to protest the vote that approved OOXML as a standard. According to an ISO press statement, appeals by the national bodies of Brazil, India, South Africa and Venezuela did not garner support from two-thirds of the members of the ISO Technical Management Board and IEC Standardization Management Board, which is required by ISO/IEC rules to keep the appeals process alive."
See NoOOXML, OpenDot, NoOOXML">Boycott Novell and Groklaw for better analysis. People are very angry about this and they should be.
What *we* can do when the goverments, corporations and organisations are corrupted and we cant turn to ask help from them, because those who has power, controls those who could help us....?
I don't get why MS really even *cares* about OOXML passing or failing. The .doc "standard" (and I use that term loosely) was still used even with it being very closed. If MS wants to use an open format then there is nothing wrong with using the more open (and vastly superior) Open Document Format. But I don't really see the motivation in trying to get OOXML to pass...
Taxation is legalized theft, no more, no less.
RIP ISO 2008
Correct NoOOXML link. This was one of the first and best of the bunch.
Nice to see that the price for ISO members was high enough to prevent appeals from going through.
Standards for sale.
Act now before the prices go up.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
The International Standards Organization today announced that it has been purchased by Microsoft for $2.5 billion. "Over the past year or so, Microsoft has paid me a shitload of money!" said the ISO's CEO while worlfing down a Microsoft-sponsored steak and lobster dinner on his lunch break. "So when Steve Balmer made the proposal to buy us, I couldn't resist!" The organization will be renamed Microsoft ISO and will focus on standardizing Microsoft's standards so that the marketing department can add standards support to feature lists.
So inertia is going to dump more crap on the world, so it seems. How a 'respected' body like ISO can let this slip through, particularly in the face of all the wheeling and dealing (corruption?) that's gone on during the voting process is depressing.
The IE6 of office software is upon us.
Smivs on the intertubes!
I think that the ISO just proved they are just another group of administrative people and have nothing to do with good reliable standards.
As bad as the situation is, this is just the beginning. ANY organization that still charges money for public standards in digital age are designed to make money, not to cater topublic interests, and will have the same problems as ISO. We should start giving new names to ISO, such as Infinitely Stupid Organization, or Internally Screwed Orifice, or Institutionalized Super Outrage.
The ISO press statement continues:
"... We're corrupt, and we're proud!"
Before we get a wikileaks of the ISO members papertrail's?
The damage to the standard has been done. There has been so much negative press swirling around OOXML that ISO approval at this point is largely symbolic and meaningless.
Microsoft shot itself in the foot by trying to bribe national ISO members instead of keeping it on the downlow and improving OOXML to appease those obsessive standard-freaks. But then again, this is Microsoft we're talking about.
I'm not a luddite and would gladly try new things (including Microsoft things), but my perception of OOXML is so low based on all the news stories I've read that I'd rather switch to papyrus than save a document in .docx
AC, your detailed technical analysis has convinced me to never trust Groklaws again. Thank you for such an insightful and objective assertion of opinion as, "unlike most readers, whenever the criticism was of a technical nature, I went to the spec itself and checked. ... those sites often lied about objective matters of fact." Such excellence is par for the course with AC comments. How can I ever thank you for saving me from "ignorance"?
Now that this is over, can someone investigate IBM? I'd like to know why they had two paid staff members writing blogs, on company time, full of technical FUD about OOXML.
Let us put it to good for once. Everyone reading this article should send at the very least one email to their elected government official. Google will tell you who to contact. We need to let our governments know how we feel about this ISO fiasco.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
Seems like "Because we hate Microsoft" isn't a compelling enough reason for the ISO.
True, but "unimplementable" should be.
weirdest thing I ever saw: scientology advertising on slashdot.
Is that a carrot in your pocket, or...
"Not an actor, but he plays one on TV."
It is not about "We head Microsoft", it is about the fact that something like WordWrapLikeWord95 should not exist in an ISO standard.
...
BTW: There was a very interesting graph in the German magazine c't. The essence was as follows:
XHTML: ~100 pages, ~400 days of standardization process
ODF: ~800 pages, ~900 days
SVG: ~600 pages. ~1050 days
SOAP: ~200 pages, ~950 days
OOXML: ~6500 pages, ~350 days.
You've no idea how incredible that looks in a graph...
I guess most of the countries' representatives ond't effectively govern as well as you could. Too bad you can't rule the world and bring us the Utopia in your head :)
Mine is Good
Is anyone surprised? Microsoft paid for that ISO fair and square. Bribed the right people, paid for the right votes. They got their money's worth. This proves that the world's way works. Corruption to some is just business to others.
But then, Slashdot is now a pro-Microsoft camp - so why all the belly-aching? I see so much praise heaped up on Microsoft here nowadays that I wonder if they'd forgotten OSS and *nix which was their original focus and forgotten the damage Microsoft has perpetuated on the computing industry as a whole. After all, it's not FAT32.com - it's Slashdot.com - but then who here even knows what that stands for anymore?
Can Microsoft be charged with fraud if they advertise that Office 2007 is OOXML compliant?
Everyone reading this article should send at the very least one email to their elected government official
I see. You've already sent correspondence to your government officials in regard to global warming, the crisis in Darfur, Russia's invasion of Georgie, alternative energy adoption, and all the other really important things.
Good thing we solved all those problems - now it's time to complain about a standard being approved by ISO that nobody cares about.
I'm a big tall mofo.
The net result of this mess looks like no program can claim to be standards compliant. No one other than M$ will be able to support OOXML due to the incomplete specification and M$ has shown no interest in supporting ODF.
I guess most of the countries' representatives ond't effectively govern as well as you could. Too bad you can't rule the world and bring us the Utopia in your head :)
Who do you think that these wonderful leaders are? They put their pants on one leg at a time just like you and me. Most of the bureaucrats who prepare these decisions are no more educated than you or I. Governments, even authoritarian ones, are the people.
What's more, I live in a democratic republic, and in such a system, the people must participate or it fails. Questioning government positions is part of what you call a country's "political discourse," which is necessary for the society as a whole to come to a coherent decision that expresses itself in elections.
weirdest thing I ever saw: scientology advertising on slashdot.
Yes, but it's a good enough reason to mod people down on /. No news there, though.
Anyone else think that this whole "ISO OOXML corruption" story is just being exaggerated and carried on by the MS-hate machines out there (slashdot being one)?
You were critically hit for no damage. The bruise will look nice, and maybe the scars will make good party talk.
I suppose I consider ISO dead now. Just like congress, they can be bought.
So, what organization is going to take over as steward of international standards processes and to take ownership of the former ISO valid standards?
Right. Nobody gives a rat's rump what I think.
I understand that OpenOffice does not absolutely conform to the ODF standard. If we can convince a beancounter that the letter of the law must be obeyed and that what MSOffice makes does not meet that requirement, MS will be able to point out that OOo doesn't fit the bill perfectly, either. So is there a plugin or something for OOo that allows creating 100% compliant ODF files?
No, because I've been reading all the articles. You'll find that there is plenty there to be pissed off about.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
I tend to look at it like this...
If nobody speaks up, Microsoft has won. There are a lot of underhanded business practices that MS has "gotten away with" because nobody cared to speak up. If people just let it die off, it opens door for other companies to undermine the standards practices because "people will soon forget."
Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
I think what the numbers mean is: the more impossible something is, the less time I want to spend reviewing it. SVG is worth getting right; OOXML is worth nothing.
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
What's more, I live in a democratic republic
Welcome to Tbilisi my Friend!
Most of the bureaucrats who prepare these decisions are no more educated than you or I.
And probably less so.
My brother wants to go into law, and is considering politics from there. While understanding of the law is great, I'd rather have a politician who could quit politics and immediately get employment in some form of skilled labor.
Good to see that technical merit is no match for dogged mediocrity. Or in this case Microsofts pocket book. Once they buy something it stays bought!
I think we should look at this as a property rights issue. When someone sends you information in a Doc format, and you don't own Office, then Microsoft should be concerned as denying your right to the information encoded on that document.
They can code all proprietary apps they like, but when my data is concerned, the means to access it should be open and public. Otherwise it's holding property for ransom, plain and simple.
Send your spendthrift head of state this
I so need to become a leader. I've been putting on my pants both legs at the same time just so that I can tell people that I'm not like them. I've also been working on a solution to put on both of my socks at the same time just in case it ever comes up.
Stop Global Warming!
Just say no to irreversible processes!
Dang, just ran out of mod points. The idea of representatives being people who want to do the right thing is considered naive, but even if writing them once in a while would produce a result like this, it's worth it. Good for you!
It is not about "We head Microsoft", it is about the fact that something like WordWrapLikeWord95 should not exist in an ISO standard.
Sure it is, if the goal of the standard is to offer forward compatibility of legacy documents.
Most of the objections around here seem to beg the question of the goals of OOXML, which are different from ODF.
My video compression blog
Most people don't care enough about learning how to use a computer and I think in general most people don't like learning anything. They know Windows and will stick by anything Microsoft does because Microsoft is familiar.
That is entirely true, which is why Plato argued that people should have superior education. Now, in the modern world, what constitutes superior eduction? Superior to what Plato knew of? Superior to what they have now? Or superior to the standard required to understand the basics of contemporary life, the technologies and societies within it, and the interactions between them? I would argue that that last option should define the minimum standard acceptable for anyone, that better should be encouraged but that since all people have some input to geopolitics, major business decisions, community policies that are likely to have a wider impact, and so on, we should never tolerate a standard of ignorance that perpetuates ignorance and harm.
Arguably, what I'm asking for is not going to be easy or cheap, but if you optimize the quality of the population, you must also optimize their ability to function together, their ability to make good decisions, and their ability to reduce unnecessary damage. At some point, the additional value brought will equal the additional cost to improve standards. That is the "ideal" point, as any more investment is burning money with no benefits and could be put elsewhere for better gain.
A "utopian" society is not a stress-free society by this standard, and there'll still be plenty of bigotry and abuse. Rather, a "utopian" society by this standard is the greatest ability and greatest freedom to choose a different path, with the least possible negative consequences for not being selfish and harmful, because people will have the understanding and tools to make genuine choices, not choices they have copied from someone else without really knowing why, or choices out of fear. To me, "utopia" isn't about perfection, it's about balance. Better understanding with no means of using that understanding isn't more "perfect" than a balance between the two. Nor is superior technology than our ability to understand what it does, why, and whether there are longer-term effects that need to be considered.
Technology should not be held back in fear, nor should understanding. By my definition of "utopia", if one is racing ahead, you should develop the counterpart until it catches up. (As a completely pointless exercise, I came up with six variables you'd need to push hard on, to keep them as close together as possible, to produce the most stable and most enlightened civilization that can be achieved at that time. I believe firmly that allowing any of those six variables to backslide will invariably destabilize society and corrupt understanding, and that all civilizations that have ever declined have done so with that being the core reason, the actual mechanics being a mere secondary effect resulting from this primary cause.)
I believe that the ignorance shown by the ISO board is a direct consequence of that board being unbalanced by my definition. It has poor understanding of the engineering and an even poorer understanding of the social consequences, simply so that it can play with shiny new toys. If there's such a thing as reincarnation, we now know what happens to cats when they die - they become board directors.
I fully accept that there'll be plenty of people who disagree with my notion of "utopia" being a state of optimized relative dynamic equilibrium, where the absolute states are always increasing, and it'd probably be a lot of people's idea of a dystopia, as it is inherently restless and requires active intervention rather than allowing the different markets to independently determine their relative pace. I also agree that a regulated balancing act of this kind may in fact not be achievable in practice, but I've yet to hear any convincing argument as to why not, only the usual stuff about big governments, which doesn't even apply to this.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
You've no idea how incredible that looks in graph...
You've now have an idea how incredible that looks in graph...
Seriously. ISO has no power of any kind over anyone. ISO only has any power or value as long as people belive ISO is worth listening to. If we all simply ignore ISO in every way we can, then they will dry up and blow away. Problem solved.
If that's the goal of the standard, then it ought to actually define what "like Word 95" means, rather than effectively saying "how Word 95 word wraps is so convoluted that we can't define it here".
Slashdotters continue to spout either ignorance or lies regarding OOXML.
You suggest that OOXML is "unimplementable"?
Then explain this study comparing cross-app compatibility of ODF and OOXML.
It gives numerical scores on the ODF and OOXML compatibility of various apps. I'll just list the "Weighed Percent" score for each app:
Results for ODF
OpenOffice 100%
StarOffice 97%
Sun plug-in for Word 96%
CleverAge/MS plug-in for Word 94%
WordPerfect 86%
KOffice 79%
Google Docs 76%
TextEdit 47%
AbiWord 55%
Results for OOXML
Office 2007 100%
Office 2003 100%
Office 2008 (Mac) 99%
OpenOffice 96%
Pages 95%
WordPerfect 84%
ThinkFree Office 83%
TextEdit 43%
The final implication stems from the surprisingly good results for OOXML implementations. Critics of OOXML have argued that it was too complex and difficult to implement. While OOXML is a long and complex standard, it is possible to offer good compatibility. In fact, our results suggest that implementations of OOXML work as well as implementations of ODF. At the level of basic word-processing that we examined, neither standard had a dominant advantage over the other in terms of compatibility scores. While ODF has had a head start that has lead to more implementations, there appears no reason why OOXML cannot catch up. After all, several developers have provided independent implementations of OOXML.
Doesn't appear that ODF is much more "implementable" than OOXML.
BTW, check out KOffice's ODF compatibility score. KOffice has been promoted around here and other places as the poster child of an ODF implementation independent of OO.o code. Well, KOffice's score isn't horrible, but isn't that great either, certainly not at the "poster child" level.
Caveat: I assume the OOXML that was tested was ECMA OOXML rather than the new ISO OOXML standard. But the ISO version actually is easier to implement than the ECMA standard, so OOXML cross-app compatibility will go up even more when ISO OOXML is implemented by the various apps.
-- "I never gave these stories much credence." - HAL 9000
"That's true; it would suck for Microsoft if Open Office was able to compete on a level playing field."
Given that a level playing field would require history to change (i.e. a timeline in which most people didn't use MS Office), it might suck for a lot of people.
..and why exactly is the GPL unethical?
It is not about "We head Microsoft", it is about the fact that something like WordWrapLikeWord95 should not exist in an ISO standard.
Slashdotters are so ignorant on OOXML yet speak so authoritatively on the subject.
WordWrapLikeWord95 isn't in the ISO standard as an opaque concept like it was in the ECMA standard. WordWrapLikeWord95, et al, are fully detailed in the ISO standard as to exactly what you'd need to do to implement them, should you wish to do so. (Those settings have also been deprecated, only for use when reading the small percentage of old documents that originally used those settings; new documents should not use them, period.)
http://blogs.msdn.com/brian_jones/archive/2008/01/18/suppresstopspacingwp-compat-settings-1.aspx
-- "I never gave these stories much credence." - HAL 9000
Actually, that's something twitter posted somewhere else.
Yeah, that's his new sockpuppets.
I was just letting him know that we found it.
because he said so
1) why would that warrant an investigation?
2) be specific about this "FUD" what did IBM say that was untrue? if you can not be specific, then it's clear to me that you are just lying.
I never understood this thing about putting your pants (we call them trousers over here) on one leg at a time. You sit on the edge of your bed, fold your legs up, and slide them simultaneously into both trouser legs. It's much easier than doing them sequentially - why would anyone do that?
I am TheRaven on Soylent News
The "messy" tags and features are non-conforming (AKA deprecated). They are in the spec only because they have to be documented somewhere for browser creators. If you wrote browser that doesn't support <font> & co., even google.com wouldn't render properly (try gaining market share with such browser).
software that is. the only people who decide what goes as standards are developers of software. if individual developers and software houses do not like OOXML and make their software accommodate it, it doesnt have a snowball's chance in hell, REGARDLESS of what you chant around. REGARDLESS of who microsoft or any other company bribes, regardless of which country mandates which standard, whichever standard wins the most support from programmers, developers, whomever creates software, will be the winner.
Read radical news here
And seeing as those legacy documents are stored in a format that is not, in fact, OOXML, how does WordWrapLikeWord95 help? A format conversion will be required anyway, so as long as the new target format has flexible enough word wrap specification, there is no need for something as specific as WordWrapLikeWord95.
The only case in which it makes any sense, and what probably is the case, is that OOXML is just a direct conversion of the old binary formats. The tag and attribute names actually often look like they were taken from the source code for old formats. Which makes it pretty easy for MS to implement the file format - they already had the code (with all the now standard-enforced bugs to boot). And about as hard for everyone else as the binary formats have been.
They also don't show the results of going the other way - saving in one of the other apps and opening in the 'reference implementation.' They are not comparing any product's implementation of either spec. If MS Office produced something completely unrelated to OOXML then you would likely get the same results due to reverse-engineering attempts by the other products.
I am TheRaven on Soylent News
Further, there are mathematical differences between the spec and what Microsoft Office does. Now which do you think an implementor will implement? Your interoperability study is based on reverse engineering, not on following any OOXML specification.
Yet further, there are defects remaining in OOXML that were not addressed and that prevent interoperability. When you try to make a specification in such a short period of time this is to be expected.
-Docvert converts MSWord to OpenDocument, clean HTML
did not garner support from two-thirds of the members of the ISO Technical Management Board and IEC Standardization Management Board, which is required by ISO/IEC rules to keep the appeals process alive.
Oh sure, now they start following the rules!
That's merely a popular example, read this for more How Many Defects Remain in OOXML
ISO Wakes from 350-Day Drinking Binge, Wonders What the Hell It Just Approved
(from the oh-man-what-a-hangover dept.)
ISO and IEC have just woken up from a 350-day drinking binge during which Microsoft footed the bill. ``It's great to be drinking with pals like ISO and IEC. Our bartenders told about 6,500 pages worth of stories, and they lapped up everything,'' stated a Microsoft spokesman. ISO and IEC simplied replied with, ``Wow, I've never seen such a liquor cabinet! Wait, did we approve something last night? Microsoft kept asking if we wanted another round of shots, and then if we wanted another round of word-wrapping styles. I can't remember what we were saying yes to... owww, my head...''
ISO and IEC lamented that there were ``these four dudes trying to crash the party'' who kept insisting that they stop drinking, sober up, and pay attention to that to which they were agreeing.
An anonymous Microsoft programmer wrote in: ``People have always just thought it was code and feature bloat, but the higher-ups have been strategizing about this for years. Nobody else can compete with a programming team of this size. Management always says more code is better... right?''
--TheOrangeSquid Is it any wonder things seem so awry? We swim in a sea of confusion and don't have to think to survive
I doubt that MS actually expects anyone to use OOXML, as it is pretty close to impossible to implement.
http://idippedut.dk/post/2008/08/06/Are-document-formats-silver-bullets.aspx
Maybe stupid idiots like you cant code wont be able to. Others can, and will. Its amazing there are idiots still complaining about binary blobs. WTF ? Disassemble that shit and understand it. I don't see crackers and hackers around the world sitting and whining they don't have the source code. They get shit done without feeling the need to sit around and blame others. If you truly _need_ the source code to understand how a program works, turn in your geek card.
But when they have to go before government agencies in various countries to answer for their monopolistic, unfair business practices they get to say, "we contributed an open document standard, and we're a big contributor to the Apache Foundation. Heck, we're all about open source and freedom!"
FUD much?
MS is simply buying its way in to "OSS", just as it has done with so many more traditional competitors before destroying them. This is very, very bad.
What is bad is retards like you are allowed to have and voice and further group-think and dumb opinions here on /.
What you really need is a scatter plot. (Note: I'm deciphering the Google Chart API as I write this; check for a link in a reply to this post.)
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
Also, I wonder if it would be better with a logarithmic scale (which the API doesn't appear to support)?
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
They're still stupid, though. Why? Because there are no old documents that originally used them because all those old documents are written in formats other than OOXML! And if you're converting them, why don't you just go ahead and do those "fully detailed" things and skip the deprecated tag altogether?!
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
In regards to the "WordWrapLikeWord95" part, I believe all those kinds of things have been removed from the spec.
As far as I can tell... it's not even in the Wiki article any more (or someone's moved it e.t.c)
Good point. Of course, if an app only needs ODF level accuracy to the original, any app implementing OOXML can just ignore those more esoteric tags. And it certainly never would need to write them. Think x86 assembly; the ancient instructions are still supported for backwards compatibility (albeit slowly), but only a subset is used in practice by modern compliers.
Sure, it'd be very difficult for any third party to implement support for the legacy tags. But it's there if they can figure it out, and it at least gives a way forward to make legacy files XML structured for easier searching and maipulation.
If you assume the goal of OOXML is to make a documented XML format that supports the features of all existing Office files, it makes a whole lot of sense. And it's a handy thing have, compared to the binary formats.
Some people may think that's not a worthwhile goal, but it's important to recognize what something is designed to do before complaining it's designed badly for how a particular person imagines using it.
My video compression blog
We didn't mind HD-DVD and Blu-Ray battling it out but when it comes to a Microsoft format... ATTAAAACK.
The idiom probably predates the common person owning an elevated bed. I've always assumed that it sprung from the fact that a manservant WOULD put their masters pants on both legs at once while their master was sitting on an elevated bed.
A commoner, having a flat pallet for a bed, would slide one leg of their breeches on and then the other as holding both legs off the ground at once is quite a challenge for most people.
What any of this has to do with ooxml I really have no idea.
I think what the numbers mean is: the more impossible something is, the less time I want to spend reviewing it.
Then reject it. Approving it because you don't want to see it is almost like marrying someone because you hate him.
If rejected (through the longer process, rather than fast track), the ISO committee never has to see the spec again. If accepted, now they are responsible for maintaining it.
You sit on the edge of your bed, fold your legs up, and slide them simultaneously into both trouser legs. It's much easier than doing them sequentially - why would anyone do that?
Real heterosexual men do it standing up.
Deserves what they get.
To anyone even moderately clueful, even from 200 yards the whiff of SharePoint says: Run away! Do not walk, run! This is not going to help you or your business in any way! This is a tarpit from which you and your data will never escape. You will be tied into Windows and whatever other tortures arrive down the pike - if you don't Just Turn Around Now and RUN! Microsoft has PLANS for you and your money... Locking up your data forever is just a means to an end...
It's extortion. Theft. Deception. And it's time we stopped tolerating it, because we know better - the Open Web itself is proof of technology and ideals that are the civilised alternative to anything Microsoft ever plotted.
you had me at #!
That's what she said!
(Sorry, hadn't ever done it before...)
My 0.02 cents
He is a Microsoft astroturfer.
I don't have a bed, you insensitive clod!
That's what she said!
2^5
Yah, your chart may be technically accurate, but mine has more punch... I have a good friend that's a PhD brain that does statistical analysis for a living... he could fill in the blanks. The only issue is though it needs to show how sucky this situation is as well as be accurate... :P
To be honest, I was hoping it'd turn out a lot better than it did. I wanted there to be a nice diagonal line for the rest of the standards, with OOXML way off it. Unfortunately, the line was more vertical than diagonal, and it needs more data points. : (
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
http://www.robweir.com/blog/images/rick.png
FishWithAHammerButWithoutAClue
i would say that people did speak up. even the members of the iso shouted about this and microsoft still won. speaking up just isn't enough when you're fighting a gorilla with 30 billion dollars profit each year.
ODF 1.0 has many defects as well and OASIS is only now trying to correct them several years after submitting the standard to ISO.
The Wraith http://ooxmlhoaxes.blogspot.com/
On the other hand: ODF was put trough ISO in 5,5 months OOXML took more than 15 months
The Wraith http://ooxmlhoaxes.blogspot.com/
The ISO standard format for computer office suite online help systems: a talking paperclip.
You're a Slashdotter. Are you spouting ignorance regarding OOXML? Or are you spouting lies regarding OOXML? Those are the only two choices right?
Who do you think that these wonderful leaders are? They put their pants on one leg at a time just like you and me. Most of the bureaucrats who prepare these decisions are no more educated than you or I. Governments, even authoritarian ones, are the people..
not mine, in the People's Democratic Wprker's Paradise Republic of Elbonia, Microsoft provides us with 3 employess, on holders our Glorious Leaders pants open while the other two pick him up and slowly lower him into his pants!
Apocalypse Cancelled, Sorry, No Ticket Refunds
Microsoft knows ISO/IEC is a big hurdle to get complete control over the software market, with this Microsoft has succeeded in corrupting ISO/IEC. Exactly the thing Microsoft wants to happen. Even worse, Microsoft managed to do this with a lot of attention from the community... which was exactly the plan of Microsoft.
The community conviniently went out of its way and made a *lot* of noise about this.
OOXML was intended to damage ISO/IEC, nothing more. And we took the bait, hook and sinker.
Questions remaining: who managed to manipulate the board into doing this? When is this corruption going to be investigated by some justice departments? What will Microsoft's next move be?
Yeah but there's a difference between fixing easily known problems (Eg, the table column limit in OOXML word processing documents) and the recently discovered problems in ODF 1.0 that weren't known at the time of standardisation.
Microsoft submitted OOXML to the international standards body Ecma International in November 2005 as an attempt to fast-track it through the ISO. Despite protests and criticisms, that process eventually proved successful on April 1, when the ISO approved OOXML as a standard.
On Wednesday, Microsoft said it will not have support for the current ISO specific for OOXML until it releases the next version of Office, code-named Office 14. The company has not said when that software will be available. Update: Microsoft to support ODF, PDF in Office next year
I guess we'll see when they actually try to do it, we'll all laugh hysterically if it turns into another Vista disaster and they can't cut features because they are locked into an ISO standard!
Apocalypse Cancelled, Sorry, No Ticket Refunds
I was originally thinking along the lines you were - but now I'm not so sure. I think under the right conditions they could get bitten by this, and hard.
It certainly depends on how the laws and regulations regarding these standards are written. In the best places they'll have reviewed the standard and found it lacking, but obviously that's not most places. However, depending on the language, failure of the standard to REALLY be open may be a legally binding requirement on them - and that their software is actually compliant with the standards will almost certainly be.
Now, I'd be amazed if any govt org that was duped by OOXML in the first place would then later sue MS for breach of contract. But where they really might get screwed is that, I THINK, they wouldn't have to. Because the government per se isn't the only hurt party. Potentially a class of all citizens who pay taxes there are, if you get a zealous class action attorney.
But there ALSO is definite and direct harm to any competitor who was trying to peddle e.g. ODF, if an MS product wins a contract with an openness clause and you can demonstrate - which you can - that they didn't actually implement OOXML. Going up against MS isn't a lawsuit for the faint of heart, but for someone with a big enough pocketbook, the payoff could potentially be huge... OOXML could have precedent-setting bans against such use, which would leave a significant void for... *drumroll* a company who was peddling e.g. ODF - especially a company that just beat MS and presumably got press about it.
Looking for freelance Actionscript (Flash/Flex) or ColdFusion work and/or freelance developers. Email me, put Slashdot
it pretty effectively shows how little consideration time was put into each page of OOXML spec compared to other specifications
Apocalypse Cancelled, Sorry, No Ticket Refunds
you must be new around here, the OOXM/ISOL brouhaha was pretty mild for Microsoft; usually they kill the men, rape the women and eat the children.
Apocalypse Cancelled, Sorry, No Ticket Refunds
"I guess we'll see when they actually try to do it, we'll all laugh hysterically if it turns into another Vista disaster and they can't cut features because they are locked into an ISO standard!
Of course, when that doesn't happen, you won't have the guts to eat crow.
Also, OO.o cut features from their own ODF 1.0 implementation. Have a laugh about that, moron.
The laughs on you, I edit LaTeX source with Emacs you insensitive clod
Apocalypse Cancelled, Sorry, No Ticket Refunds
So OOXML shouldn't be standardized because it's unimplementable.
It's unimplementable because the standard doesn't yet exist.
And it shouldn't be standardized because it's unimplementable.
It's unimplementable because the standard doesn't yet exist.
etc..
Circular logic - the M.O. of a moron.
Oh, linking to Rob Weirdo might convince MS haters but does nothing for rational folk. Rob Weirdo is a proven liar.
Your personal insults are based on a misunderstanding. It does however reveal how quickly you will resort to that, and that you do that rather than asking questions to better understand another person.
Ah, but OpenOffice explicitly doesn't support OOXML - it supports a reverse-engineered version of Microsoft Office's version of OOXML. Since they're creating the documents in MS Office, all that's saying is that a software that's put a lot of effort into being interoperable with Microsoft Office has managed to mostly achieve it. (Also, you'll notice that each list contains different software, and that where a piece of software is on both lists its compatibility scores for OOXML and ODF are very similar. It looks like the score depends more on the quality of the software than of the standard, which isn't surprising - it's probably mainly influenced by what features each piece of software supports, rather than by its support for the two document formats.)
Except, once my pants are on, I make gold records!
I cried real tears when Li Mu Bai died.