Slashdot Mirror
Microsoft Wins Industry Standard Status for Office
everphilski writes "The International Herald-Tribune reports that Microsoft has won industry standard status for Office. EMCA International, a group of hardware and software makers based in Geneva, approved the MS file formats with only one dissenting vote - IBM. IBM backs the OpenDocument standard, which was approved by the ISO in May of this year." From the article: "Bob Sutor, IBM's vice president for open source and standards, called Microsoft's Office formats technically unwieldy - requiring software developers to absorb 6,000 pages of specifications, compared with 700 pages for OpenDocument. 'The practical effect is the only people who are going to be in a position to implement Microsoft's specifications are Microsoft,' Sutor said."
Wow, 6,000 pages to describe an "open" format? Never underestimate the power of committees.
Sutor, IBM's dissenting voter says: "The practical effect is the only people who are going to be in a position to implement Microsoft's specifications are Microsoft." This in the context that the OpenDocument (competing) standard is only 700 pages. Seems like both must be quite verbose, but I'd opt for mastering 700 pages.
6,000 is a lot of pages to master, but it should be freely available for others to interpret, correct? On the other hand, since it is "essence of Microsoft", there's probably lots to misstep with and lots to nuance for interpretation letting Microsoft essentially maintain a proprietary flavor of a supposedly open standard.
Also of note from the article:
Van den Beld might be an idiot. Using his logic we should strike Microsoft Windows XXXXX as the standard for OSes, not.Hopefully there is still some inertia for the OpenDocument (yes, I know it's an ISO Standard) standard to gain purchase and compete. It is largely the emergence and work done with OpenDocument that has pushed Microsoft into the uncomfortable arena of pretending to like open standards.
Does EMCA standardize anything other than MS apps? Before MS started using them, I'd never heard of them. My guess is its a mouthpiece for large companies who want a body to declare them a standard. At this point I'm ignoring anything from them- if you want to call it a stadard I want to see ANSI, ISO, IEEE, or IETF on it.
I still have more fans than freaks. WTF is wrong with you people?
IBM's vice president for open source and standards, called Microsoft's Office formats technically unwieldy - requiring software developers to absorb 6,000 pages of specifications, compared with 700 pages for OpenDocument.
This piece of information is of little use without comparing the supported *features* in both format and their implementation.
ECMA just confirmed the MS Open Office XML format as a standard, not Office in general. MS further states that OOXML will be an "open and royalty-free" specification.
What's also interesting is that MS will be offering a "bridge" (as a separate download) that enables Office software to read and write ODF (the OpenOffice Open Document Format) files.
Just junk food for thought...
I am not an expert on these bodies so can someone please explain the difference between EMCA International and ISO and how the approval from each organization differs.
Then WHY was it approved as a "standard"?
- Just my $0.02, take with a grain of salt, your mileage may vary.
Sure it can
.bmp?
buggy- well, it can't be buggy but it can be so complex that its hard to implement without bugs
bloated- a file format can easily store data in unefficient formats
insecure- hold important data without encryption
unreliable- hold the data in a lossy way
overpriced- Standards don't have to be free, they can charge a license fee (or even refuse to license on a RAND basis)
nonintuitive- Ever tried to decode all the variations of
clunky piece of dog shit- A hard to implement format is easily described as clunky
I still have more fans than freaks. WTF is wrong with you people?
It's ECMA. It even says that in the page you've linked to. And the original article. This Slashdot typo's infectious - it seems to have spread to half the comments posted already...
Tedious Bloggy Stuff - hooray?
Microsoft's spokesman countered the IBM executive's statement by pointing out,
"Actually the Open standard we propose is six thousand pages, but that's only because we printed it in 256 point boldface fonts in order to be handicapped accessible for the visually impaired, you insensitive clod."
Microsoft further countered allegations of being too hard for developers by pointing out,
"If you take away the title information, the table of contents, the index and the pages that say This Page Intentionally Left Blank, all the standards document says is 'Buy a copy of Microsoft Office'. What could be simpler than that?"
It's all well and good that OOXML is a published standard, but how long until Microsoft decides they need some enhancement and just add it without going through a revision to the ECMA standard? It's one thing to get something to become a standard, quite another to adhere to it. Think of how Netscape decided they wanted new HTML features but didn't want to wait for W3C and just dreamt up stuff like the blink and marquee tags. Once Microsoft Office diverges from the OOXML standard we're right back to where we started—a proprietary document format.
Microsoft as a company may decide product features mean more to them than adhering to a standard, even one they created. I'll never forget Microsoft's FORTRAN compiler under MS-DOS described by Microsoft as "a superset of a subset of FORTRAN 77." In other words, whatever they hell they felt like implementing.
I guess your standards for standards is higher than the standard industry standards standards used by standard Microsoft employees. In other words, "I've upped my standards, so up yours".
When our name is on the back of your car, we're behind you all the way!
Go take a look at it and judge for yourself. The open document formats are fairly reasonable XML-based structures (as "reasonable" as XML can ever be). MS Office XML abuses XML and is horrendously complex.
From a practical point of view, OpenDocument already works for interchanging between multiple open source apps.
In addition, Microsoft's file format is patented and Microsoft uses that patent to spread FUD. While the patent probably wouldn't stand, it's an additional reason not to use MS's office formats.
"The great thing about standards is that there are so many to chose from." --Attributed to Admiral Grace Hopper
Javascript + Nintendo DSi = DSiCade
They could have avoided sucking by just using Open Document instead of inventing their own pseudo-open format. Why reinvent the wheel?
How about this one:
n tlicense.asp.
p x. Is it the same? different license? Bad links happen to everyone.
No right to create modifications or derivatives of this Specification is granted herein.
There is a separate patent license available to parties interested in implementing software programs that can read and write files that conform to the Specification. This patent license is available at this location: http://www.microsoft.com/mscorp/ip/format/xmlpate
The link with the actual license to READ and WRITE a file to their specifications is dead. This one works though, http://www.microsoft.com/whdc/xps/xpspatentlic.ms
Some handy excerpts: "Necessary Claims" do not include any claims: (i) that would require a payment of royalties by Microsoft to unaffiliated third parties; (ii) covering any Enabling Technologies that may be necessary to make or use any product incorporating a Licensed Implementation,....
This says to me that they have not indemnified developers from patent time-bombs for the functions one step beyond their proposed standard or other patent time-bombs laid by lesser-known Patent IP firms. Maybe someone with more coding skills can explain if it would be possible to implement a standard without so-called "Enabling Technologies"?
(iii) covering the reading or writing of documents other than XPS Documents, or rendering of XPS Documents in a manner that is different than the rendering allowed by the XML Paper Specification. "Enabling Technologies" means technologies that may be necessary to make or use any product or portion of a product that complies with the XML Paper Specification, but are not expressly set forth"
To me this says Microsoft can come after you if you do something they didn't think of.
I don't see how this benefits any developer outside of a select few.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
That's a very valid point, I don't see what makes it a "flame".
I am also pro-open and have my own irks with Microsoft. And I do use OpenOffice.org when I can.
But like it or not, MS Office is still in the lead as far as being intuitive and functional. OO is close, but certain parts of it still fall short of MS Office. Microsoft has been developing and refining this stuff for a long time, and it is by far used by more people (and businesses) than any other office software suite.
Plus, it works. Sure, MS Office has its flaws, but let's face it: So does OpenOffice. This doesn't change the fact that it's the most widely used, and as such would be a reasonable candidate for becoming an industry standard.
(Of course, I use 'industry standard' loosely since different groups seem to declare different standards for document formats...)
Since it's apparently grounds for automatic down-modding to express a valid opinion in favor of Microsoft on Slashdot, you people can 'troll' or 'flamebait' me all you like. Doesn't make my point any more or less reasonable.
/* No Comment */
While I'm inclined to a cynical view that Microsoft is unnecessarily burdening the specification - and they probably don't mind the fact that this will impede the development of competitors products - I do have to admit the possibility that they are addressing a different criticism that many have made of them in the past.
Namely, that Microsoft specifications are incomplete and/or imprecise (corner cases, etc.).
Albeit verbose, is their specification technically watertight?
Or is it merely, "Here's everything Word can do as a result of development since 1985." with no overall logical structure?
"Provided by the management for your protection."
How long until Microsoft embraces and extends its own standard? This is simply an old Microsoft trick with a new twist. As soon as Microsoft documents break compatibility with ECMA OOXML, then every other third party software will lose the ability to read and write compatible documents. Worse than the current situation, because an attempt to maintain compatibility with Microsoft Office might violate the conditions of the OOXML license. And no doubt break the format they will, in subtle ways of course, a little bit off here and there just enough to make a document look much better in Microsoft Office than it will in other applications.
The Microsoft license to use ECMA OOXML is contingent on following the standard to the letter, which is a seemingly innocuous condition until you realize that Microsoft itself is under no legal obligation to follow the standard to the letter. So you will have a bunch of third party software that follows the standard which won't be able to accurately read or write documents written by the dominant office software, it will just look like the other software is defective when really it is working according to the standard. And even if the other software developers want to break the standard in favor of microsoft compatibility, they won't be allowed to do so under the OOXML license. Microsoft wouldn't do this at first of course, what good is a trap sprung before your prey are fully in, so I am sure that Microsoft would spend a year or two adhering rigorously to the standard, just enough time for other software to incorporate OOXML compatibility. Then it would be time to break compatibility and continue the microsoft monopoly for another few years, while things work their way through the courts.
If Microsoft itself makes a legally binding and enforceable commitment to follow the ECMA OOXML standard to the letter, then I don't see a problem with another document format standard. But as the licensor, I don't see how they could be forced to adhere to the OOXML standard. Unless Microsoft itself can be forced to rigorously follow the OOXML standard, then this is just a monopolist's trap.
FOSS should avoid "Open" XML because Microsoft has encumbered it. Their game is now on. Offer code and protocols that they claim is "open" but, when push comes to shove, they alone control.
Down the road a bit they will begin strategic law suits and try to make FOSS programmers look like a bunch of thieves for implementing the "open standards" they pushed through without paying royalties.
Microsoft is not even a bit interested in competing on a level playing field. For a very long time they have used their monopolies to gain unfair advantages; antitrust laws be damned. Now they want to use their monopoly muscle in their Office package to control a "standard" that they feel will lock out their greatest competition. They know that GPL'd software CAN NOT be encumbered by patents.
They have no intention of real cooperation.
The solution: EVERYONE must work to make them irrelevant. Put them into a position where they either start playing fair or die. Not an easy task. We must press our Justice department to hold them accountable for breaking antitrust laws. The Courts MUST break Microsoft into a least three separate companies. This can easily be justified by their continued disregard for the law.
We should only support protocols and "standards" that are truly free. No unacceptable licenses, no royalties etc. As Linux gains market share there will come a time when Microsoft's insistence on being incompatible with OSS will begin to work against them.
We should push for laws that force standards and protocols to be truly open and available to everyone including Open Source.
The race isn't always to the swift... but that's the way to bet!
Let me tell you how simple ODF is. I did the following with ZERO documentation. No knowledge at all.
.zip file, opened content.xml and found the xml for what I had put in the test doc. I then wrote a Java program that would parse the CSV and output xml that looked like the xml in the file. Cut and past the generated xml into the document, drop the photos in the pictures directory, and then zip it back up and change the name back. It just worked.
I implemented a photo directory for my church congregation. Since it would need to be easily updated I kept the information in a CSV spreadsheet, including names, addresses, and the name of the photo file. I looked at doing a mail merge with either OOo or Word and it didn't look like I could get what I really wanted with either. So I made a sample doc in OOo Writer and saved it. I then renamed it to a
I'll admit that you would have to be a programmer to do something like that, but it was really easy and required no documentation or specialized knowledge. That is the power of the ODF. I'm guessing the same isn't possible with the MS format.
Lasers Controlled Games!