India Votes Against OOXML 171
harsha_c sends in a local Indian perspective on the vote against Microsoft's OOXML ahead of the March 29 deadline. Of 19 companies participating, only 5 voted in favor of OOXML. "It was the ultimate battle for control over global IT standard for documents — between Microsoft-promoted OOXML and Sun and IBM-backed Open Document Format. It was played out between Indian IT giants, namely Infosys, Wipro, TCS supported by Nasscom on one side and the global IT biggies like IBM, Sun Microsystems, Red Hat backed by te IITs, IIMs and IISc on the other, on their respective positions on Microsoft's OOXML standard. Microsoft understandably expressed its disspointment. 'While we are disappointed with the decision of the BIS committee, we are encouraged by the support from NASSCOM.'
Hooray! An honest nation! (Score:3, Interesting)
Re:Hooray! An honest nation! (Score:4, Insightful)
Huh??? (Score:5, Insightful)
Then, you say "OOXML really makes no difference", and continue on to say "except for... not having... an overpriced, closed vendor...".
Ditto. You start each sentence one way, then contradict yourself later in the same sentence. Sorry, but you can't have it both ways.
Moderator should STFU (Score:2, Interesting)
Contradiction isn't contradiction (Score:2)
Re: (Score:3, Insightful)
Honestly, most companies will go with Office anyway because there's still Outlook, Excel, PowerPoint, and Access. Most of those are at least as entrenched as Word.
ODF vs OOXML is important in a philosophical kinda way, but I don't expect much practical change.
Re: (Score:3, Insightful)
Re: (Score:3, Insightful)
What do you foresee some of the practical implications being? Companies continue to use Office exclusively, but now their internal documents are saved in ODF?
Standardization is great, but this is such a small step I don't see it having an impact. Nobody is going to use two office suites. Nobody is going to buy Excel, PowerPoint, Outlook and Access separately and then use OpenOffice for word processing. Until there are standardized formats covering the rest of Office's components, any actual change i
Re: (Score:2)
Re: (Score:2)
Yeah... But for many people who take work home, "work" could just as well include spreadsheets, presentations, and email. And since they're going to need Office for those anyway, might as well buy Office and use Word also.
As for businesses interacting with governments, a lot of that is already done through PDF. For the times it's not PDF, it's just as likely to be Excel spreadsheets or PowerPoint presentations, as it is Word documents.
I'm not saying the change shouldn't be made. I'm just pointing
Re: (Score:2)
You're missing my point. The main issue slowing adoption of Google Apps, OpenOffice, KOffice, Gnumeric, and the others is their poor compatibility with Office as a whole. ODF and OOXML cover word processing document formats. That still leaves spreadsheets, presentations, small databases, and the stuff Outlook does. Most companies buy Office and use that for everything. They're not going to stop using Excel, PowerPoint, Access and Outlook simply because they can open Word documents in other programs.
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Insightful)
I disagree. For the time being, MS has almost nothing to lose from this. Companies and governments are still going to buy Office for Excel, PowerPoint, Access and Outlook. Worst case scenario, they'll have to shell out an extra $50 for a third party ODF import/export plugin. More likely, MS will make their own exporter and include it. Hell, they could sell it as an add-on and make even more money off of Office. Just because Word will have to support ODF doesn't mean it has to be the default format.
Re: (Score:2)
Like any geek, I like the idea of Microsoft being forced into submission, but document format standardization isn't going to be what does it. Maybe when the rest of the office formats are standardized.
Um, that's what they're doing! A lot of people respond to anything about OOXML with "Microsoft should just drop it and use ODF", but those arguments always miss the point - that OOXML is actually a standardised version of all of the Office formats. Microsoft can't just drop OOXML and use ODF because they aren't really comparable. ODF is a document format, OOXML is a format designed to cover 5 different types of documents - and people wonder why the spec is bloated.
Re: (Score:2)
ODF has a clear design. Microsoft can use it.
Re: (Score:2)
Interesting though that you didn't mention that the ODF format extends to more than just documents (that OpenDocument name really sucks for ambiguity) but rather decided to make a bunch of completely irrelevant statements. It's how I know I'm on Slashdot.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
And then you have corrupt nations that sell their voice far too cheap. Standard people need to eat a
Re: (Score:2)
Re: (Score:2, Insightful)
Re:"not properly document" criticism is invalid (Score:5, Informative)
autoSpaceLikeWord95 and useWord97LineBreakRules (Score:5, Informative)
Re:autoSpaceLikeWord95 and useWord97LineBreakRules (Score:5, Insightful)
As soon as the revised spec is published by Ecma, the information will be in the public domain. It's crap all right, but it's not "proprietary crap" any longer. And it's certainly no longer an example of missing information in the OOXML spec.
I agree that it is debatable at least whether this kind of information really belongs into a standard. But what would you suggest that should be done with this information?
Re:autoSpaceLikeWord95 and useWord97LineBreakRules (Score:5, Insightful)
Re:autoSpaceLikeWord95 and useWord97LineBreakRules (Score:4, Insightful)
They should convert that information into the equivalent representation in their new format. Replacement of specific spaces with hard breaks or forced non-breaks or whatever will cause the resulting document to print exactly the same and would not require this stuff.
This puts all the ugly part of implementing this information into the program that is reading the
Explicit rendering instructions (Score:2)
Remove obscure rendering instructions from the standard. Have the vendor saving the document decide to set 'autoSpaceRule="ExplicitRule"' and 'lineBreak="ExplicitRule"'.
If "autoSpaceLikeWord95" and "useWord97LineBreakRules" rendering requires making paragraph level or even word level changes to autospacing and line breaks, then apply the attributes to the affeceted paragraphs. In other words, instead of 'useWord97LineBreakRules="true"
Re: (Score:2)
Re: (Score:3, Informative)
Re: (Score:2)
Re:Hooray! An honest nation! (Score:5, Insightful)
But just because someone is against Microsoft on this issue doesn't mean they are 'honest' or honorable with their intent or motivation.
India is a growing IT powerhouse. When Microsoft provides the basis for participation in IT products and services, it goes without saying that they have influence in your success or failure. It may well be that India's motivation is simply to help Microsoft become irrelevant so that their potential is no longer dependent on Microsoft's will. After all, Microsoft is an American company and as such is subject to influence of the U.S. government. You can see that there's plenty of reason to mistrust Microsoft.
You can dishonestly argue for the right thing (Score:2, Insightful)
Yes, but... (Score:5, Informative)
This is not something I made up. All you have to do is read the articles linked to from here, and perhaps Ars Technica. Other places too, but that should be enough to convince anyone.
Re: (Score:3, Insightful)
Re: (Score:2, Insightful)
One link. There are many out there. Just look. (Score:3, Informative)
Re:One link. There are many out there. Just look. (Score:5, Informative)
I do not think it is out of scope to take into account the past trustworthiness of Microsoft as an international entity, either. You may disagree with that, but the linked post can't really be argued against.
Re: (Score:2)
I do not deny that there are plenty of design issues with OOXML. The statement which I have been challenging was that Microsoft "refused to address" them.
Not having first hand experience with this particular issue, I can't refute that. I have to admit I'd be very suspicious that any software company would be too willing to spend time add
Re: (Score:2)
Microsoft offered nothing additionally.
The specification as it came out of the BRM is totally immature. Most comment resolutions were block approved because the BRM had limited time. We can expect that there are still hundreds of problems, which is totally unsuitable for an international standard.
It is a multi-billion dollar bet and Microsoft fights with all legal means.
What happens when ISO members disapprove t
Re:Hooray! An honest nation! (Score:5, Funny)
That's funny; I always thought it was the other way round.
You make my point for me. (Score:2)
Re: (Score:2)
Seems like a very honest and honerable thing to do. I couldn't find the bit were you talk about India being dishonest and untrustworthy, just because they don't want Microsoft?
Dishonesty of voting for OOXM (Score:5, Insightful)
Either they are dishonest because they don't understand what they're doing while claiming to understand, or they're dishonest because they're knowingly voting against their country's best interest.
Nota bene, the representatives of Microsoft Corporation and partner companies are not necessarily dishonest in their lobbying for "APPROVE" votes, since what they ask for is genuinely in their interest. But the national bodies are supposed to represent the correspondiong national interest!
"One standard" vs "multiple standards" (Score:4, Insightful)
In fact facilitating technical progress requires that the "no contradicting standards" rule cannot be strictly enforced.
In this situation however there is a serious problem. Because of Microsoft's dominant market position, if OOXML gets ISO/IEC approval, that will probably kill ODF. The problem with this is that this kills investments in ODF. If Microsoft is allowed to get away with this, the net result will be a chilling effect on all investments in non-Microsoft standards.
Re:"One standard" vs "multiple standards" (Score:5, Insightful)
It may take a while for the smoke and mirrors to clear, but in the end, the truth will out.
Re: (Score:3, Interesting)
Re: (Score:2)
And you, sir, live in a dream world where corrupt and/or clueless politicians, shady back-room deals, and money-trumps-all reality don't exist.
Re: (Score:2)
I do not suppose that many politicians are wise and reputable, although is just possible some are. However, being old, I know that the life of a government is short, while the life of software is long. Look how no one has ever made money from Un*x, but Un*x lives. Sure people may vote in parliaments for all sorts of things, but over many years, it has becom
on the openness of OOXML (Score:2, Informative)
OOXML can't kill ODF, because ODF is open, and OOXML isnt. People who want to guarantee access to their documents in perpetuity (eg legitimate governments) cannot use OOXML because it cannot meet their needs.
Microsoft is working hard on making OOXML as open as it needs to be in order to meet the requirements of the relevant decision-makers. Of course, whether that is open enough to allow genuine free software implementations is not a question that Microsoft really care
Re: (Score:2)
But if you think that ODF can survive in competition against OOXML if both are ISO standards, you're kidding yourself.
What kind of competition would that be? Certainly not a competition based on having a viable alternative implementations. Anyone care to speculate on the first non-MS implementation of OOXML to pass the OOXML Acid 3 test suite?
Don't everybody stampede all at once to http://www.longbets.org/ [longbets.org]
To cover a 6000 page specification that hasn't yet undergone a clarity bulk-out, the OOXML Acid 3 test suite would need to incorporate on the order of 20,000 distinct unit tests.
With an implementation, a test suite, or
Re: (Score:2, Insightful)
So why do you think they started creating their own format in the first place?
They migrated from their binary formats to an XML based format because they're convinced that XML is the way of the future. Documentation of this format is what they submitted as the starting point for creating the OOXML "standard".
Why should you create another format if there already is an open one?
Because Microsoft has a strong enough market position that they thought that could get away with doing their own thing and essentially forcing the whole world to go along with them.
Even if they're forced now to make OOXML a genuinely open and technically acceptable standard
Re:"One standard" vs "multiple standards" (Score:5, Insightful)
Re: (Score:2)
It may take a while for the smoke and mirrors to clear, but in the end, the truth will out.
I wish I shared your faith.
To my mind, governments mandating that documents are stored using an open standard are doing so with good intention - so they can't be held to ransom by an arbi
Re: (Score:2)
Re: (Score:2)
If the people in positions of power did understand the importance of open standards, then microsoft would never have got to where they are today in the first place.
Re: (Score:2)
Can you give your definition of "open"?
Re: (Score:3, Informative)
Can you give your definition of "open"?
Where as my
~Dan
Re: (Score:2)
I'm shocked to find out that Pages, Numbers, and TextEdit on my Mac, not to mention my iPhone, are Microsoft products.
And when did Microsoft acquire Thinkfree Office? Dataviz? Intergen? NeoOffice? Zoho Writer?
Re: (Score:2)
I'm shocked to find out that Pages, Numbers, and TextEdit on my Mac, not to mention my iPhone, are Microsoft products.
And when did Microsoft acquire Thinkfree Office? Dataviz? Intergen? NeoOffice? Zoho Writer?
~Dan
Re: (Score:2)
can you?
the Irony of your last post is... Well I don't want to confuse you any further.
Re: (Score:2)
And for the record, OpenOffice.org 3 Alpha can natively open, read and save OOXML.
Re: (Score:2)
I think what he meant (although far less eloquently than it could have been put) is that you can't really make a statement regarding the ability of various software to open OOXML documents when you have expressed a complete ignorance to all products which are not the ones you use.
And for the record, OpenOffice.org 3 Alpha can natively open, read and save OOXML.
I don't see what that has to do with my posts
.odf doesn't need any reverse engineering.
How does OpenOffice use OOXML?
Did they reverse engineer it?
~Dan
Re: (Score:2)
Do you actually know anything at all about OOXML?
Re: (Score:2)
OOXML cant kill ODF, because ODF is open, and OOXML isnt.People who want to guarantee access to their documents in perpetuity (eg legitimate governments) cannot use OOXML because it cannot meet their needs. It is full of rabbit holes.
It may take a while for the smoke and mirrors to clear, but in the end, the truth will out.
I love the way Microsoft use the words "Office" and "Open" to try and fool people into thinking that OOXML is going to be an open standard.
If Microsoft wanted an Open standard as they want people to believe they would just contribute to ODF.
~Dan
Microsoft's own fault (Score:5, Insightful)
Re: (Score:2)
Even their OS X paying customers (MS Office is big deal) are having problem with "New XML thing". They must have wondered if the overpaying OS X users get that treatment, what would happen to their millions of open source machines?
I will really laugh if Icaza somehow gets this "ooxml reader" idea and channel through Novell
ODF is backed by more than just two (Score:3, Interesting)
Re: (Score:3, Insightful)
From the perspective of MS competitors, OOXML is an attempt to kill the document format that they have been investing in (ODF).
Is it? (Score:4, Insightful)
How do you figure that? Anyone implementing OOXML readers or writers still has to reverse-engineer Microsoft's applications. It doesn't make a lot of difference whether the undocumented proprietary code looks like "xmlns..." instead of "{\rtf..." or binary gibberish.
Microsoft just doesn't *understand* open standards (Score:5, Informative)
Recently I accidentally went to a short promotional Microsoft presentation (non-US) about OOXML for work. From the description about integrating with Office from a programmers' perspective, I'd thought it was going to be about writing Office addins, but it turned out to be a promotional-fest for OOXML in front of about 30 or so local software architechts for various companies and government organisations.
They started with a couple of locals without explaining what was coming -- one guy had built a Silverlight application that could parse basic OOXML Word documents and display them according to the OOXML specification. The other guy had written a web app that generated its own Office 2007 documents (Word and Excel) without having to rely on any third party or binary manipulation.
Then the local Microsoft CIO jumped up, having recently returned from Geneva, and started complaining about how there were really a small segment of people who had gripes with Microsoft and were refusing to work with Microsoft and trying to stop the standard going through for its own sake. They made a big thing about how the two people who'd just presented hadn't needed to read a complete 6000 page specification to do what they'd done, and he used the phrase "defacto standard" in virtually every sentence. They were preaching to the converted on this occasion, considering the room was full of people who were already big Microsoft customers, and really only wanted reassurance rather than to be convinced. I was tempted to ask if Microsoft ever had any plans to support the OASIS standard, but I didn't in the end.
I came away from that presentation with the impression that Microsoft as a company, and especially at the executive level, doesn't actually have a clear understanding of what an Open Standard is. The entire focus of Microsoft is that their Office suite is by far the most popular (for whatever reason), and therefore Microsoft should be the one to decide the standard. If someone else did that while Microsoft was looking the other way, then it must have been an accidental quirk that now needs to be corrected.
Perhaps there's some idea somewhere up in the ranks of leveraging their broken format in the future to reinforce their market dominance should there ever be a problem, but I think for most of them, they're just a bit pissed off or shocked that someone else has already defined a standard and is now trying to tell Microsoft that it can't do what it wants to do. After all, it's not "supposed" to work that way in their minds... Surely the "defacto standard" that's used everywhere should be the one that matters, right?
In their own minds, most of the Microsoft managers are quite certain that Microsoft would never abuse its position, or their already fundamentally of the belief that it's only fair that money should always change hands for these kinds of things, and that if Open Source apps can't find sources of funding then it's their own problem. (Money makes Microsoft go round, after all. It shouldn't be surprising for Microsoft employees to have those kinds of ethics.)
The frustrating addendum to this is that many businesses are in exactly the same mindset as Microsoft because money makes their business go around, too. If Microsoft starts using badly documented parts of their spec and charging for others to implement it, those people will quite happily either keep using Microsoft products, or pay for a product that costs extra as part of the necessity of paying the Microsoft tax. These people haven't even consciously dealt with concepts like standards definitions before, they don't appreciate how critically important it is to get it right, and they don't want to now. That's where Microsoft is getting its support from.
Re:Microsoft just doesn't *understand* open standa (Score:2)
I think you're right: ridiculous as it is, many Microsoft managers really think they are winning in the market through quality and innovation.
These people haven't even consciously dealt with concepts like standards definitions before, they don't appreciate how critically important it is to get it right, and they don't want to now.
But these people presumably also want various office suite relate
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
An interesting point is that, if Web based applications such as Google Docs start to take hold, I think you will find that there is a sudden reversal in the complexity of most documents. One of the things about both ODF and OOXML is that they define HUGELY complicated document formats. (ODF hides a lot of its complexity by referencing other standards. OOXML is just, well, ridiculously complicated, with four or five different ways to do any one action.) On the other hand, if you look at what you can do
Re: (Score:2)
Re: (Score:2)
That hasn't been a problem for any prior standard. Off the top of your head, can you name any other comparable standards (or any ISO standards at all?) for which that has been done?
Re: (Score:2)
Doesn't Solve the Fundamentals (Score:5, Insightful)
If IBM and others are as serious as people like Rob Weir seem to be then I strongly suggest they stop being chicken shits after the way in which they capitulated OS/2 in the face of Windows, start funding a really viable alternative to Windows and start really getting just what is required. This would be a desktop operating system that would circumvent the OEM channels Microsoft controls by being given away freely so that everybody, including OEMs, can install it free of Microsoft's control, and it will be a desktop good enough in terms of developers' tools and installation so software can get to users. With enough effort then you'd definitely carve out a market large enough to make it viable, and you'd then have an office suite with enough of an installed base. Governments and other organisations would then pick it up as a result.
Winging about OOXML isn't going to get anybody anywhere, sadly. It's only maintaining the status quo.
Re:Doesn't Solve the Fundamentals (Score:5, Insightful)
funding a really viable alternative to Windows
A viable alternative to Windows has to run popular Windows software. The problems are a) MS owns (or can buy) the most popular Windows software and can modify it to be incompatible with an alternative OS, or b) MS can push the next release of Windows before the alternative can gather momentum. This makes creating a viable Windows alternative a very risky, expensive, and exceptionally time sensitive gamble.
Which is why ODF scares the hell out of MS. ODF would make it much easier to develop an alternative to Office. As it stands, Office's price is pretty inelastic since there is no real competitor. We've been paying five dollar a gallon prices for Office for a long time now. ODF would make it possible for people to switch to a wallet friendly and just as effective Office alternative. And unlike Ma Bell, once the office productivity market is broken up, there won't be a way to put it back together again.
Once people no longer have to rely on the Microsoft Office software suite, their need to run Windows diminishes greatly. If Office falls, Windows OS falls, and MS goes from Kraken to being just another fish in the pond.
End result: you don't need to create an alternative Windows compatible OS. You just need to develop an Office alternative. Which is why MS is using every ethically challenged legal and business strategy to shut down ODF.
Even if MS stops ODF, if they keep pushing out underwhelming and much delayed Vista-like versions of Windows, or if MS cannot keep people on the software upgrade/subscription path, then they might really be vulnerable to an actual alternative Windows compatible OS (which at the moment is XP. Go figure.) Given that an operating system isn't useful in and of itself (applications make a computer useful,) it is a double hit to see MS having a great difficulty in coming up with and implementing must-have features or improvements to Windows. They're also scraping the bottom of the barrel in terms of Office improvements. It's becoming apparent that MS has has lost the agility needed to create and implement innovations in a cost and time-effective manner.
So until MS figures out how to compete by producing a quality product, it's going find itself in the same position that IBM did in the early 90s (where IBM almost went bankrupt.) It will be interesting to see if MS can pull an IBM and re-invent itself from a clumsy dinosaur into a fleet footed mammal.
Re: (Score:2)
Not necessarily. While I believe Ubuntu and others are making a mistake by ignoring WINE, and I think it would be a boon for many to be able to import a COM DLL into a Linux desktop environment and create a native front-end (the scary thing is, WINE might actually do a better job than successive versions of Windows), what we're talking about here is a snowball effect. The people who can use it now can pick it up, you make sure everything
Re:Doesn't Solve the Fundamentals (Score:5, Informative)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
This is a big win (Score:3, Interesting)
Re: (Score:3, Insightful)
Infosys, Wipro and TCS are in Microsoft pockets for long time. Of course, they don't want to lose their big projects with Microsoft. But that does not justify their support for OOXML.
Re: (Score:2)
Also, these are the IT services companies that live on offshored projects. Their clientèle is not exactly what you would call technical; sure banks, hospitals, etc. use technology, but they are not what you would call a technology organization. And these organizations are Microsoft shops too, so obviously NASSCOM & the other biggies don't want the burden of having to spend on upgrading their IT infrastructure to support ODF too.
Bad title - vote against is not news (Score:3, Insightful)
The only news here is (possibly) the insight the article gives as to why and how India has been and will be voting against OOXML, therefore the "India Votes Against OOXML" title is really stupid.
Re: (Score:2)
Duh? The vote in September was the initial Ballot, now this resolution is to not change the earlier vote as per the provisions provided by the BRM.
As per Wikipedia [wikipedia.org]:
They REALLY need to fix reparenting... (Score:2)
Parent is NOT a virus, BTW. It's actually a map of which countries voted what on OOXML.
Is all about the market. (Score:2)
IBM, Google, and many others have a vision on a ubiquity desktop, even Microsoft have this. But due the dominance of the desktop. This isn't able because the locking of the server and desktop for the collaboration and the portability to slimmed down applications. This doesn't work for IBM, Google and many others, so they're aligning to put ODF as an standard, because is a warrant for a bette
Re: (Score:2)
Yesterday, a cousin who is "thicker than two short planks" came round to visit. She had e-mailed her college work to us so she could use or Colour Laserjet 5 printer (which is 8 years old, and uses toner bought in pint bottles of e-bay for £6) because she and her husband
Here be lawyers (Score:2, Insightful)
Parent is a virus link (Score:5, Informative)
Please don't click it.
Re:Parent is a virus link (Score:5, Funny)
Not a troll, if you don't mind (Score:2, Interesting)
I call bullshit on the parent that suggests that Noooxml is a virus page. That should never have been modded up: it's an attempt to stop people finding out about what has been happening, and I'm prepared to waste karma pointing that out.
Evidence against noooxml:
Some random person says that it's a virus but doesn't provide any proof.
Evidence for nooxml being valid:
- It's linked from the front page of Groklaw - www.grokla.net. Currently item 2 in the
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Can someone with a better knowledge of XML can explain to me (I'm an infrastructure guy) why the OOXML 'standard' is 6000 pages? Surely a DTD defining a document format should be relatively simple - Doc Title goes here, body text here, format info here, etc.
I thought the whole point of XML is that it's effectively self documenting - simply publishing the XML DTD should suffice. I can't see how this should be more than 10's of pages. Am I being too simplistic?
ODF is actually defined using a Relax-NG schema, but that's admittedly a bit of nit-picking. :)
Defining structures for several different sorts of documents (which need to interoperate with one another) is a bit more complex than perhaps you make it out to be, but even so, such a spec does ultimately reduce to the sort of thing you're talking about.
In addition, "self-documenting" is a nice theory, but in practise, things do sometimes need to be explained - we expect C or Java code to be commented, and the s