Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Software Microsoft

Jeremy Allison On Microsoft, OOXML and Standards 102

An anonymous reader writes "OOXML is already Microsoft's "de facto" standard as implemented in Office 2007, so when would any changes arising from the Comments Resolution meeting in February 2008 be put in place? According to Jeremy Allison's latest column, when last minute changes were suggested for the CIFS standard, which Samba exists to disentangle, "the response came back from Microsoft that although the fixes were valid, unfortunately the code was already written and was going to be shipped in the next service pack. End of discussion. It wasn't even in a shipping product yet, but the specification was determined to be unchangeable as they didn't want to change their existing code.""
This discussion has been archived. No new comments can be posted.

Jeremy Allison On Microsoft, OOXML and Standards

Comments Filter:
  • by betterunixthanunix ( 980855 ) on Saturday September 15, 2007 @08:10AM (#20615395)
    "Today, ninety-two percent of desktops and now seventy percent of servers run the completely proprietary and non-standardized Microsoft Windows operating system." 70% of servers are running Windows? What year is this? Have I been in some kind of coma?
    • by shutdown -p now ( 807394 ) on Saturday September 15, 2007 @08:19AM (#20615443) Journal
      If you count not just web servers, but e.g. intranet Exchange servers and AD controllers, 70% sounds plausible.
      • by Anonymous Coward on Saturday September 15, 2007 @09:05AM (#20615695)
        The number of servers metric is close to useless anyway. We have nearly 500 exchange servers plus another 200 domain controllers (100k employees worldwide) and only one Linux machine... However, the Linux system is on three of the most expensive pieces of hardware you can even imagine, backed up by an immense SAN, and serves apps and data to every user in the company concurrently.
        • Two ways? (Score:2, Interesting)

          by WED Fan ( 911325 )

          So, if the metric shows Linux gaining ground its valid, but if the metric shows Windows dominating, the numbers are suspect? And we can find all sorts of explanations?

          This is like the metrics for the Anthro Global Warming crowd. Any study that suggest geo, solar, and other causes is dismissed. Any bad math is dismissed.

          Yes, MS is dominating and not really losing ground. Downloads of Linux are up, but that does not indicate use, it indicates curiousity. Everytime there is a significant release by any of th

          • Re: (Score:1, Troll)

            by WED Fan ( 911325 )

            So, if the metric shows Linux gaining ground its valid, but if the metric shows Windows dominating, the numbers are suspect? And we can find all sorts of explanations?
            This is like the metrics for the Anthro Global Warming crowd. Any study that suggest geo, solar, and other causes is dismissed. Any bad math is dismissed.
            Yes, MS is dominating and not really losing ground. Downloads of Linux are up, but that does not indicate use, it indicates curiousity. Everytime there is a significant release by any of th

            • I think what the previous poster was getting to is that the metrics aren't accurate reflections. It the AD or Exchange servers do one thing each and the linux box can replace 5 of them each, then wouldn't one linux server need to be counted as 5 AD and Exchange servers?

              It isn't that he is dismissing what he doesn't agree with. It is that he thinks the linux servers are under reported because the role they take on actually replaces several windows servers. So it isn't the metrics, it is the value of the metr
          • Re: (Score:3, Insightful)

            The point the poster was trying to make was that simply counting the number of physical servers in use is not an accurate measurement. His point was that there is more to it than physical servers; a single server could potentially be supporting thousands of users in an organization. There is also the question of, for a given hardware platform, how many users can be supported by one server system vs. another (Linux usually wins on this one, since the kernel has been tweaked to create processes very fast, e
        • by o517375 ( 314601 )
          The number matters to MS which has you exactly where it wants you -- forking over lots of $$s
        • Yeah its fubar.

          Windows servers need larger clusters so if one BSOD's then it will have minimal impact. ;)
      • by Anonymous Coward on Saturday September 15, 2007 @09:32AM (#20615873)
        Don't forget bot-nets... Those are servers too.
      • If you count not just web servers, but e.g. intranet Exchange servers and AD controllers, 70% sounds plausible.
        Problem is that comparing server to server is like comparing oranges to apples. Its the amount of juice they provide that counts.
        Yeah 70% of servers might be, but most of them support the 93% desktop infrastructure ONLY.
        While Unix'es are usually there for processing, service delivery and other higher value non-infrastructure services.
    • by Anonymous Coward
      The article is in an Indian-based web site. As odd as it may seem, Microsoft is the clear leader over there. You'd think that expensive, proprietary software wouldn't be used much in a nation where so many suffer from from extreme poverty, even to the point of starvation. One would expect Linux and OSS to be widely used.

      However, many of the universities and technical institutes to use only Microsoft products. So you end up with these Indian schools generating many thousands of graduates each year who only k
    • Netcraft says 34%. But that doesn't count all the back office file servers, exchange servers, ms sql, citrix, etc.
    • maybe most of those 92% of desktops are also counted as servers for spam and bot networks.
  • by xlyz ( 695304 ) on Saturday September 15, 2007 @08:10AM (#20615397) Journal
    if they don't change it, then don't approve it as standard
    • by QuietLagoon ( 813062 ) on Saturday September 15, 2007 @08:36AM (#20615547)
      if they don't change it, then don't approve it as standard

      The problem is that Microsoft (in an implicit admission that its software is sub-standard) is using the profits from its cash-generating Windows monopoly to buy votes in favor of its submission.

      In other words, to paraphrase Ballmer, Microsoft could submit a ham and cheese sandwich for ratifcation, and it would be approved.

      • by m2943 ( 1140797 ) on Saturday September 15, 2007 @10:23AM (#20616269)
        In other words, to paraphrase Ballmer, Microsoft could submit a ham and cheese sandwich for ratifcation, and it would be approved.

        That sounds like a much better standard than OOXML, and it's much easier to implement for everybody. And if Microsoft tries to sneak bits of a 10 year old ham and cheese sandwich in there, like they did with OOXML, people will know the second they bite into it.
        • Re: (Score:3, Funny)

          by Anonymous Coward
          > easier to implement for everybody

          No. The standard would say:

          To make an ISO standard Ham and Cheese Sandwich, make it like Bill Gate's mother used to.

        • by gowen ( 141411 )
          The ham sandwich standardisation process was abandoned after repeated disagreements between the French and English over the definition of 'mustard'.
      • Re: (Score:2, Insightful)

        by DogDude ( 805747 )
        Wrong. This has nothing to do with buying votes from the ISO. This has everything to do with standards bodies being ignored because they're irrelevant. Remember the W3C? Yeah, they still exist, but who in their right mind pays attention to them? Why would anybody? They pick arbitrary standards that they think are good ideas, but if nobody actually uses those standards, what's the point? That's what a de-facto standard is. It's a standard that comes about through everyday use, not some arbitrary orga
        • by jack455 ( 748443 )

          Remember the W3C? Yeah, they still exist, but who in their right mind pays attention to them?
          Me for one

          Oh yeah and all the browsers that support css. And some features of css2 css3 etc.
        • This has nothing to do with buying votes from the ISO. This has everything to do with standards bodies being ignored because they're irrelevant.

          If the ISO standards process is so irrelevant, then why is Microsoft buying votes to get their mediocre software approved?

          • by DogDude ( 805747 )
            Why? Because it was so cheap to do, why wouldn't they cover all of their bases? It certainly doesn't hurt to have the backing of the ISO. MS supposedly spent $50K on that. Hell, that's ridiculously cheap. Just for the potentially good PR, I'm sure they wouldn't have paid more than ten times that.
    • if they don't change it, then don't approve it as standard
      That's not how it works. ISO standards are not "designed by committee" (yes, it's pejorative) but they're submitted by companies and institutions. You don't need to listen to every single project, company or institution that disagrees with your decisions, you only need to follow a simple set of rules while developing the spec on your own.

      The ISO process doesn't works like the W3C process.
  • by GreatBunzinni ( 642500 ) on Saturday September 15, 2007 @08:10AM (#20615399)
    Correct me if I'm wrong but isn't it that in order for a file format to be accepted as an ISO standard there has to be at least a couple of independent working implementations? If Microsoft's OOXML is amended but the only piece of software which implements OOXML doesn't even follow the standard presented to ISO, where does that leave the OOXML's standardization?
    • by jkrise ( 535370 ) on Saturday September 15, 2007 @09:03AM (#20615679) Journal
      isn't it that in order for a file format to be accepted as an ISO standard there has to be at least a couple of independent working implementations?

      Actually I thought so too myself, but apparently this is forbidden by the ISO! However the spec itself must be complete, self-contained and authoritative... this bit I am quoting from a related link from a Groklaw article, in the comments section of Mr. Alex Brown's blog:
      http://www.adjb.net/comments.php?y=07&m=09&entry=entry070909-104641 [adjb.net]
      and the Groklaw article is here:
      http://www.groklaw.net/article.php?story=20070910110639612 [groklaw.net]

      The relevant answer:

      ISO rules forbid reference implementations. The thinking is that the text must itself by complete, self-contained, and authoritative; a reference implementation opens the possibility of deviation from the text, thereby creating uncertainty about which is "right".

      That said, in SC34, we follow the practice of informally requiring that our "home-grown" standards (RELAX NG, NVDL, Schematron etc) are proved efficiently implementable during standardisation. If my time wasn't so taken up with DIS 29500 I would be working on an implementation of DTLL in Java to accompany the draft standard, for example!
      • Requiring implementations is different from requiring "reference implementations". Since their network standard, ISO changed its procedures to encourage people to ask for functional implementations (from different vendors) of the standards they create.

        But a reference implementation is "do it like Office 2007". ISO doesn't accept that, the specification should be on a document, not a software.

    • by arivanov ( 12034 )
      Exactly where it belongs - nowhere. Hence the best thing which can happen now is to vote through at least a couple of amendments.
    • by legirons ( 809082 ) on Saturday September 15, 2007 @09:43AM (#20615949)
      "Correct me if I'm wrong but isn't it that in order for a file format to be accepted as an ISO standard there has to be at least a couple of independent working implementations?"

      It's RFCs [wikipedia.org] and Internet Standards which need to have multiple implementations. See RFC 2026 [faqs.org] for the meta-standard (explanation of what standards an RFC needs to meet)

      Internet standards are also required have been tested in real-world scenarios for long periods, plus they should be as simple as possible to implement, plus all discussion needs to be in public, which might explain their popularity compared to ISO computing standards.

      Interestingly, if there's a patent needed in an RFC, then the two reference implmentations even need to have used "separate exercises of the licensing process"

    • by ntrfug ( 147745 )
      That's for Internet standards.

      See 4.1.2 "Draft Standards" of RFC 2026 "Internet Standards Process".
    • Correct me if I'm wrong but isn't it that in order for a file format to be accepted as an ISO standard there has to be at least a couple of independent working implementations? If Microsoft's OOXML is amended but the only piece of software which implements OOXML doesn't even follow the standard presented to ISO, where does that leave the OOXML's standardization?

      Personally, I think they need to go one step further beyond just 'documenting the standard' and demand that the standard and all reliant technolog

    • Correct me if I'm wrong but isn't it that in order for a file format to be accepted as an ISO standard there has to be at least a couple of independent working implementations?

      I think you're confusing the ISO process with the IETF Standards Process [ietf.org].

  • by Richard W.M. Jones ( 591125 ) <rich@anne[ ].org ['xia' in gap]> on Saturday September 15, 2007 @08:17AM (#20615425) Homepage

    Presumably that would mean that Microsoft couldn't legitimately claim that Office 2007 followed an ISO standard, which is the whole point of this exercise?

    Well, I guess it wouldn't stop them from trying, or at least issuing confusing public statements on the subject.

    Rich.

    • Re: (Score:1, Insightful)

      by Anonymous Coward
      No, the point of the excersize was the extra positive spin in the early phases of the Office 2007 product life cycle.
      "we submitted our new file format for ISO standard certification" is just an extra bullet point in their presentations to convince the, generally conservative, decision makers that switching to a new file format might actually be a good idea. It suggests vendor independance, easily accesible data etc.

      Of course when the new file format has taken over a significant portion of the market there c
      • Re: (Score:3, Informative)

        by Locutus ( 9039 )
        That is correct and the state of Massachusetts has already caved on ODF and allowed MS OOXML as an "acceptable" open standard.

        It blows me away how ignorant people are about Microsofts motives after over 15 years of anti-competitive business practices/methods. But then again, someone voted for Bush in 2004 even after no WMD's were found and most of them believed Iraq was tied to the 9/11 attacks... Boy does the US education system suck. IMO.

        LoB
        • by Pecisk ( 688001 )
          Education system doesn't learn human to try to understand the world around him and don't take everything and everyone says for granted (aka critical thinking). It is parents job, not teachers, actually.

          IMHO, problem is such circle. Parents are tired and overworked and can't educate their children about how to live in this world. Such children are very frequently ends up learning good simple things aka facts, but without big insight about world. They usually tend to see that their parents don't have time bec
  • Money Quote (Score:5, Interesting)

    by Mateo_LeFou ( 859634 ) on Saturday September 15, 2007 @08:17AM (#20615431) Homepage
    "My own favorites were Cuba voting "yes" to the fast-tracking of OOXML, even though Microsoft is prohibited by the US Government from selling any software on the island that might even be able to read and write the new format, and Azerbaijan's "yes" vote, even though OOXML as defined isn't able to express a Web URL address in Azeri, their official language."
    • Re: (Score:3, Interesting)

      by jonwil ( 467024 )
      And if Microsoft paid bribes to the Cubans to get their vote, doesn't that mean Microsoft is in violation of the export embargo (which makes it illegal for Americans or American companies to give money to Cuba)
      • by tacocat ( 527354 )

        Microsoft has been found guilty of many things. But how many of them have they actually been sentenced on? And of those, how many times was the sentence actually carried out?

        There's a lot of legal wranglings when it comes to the definition of Right and Wrong when it comes to that Corporation.

      • by gowen ( 141411 )
        Nah, this is just evidence of Castro trying to sabotage US capitalism again.
        He's a crafty little bugger, you know.
      • And if Microsoft paid bribes to the Cubans to get their vote, doesn't that mean Microsoft is in violation of the export embargo (which makes it illegal for Americans or American companies to give money to Cuba)

        Yeah... Right... and they are the only ones that are dealing with Cuba!?!?!?!?
        It's the people and small enterprises that are banned to deal with them, big enterprises are free to do whatever they want. Since they are actually in control of US.(In Russia the government controls the commerce... work out who controls who in US)
        History note: IBM had business in USSR during the war in Afghanistan. Witch I am pretty sure was not allowed by US government.

    • Obvious answer: Cuba know it's crap, and want the US to have to deal with it. They don't care, they're effectively immune to it.
  • by BasilBrush ( 643681 ) on Saturday September 15, 2007 @08:19AM (#20615439)
    If this is supposed to be a standard, supposedly in the hands of a standards body, then why would it need Microsoft's permission to change the things that are broken in it. The standards body should change the spec to fix some of the worst deficiencies highlighted by the comments. And then if Microsoft doesn't change their code match, then point out that Microsoft's implementation is in breach of the standard.
    • by nine-times ( 778537 ) <nine.times@gmail.com> on Saturday September 15, 2007 @08:24AM (#20615473) Homepage
      Why should the standards body bother to try to fix Microsoft's broken spec at all? Why not just reject it, and say, "Sorry, Microsoft, but here's a list of things you have to fix before we'll look at it again."
      • by Locutus ( 9039 ) on Saturday September 15, 2007 @11:13AM (#20616677)
        yes, there is a problem here isn't there? For one, an open spec is usually accepted and governed by an industry organization. So ISO, after years of working with industry partners on ODF, maintains the ODF formats/specs. But the Microsoft spec, well that is and EMCA spec and ECMA allows proprietary IP in their spec and allows the charging of licensing fees. Also, MS OOXML was created be and is controlled by Microsoft. They effectively purchased their way into the ECMA standards process with their sole ownership of the product. It was intended that they would use a special "fast-track" mechanism the ECMA and ISO have, and use it to quickly sidetrack much of the public forums an ISO spec goes through.

        But back to the point of who manages an open spec. So ISO has a spec they are managing and it's called ODF. Now, Microsoft wants them to also spend their time/efforts on the MS OOXML spec and it would be ISO's job to maintain both specs. The thing to realize here is that never has Microsoft intended to do this for open access to their file formats. This whole thing has been devised as a scheme to block acceptance of ODF and is a reaction to ODF. Remember, ODF took years to get through the process. Not to mention that Microsoft has been fooling the public+dog with it's open XML talk for over 10 years now. It is all bull shit. It is Microsoft. Need I say more?

        LoB
         
        • Yeah, I know. But my point is that Microsoft brings what is essentially not an open spec to ISO and says, "Endorse this as an open spec." Why shouldn't ISO simply refuse until the spec is made reasonable and implementable?
          • Re: (Score:3, Insightful)

            by Locutus ( 9039 )
            the ECMA brought it to ISO via the existing Fast-Track mechanisms already in place. ISO is following it's rules in how it handles the Fast-Track process with ECMA. The fact that Microsoft picked through the process and found and is exploiting holes in it are all part of the way Microsoft does "business".

            So the ISO is following the rules of the organization with regard to this. Unfortunately, that's all it is doing. Even after it has seen how the rules are being manipulated to further push a very bad specifi
    • by khasim ( 1285 ) <brandioch.conner@gmail.com> on Saturday September 15, 2007 @09:27AM (#20615841)
      If OOXML is accepted as an ISO standard then Microsoft's implementation of that "standard" will be the "de facto" standard implementation of it. Not exactly a "reference implementation" but effectively accepted as such.

      Even if Microsoft's implementation doesn't follow any of the published "standard".

      Just as IE was the "standard" when you were designing a web page. Sure, you could follow the official WWW standards, but if IE couldn't render it, it was considered "broken" by the general public.
    • by omz ( 834760 )

      If this is supposed to be a standard, supposedly in the hands of a standards body, then why would it need Microsoft's permission to change the things that are broken in it. The standards body should change the spec to fix some of the worst deficiencies highlighted by the comments

      It seems that you forget that this fast-track is taking place in Wonderland [itn.liu.se]

  • Why would MSFT fix a security hole? They never bothered about security holes. The fix proposed by Samba would work both in MSFT solution and the open source solution. That is a definite no-no.

    MSFT will take a while to come up with a fix to that security hole that is covered by some patent or something. That way only the MSFT implementation would be free of that hole while samba team would be handicapped. I am tempted to say MSFT intentionally created the hole in protocol, but they it is not likely. Secur

  • by 3seas ( 184403 ) on Saturday September 15, 2007 @08:48AM (#20615611) Homepage Journal
    ....the sooner people will stop using MS products.

    And that is even more blunt, to the point, that anything coming out of MS's mouth.

    I'd strongly promote switching to Linux at work if only the applications I use had realistic alternatives on Linux.

    Namely Autocad, Illustrator, a cad/cam package with non-buggy cnc post processors that would plug into a linux version of autocad,....

    And what ever the alternatives are, they have to be file compatable as we have a large store of cad drawings to deal with.

    There are other programs as well, like filemaker and the resources we have built up in that, etc..

    Its not just a matter of finding a similar program but one that have realistic support for existing files and resources.

    I have no doubt that many more would change away from Windows if such a realistic change was possible.

    Whether or not MS knows this...... or have they become so arrogant to be stupid?

    Stupid seems to be the direction that have been taking....
    • by Anonymous Coward
      "Whether or not MS knows this...... or have they become so arrogant to be stupid?"

      What does a file format in Office 2007 have to do with apps for Linux? Microsoft isn't going to write them. Mainstream companies aren't either. Your feelings towards Microsoft notwithstanding. What incentive does the commercial industry have to support yet ANOTHER operating system? Especially considering even Macs have trouble getting the apps they want, and the argument is even stronger there in moving to that platform instea
    • OT: CAD, etc. (Score:1, Interesting)

      by Anonymous Coward
      I don't know why you're getting positive mod points, as you've drifted off topic. However, I'd like to take issue with some points raised.

      Namely Autocad, Illustrator, a cad/cam package with non-buggy cnc post processors that would plug into a linux version of autocad,....

      AutoCAD, while almost ubiquitous, is rather limited design software. There are many alternatives on Linux, some of which are listed on Wikipedia [wikipedia.org], including the proprietary/commercial application Pro/E. (F/OSS have some way to go, but Ope

    • Have you take a look at these products?

      http://www.varicad.com/ [varicad.com]VariCAD - supports DWG files via the http://opendesign.com/ [opendesign.com]"Open Design Alliance"

      http://fastcad.com/ [fastcad.com] fastcad - Created by none other than the original developer of AutoCAD, Mike Riddle. Apparently version 8 will run on Linux

      note: I have only researched these products because I want to start a Linux solutions company. I have not used them myself (yet). Also IANAE (I am not an engineer)
  • by jkrise ( 535370 ) on Saturday September 15, 2007 @08:54AM (#20615637) Journal
    I think Microsoft and even Slashdot must replace the FAQ section with a RAQ section, where questions of the "Emperor's New Clothes" type can be asked and answered. This bit in the original article is very thoughtful, and one I've been asking myself:

    "...after analysis by some of the experts on the list we discovered that there were some theoretical holes to the new signing protocol, which needed a few trivial changes in order to fix and improve the security. After these proposals were submitted, the response came back from Microsoft that although the fixes were valid, unfortunately the code was already written and was going to be shipped in the next service pack. End of discussion. It wasn't even in a shipping product yet, but the specification was determined to be unchangeable as they didn't want to change their existing code...."
    I think Mr. Jeremy Allison and Microsoft have different views on security. Any layman would think that security means 'of the product' or 'of the user'... but Microsoft seems to think about its own financial security; which in turn seems to be based on the INSECURITY of its products, services and service packs!

    Microsoft has laboured hard to create an impression that a 'secure' system is one that needs daily patching, and must be 'closed' and 'proprietary'. Allison & co. KNOW FULLY WELL that an open, documented and properly implemented system provides true security.

    The recent unwarranted update of Windws Update is a case in point. Users who would trust only themselves, and who use Windows only to run their applications, would not like to destabilise their environments by introducing new untested undocumented additions. If it works, they reason, no need to touch it.

    In Microsoft's view, their present proprietary document formats have been an enormous cash cow, they will not break that by opening up the formats and inviting needless competition. Which is why, even if the OOXML spec undergoes lots of changes and lengthy explanations; there will not be a single faithful implementation. Including in Office 2007.

    Can someone ask this "Rarely Asked Question" to responsible folks at Redmond, and see how they respond?
  • by Prototerm ( 762512 ) on Saturday September 15, 2007 @08:58AM (#20615655)
    Once again, Microsoft proves there's no such thing as doing it right the first time.
    Or the second (Service Pack 1).
    *Maybe* the third (Service Pack 2), but don't count on it. If you recall, Microsoft released the first version of NT as version 3.1 in an effort to combat this effect. And after they slip-stream the new OOXML changes into Office 2007, obsoleting old documents, sheeple will groan and moan, but they'll still drink the Kool-aide.

    (Sigh!) Sometimes, I wonder why FLOSS even bothers.
  • what a mess IT is! (Score:2, Insightful)

    by FudRucker ( 866063 )
    i sincerely believe the computer industry is a mess, no private corporation or company should be able to dictate an ISO standard, i believe open file formats & open networking protocols should be mandatory for anything & everything that is distributed between different computers anything less is perpetuating a crime allowing a corporation to maintain vendor lock in & a monopoly for $profit$...
    • by erroneus ( 253617 ) on Saturday September 15, 2007 @09:45AM (#20615965) Homepage
      Long ago, anyone could claim to be a doctor... eventually the government and other bodies stepped in and started requiring standards. Not so long ago, the same thing happened to dentistry. Similar things happened to architects, electricians, plumbers and many other professions that shape the quality of life, existence and industry in the modern world. Oddly, we have yet to establish such standards in software and information technology and yet it is precisely software and information technology that virtually every aspect of life in the modern world heavily depend on.

      There have been many disasters caused by bad code, bugs or other glitches in systems and yet for some reason it's more important that development costs are saved by using crappy programmers with crappy programming practices. Thousands of people will have to suffer and die before things will change I guess... that's what it took for all those listed above.
      • That is why we have a professional engineer's organization. (Which I am a member) But nobody outside of the military seems to demand source code and software design be treated as sealed construction drawings. There also is a professional association for IT professionals, but I don't think they have any legal teeth. http://www.cips.ca/ [www.cips.ca]
        • Reducing software to a commodity product along the same lines as music, movies or books is largely to blame you know... what company or companies do we suspect had started that "revolution?"
  • If Microsoft fixes the OOXML specification and it becomes a standard, then Microsoft Office won't even be compatible with Microsoft's own standard. Color me not surprised.
  • by Locutus ( 9039 ) on Saturday September 15, 2007 @10:47AM (#20616437)
    don't fool yourself, Microsoft has no intention of letting other compete and/or have open access to its application file formats. Microsoft Office generates over 30% of Microsoft's profits, yes profits, and they will not give that up.

    All this stuff about openness is about keeping Open Office and its ODF fileformat from being chosen as a government standard.

    So don't kid yourself an believe there is any other motive or that they would consider implementing those comments to clean up the spec. Hey, there's nothing in their history to suggest they want to compete in this sector. They own it now, it's worth billions in profit annually, and they will not give it up. So let's stop fooling ourselves into thinking it is anything else.

    LoB
    • Actually they don't have to give it up. But to keep it they HAVE to put more effort into it. Because in their monopoly situation they just have to sit still and enjoy.
      I believe that MS is not too bad on the tech side, but the business side is plain EVIL and OMG "think of the children"!
      They could produce an office suite that is ODF and could be really competitive, but that would COST them now. And the cost would be somewhat financial, but mostly in confidence of profits. But they are NOW overconfident.
  • Ship Dates (Score:3, Interesting)

    by ClubStew ( 113954 ) on Saturday September 15, 2007 @10:52AM (#20616483) Homepage

    That's how software in the commercial world works. Software has to ship, and changing code at the last second means complete test runs which both pushes the schedules back as well as costing and organization a lot. Releasing patches is an expensive ordeal as well. It's not like you just can put up a .patch file and expect everyone to download, integrate it, and re-compile their app.

    Of course a company isn't going to change their software at the last second. Just because something hasn't shipped yet doesn't mean it isn't done.

    • by Shatrat ( 855151 )

      Just because something hasn't shipped yet doesn't mean it isn't done.
      C'mon this is microsoft, even when it does ship it isn't done.
      This is the least compelling excuse for why they arent improving the spec and implementation of OOXML I have heard.
  • If they approve the OOXML spec with request to change it, or deny it standardization altogether, MS doesn't really need to care. This entire exercise is a bone thrown at the market. MS may be trying to placate the government entities and business partners that are tired of Office vOld.1 no longer working in their archives, but MS hasn't lost share of the desktop office productivity market because of their proprietary formats. Just like IE, they can shove OOXML down our throats anyway.

    I hate to a
  • by WhiteWolf666 ( 145211 ) <[sherwin] [at] [amiran.us]> on Saturday September 15, 2007 @01:03PM (#20617527) Homepage Journal
    Microsoft should not be designing standard.

    MS submits a standard expecting it to get fasttracked. MS bribes decision makers to make this so.

    The the standards committee comes back and says, "we need these changes", MS says, "Too late. We've shipped. Take it or leave it."

    This is not good behavior.
  • I work for a national standards organisation.

    One of our suppliers has a large infrastructure application. We are defining standards for communication.

    We wrote the standard in the best way possible according to our parent standards body, which provides a meta-standard which should make messages comprehensible even if you haven't read the standard. Our supplier pouted, sulked, whined, and eventually we were forced from above to rewrite them to comply as closely as possible with the existing API, which contain
  • I have been following this lateest tatic of M$ to FUD the ISO, and I never heard this aspect of their unwillingness to follow their own standards, and of course, ship the clothes anyway.

    I am going to let users know, and have them bail out of Office 2007 by the thousands.

  • by Big Nothing ( 229456 ) <tord.stromdal@gmail.com> on Sunday September 16, 2007 @08:44AM (#20624993)
    Ironically, when reading this article it is accompanied by a Microsoft ad proclaiming "Defy all challenges". A fitting motto, I suppose.

If all else fails, lower your standards.

Working...