Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Microsoft Software Linux

Microsoft Pledges Conditional Support for ODF 241

Macthorpe writes "BetaNews is reporting that Microsoft has announced in a letter that they will support ODF as a format option, if it doesn't 'restrict choice among formats'. Citing their lack of opposition to the ratification of ODF as a standard, they go on to say: 'ODF's design may make it attractive to those users that are interested in a particular level of functionality in their productivity suite or developers who want to work that format. Open XML may be more attractive to those who want richer functionality [...] This is not to say that one is better than the other — just that they meet different needs in the marketplace.'"
This discussion has been archived. No new comments can be posted.

Microsoft Pledges Conditional Support for ODF

Comments Filter:
  • Format (Score:4, Funny)

    by freemywrld ( 821105 ) on Tuesday July 17, 2007 @09:53AM (#19886785) Homepage
    A format richer.... with bugs!
    • Re: (Score:3, Insightful)

      by mwvdlee ( 775178 )
      Personally, I'm well beyond the stage where I require my documents to have headers in tacky word-art and atleast 5 different fonts in 9 different colors for the body, surrounded by a border of ponies.
      I think most of us can survive without "rich" features.

      Besides, by "rich", Microsoft probably means it'll make them rich if you get locked in to it.
  • Comment removed based on user account deletion
    • My guess would be "no." Based on the FUD that they periodically push about open source, I'm guessing they would want to add support through a project of their own so that they aren't "infected" by the "viral" open source licenses.
      • Re: (Score:2, Informative)

        by Giloo ( 1008735 )
        Hmm, maybe too flamebait or trollish here, but still.

        The good thing that could bring a MS-made ODT plugin would be 100% compatibility between ODT and OOXML. While the plugin for MS Office from Sun is just fine, it's not possible to migrate old MS Docs seamlessly. This means that people won't switch.

        I do want to make people use OpenOffice, and I use it myself, but I need to make sure that old documents will be translated with no page breaks problems and with no human interaction. And I also need to make sure
      • Re: (Score:3, Interesting)

        by sumdumass ( 711423 )
        I'm thinking they might use the Sun plugin under some special licensing deal that alows them to more closely refine the standards they are implementing.

        Opensource scare MS in their own product because they lose the level of control they are used to having. If the community changes the development and the model behind it or even changes the license to something MS wouldn't agree with (the community or sun) MS would be left out of the picture or force into a situation they might not like.

        I also suspect they w
        • by edwdig ( 47888 )
          I'm thinking they might use the Sun plugin under some special licensing deal that alows them to more closely refine the standards they are implementing.

          I believe they tried that exact idea once before. I also remember it ending in a nasty lawsuit...
          • I think that is where we got this part of the comment "I also suspect they would work for a better license then they got with Java where they can embrace and extend without complaints."

            I dunno, are we talking about the same thing?
      • by jZnat ( 793348 ) *
        Which is why they've already made a converter [sourceforge.net] that is licensed with a BSD-like license instead of a GPL'd one, right? They definitely don't like free software due to the GPL, but they've been known to release some things under an open source license (and I'm not talking about their bullshit attempt at open source software with the shared source license or whatever it's called).
    • Re:really (Score:5, Insightful)

      by Chrisq ( 894406 ) on Tuesday July 17, 2007 @10:11AM (#19886925)
      I hope I am wrong but I expect that they will have an import export functionality that has a deliberately crippled scope, for example not supporting all formats or only a certain level of table nesting. They will then state ambiguously that this is "unsupported with ODF", which along with marketing FUD will make it appear as a restriction of ODF rather than their implementation. I think that what has happened is that they see a possibility that OOXML will not be ratified as a standard. By supporting ODF they will still be able to supply companies and oganisations with a policy of using standards based formats. Their hope is that once Office is in there, if the implementation is bad enough, people will either unofficially use OOXML or lobby for a rules change to allow it to be used.
      • ...They will then state ambiguously that this is "unsupported with ODF"...

        Then they will quickly add..."Saving this document in Open XML format will solve the problem...". Would you like to save in Open XML?

        The default selection on here will be to select yes, and once one does that, it could become the default. Might I add...do not trust Microsoft.

  • Ohh Microsoft...! They (Microsoft) appear to be softening their stance on ODF...or are they?

    I'll let the pundits look into this new opened up front from Microsoft.

    But I wonder...why, don't Microsoft partner up with the ODF folks to develop one "killer" standard?

    • Re: (Score:3, Informative)

      But I wonder...why, don't Microsoft partner up with the ODF folks to develop one "killer" standard?

      You must be new here or forgot your tag.

      MS wants to keep control (aka Vendor Lock In)
      Think of MS as the RIAA of spreadsheets and memos.
      If ODF becomes the defacto standard, MS looses control and everybody can get of the MS office upgrade treadmill.
  • ODF vs. Open XML (Score:3, Interesting)

    by vigmeister ( 1112659 ) on Tuesday July 17, 2007 @09:58AM (#19886841)
    I am not sure why neither one of these formats approaches the consistency of Publisher files or Pagemaker files when it comes to retaining formatting across platforms and versions. pub files and pagemaker files (I forget what they were called) were much more consistent across versions back in 2002 (Last time I was an editor for anything was 2003). Anybody know why? Granted that pub files were enormous, but in today's day and age, size matters lesser than it did before (My girlfriend tells me that every night)

    Cheers!
    • Different purpose: Publisher and Pagemaker are expressly designed to lay out and specify exactly where everything goes on a page. If you want or need that level of control, then you can buy those programs. Office and OpenOffice aren't designed for people who normally care about that level of control over the output, but instead want document creation in standard formats to be quick and easy.
      • Re:ODF vs. Open XML (Score:4, Interesting)

        by vigmeister ( 1112659 ) on Tuesday July 17, 2007 @10:11AM (#19886923)
        My feeling is this - you create your document 'easily' using standard Office suite interfaces. It saves it like it would a publisher file which lays out your doc and specifies EXACTLY where everythign goes. When you open it again, it is formatted perfectly and you keep editing until the cycle repeats. Not sure why this wouldn't be possible. Like the reply below you suggests, uniting office level of control with a desktop publishing level of precision might lead to a killer application.

        Cheers!
        • PDF Export when you are ready to publish?
        • I agree that something like this WOULD be nice. It would probably require a good bit of work to make current office programs be able to do this consistently. For one thing, you'd probably want to start embedding fonts in the doc files. (which AFAIK no office suites do currently?)

          Reminds me.. a friend of mine in college had multiple professors (I think it was department policy) who would only accept document submissions in PDF format. Reason being that there were just too many word processing programs/platfo
          • I agree with most of what you're saying. To preserve immaculate formatting, file sizes would have to increase, but I think I'll live with that. Perhaps they can have options for different types of users. Or come up with an .fnf (formatting nazi file) extension :).

            One of my professors also does the same PDF routine. Except he manages to comes across as a badass by telling us he wants PDFs because it is not proprietary. He also accepts W3C compliant HTML. Add to this that he is a really brilliant guy, and I a
        • by r00t ( 33219 )
          What units do you use?

          a. Bob's screen
          b. Joe's screen
          c. Bob's printer
          d. Joe's printer
          e. something arbitrary, like EMUs or TWIPs

          Whatever you choose, it'll look ugly nearly everywhere unless you relax the idea of exact formatting. Text layout normally fits letters to the grid of pixels. When you change the device, you need to redo the grid fitting (changing layout) or live with blurry/uneven text.

          • Pretty much everybody uses either inches or cm as a unit. I don't think any serious word processors still fit layout to pixels.

            Open up OpenOffice and type "aaaaa"; then use a magnification tool to look at the pixels that make up the letters, all of the 'a' chars will all be different. The same thing should apply for all Office suites. Most everyday programs still fit letters to pixels because it's faster, but it's trivial to make letters straddle pixels on 100Mhz+ computers.

            It's rare to see a printer
          • by enjo13 ( 444114 ) on Tuesday July 17, 2007 @11:26AM (#19887939) Homepage
            1. Twips are anything but an arbitrary unit. There are 20 twips to a point. 72 points to 1 inch.

            2. The reason for the differences is the fact that very little in a document is stored in absolute positions. Almost everything is stored relative to other things in the document. Images are generally stored as some offset from a text anchor, for example. This allows you to make broad sweeping changes to the document easily as you can add text or other elements and the rest of the document will re-flow (since everything is stored relatively) nicely. The downside is that you are now dependent on the layout engine to ensure integrity between devices, and differences in layout in one portion of the document effect the rest of the document being positioned relatively to it. This is why word processor documents can be subtly (or sometimes hugely) different when viewed on different machines.

            This differs from a absolute positioning view of the document (think publishing software) where everything in the document is positioned in absolute terms (more or less). This makes the editing process more difficult, since adding big content pieces often means you have to revisit the various document elements and reposition them accordingly.

            At the end of the day, your word processor and your publishing tool are really solving different problems. Your word processor document isn't meant for distribution, it's meant for revision. Your PDF file is difficult to revise, but the layout is more or less guaranteed on every machine.
            • Re: (Score:2, Interesting)

              by Tacvek ( 948259 )
              Twips may not be arbitrary per se, but the number 20 might be. Further though the relationship between twips and pixels depends on the DPI. Not the actual screen DPI, but the DPI the operating system is using. It comes back to an important decision.

              Lets say I am a screen manufacturer. I currently create a screen of QVGA resolution (320×240). It is correctly sized for 96DPI having a diagonal of 4.16666667 inches. (If I calculated correctly). Now I decide to make a new screen of the same size, but usin

            • This differs from a absolute positioning view of the document (think publishing software) where everything in the document is positioned in absolute terms (more or less). This makes the editing process more difficult, since adding big content pieces often means you have to revisit the various document elements and reposition them accordingly.

              Most, if not all, desktop publishing apps allow linking text boxes and reflowing text between them. In most cases, that is all that is needed. Graphics and charts are g

    • The programs are really aimed at entirely different audiences. Pagemaker is like Quark or Indesign--desktop publishing. The control these programs give you over layout (page layout, spacing [pagraph, line, word, character], typographic features, etc) is something no word/wordperfect/oo.org/office program can match. But the goals are really different too. I wrote my thesis in word and then laid it out in InDesign. It would not have been fun to write the thing in Indesign from scratch though...the functions a
    • by jrumney ( 197329 )

      I am not sure why neither one of these formats approaches the consistency of Publisher files or Pagemaker files when it comes to retaining formatting across platforms and versions.

      I don't think consistency across versions is something that .pub files are known for. From what I've heard, you're lucky if your previous documents will even load when you upgrade MS Publisher. As for platforms, is there more than one choice? But desktop publishing is a different application than general word processing.

      • You're right about the platforms thing. Publisher used to be very consistent during the time frame I mentioned... I edited magazines and newsletters on one version and the publishing contractors were almost always using another (They kept upgrading, our school had one lame copy) and I never faced any problems. I'd guess that my experience just anecdotally proves backward compatibility, but as a general rule, I'd guess that pub files play better than docs. If it's degraded, it needs to be fixed (Publisher us
    • WordPerfect's SGML-based file format was even better. You could save a file in WordPerfect 13 and open it in WordPerfect 7 without losing any formatting. And yet 13 had a lot of newer features that 7 didn't have. Now there was a nice format to work with.
  • Microsoft "richness" (Score:5, Interesting)

    by mw13068 ( 834804 ) on Tuesday July 17, 2007 @10:00AM (#19886851)
    Is it just me, or do other people feel like gagging every time someone at Microsoft says something is "rich," has "richness," "rich user experience," etc.

    It's like eating a whole stick of butter with mayonnaise to dip it in. MS "richness" can't be good for you.

    *hurls into the wastebasket*
    • by mwvdlee ( 775178 )
      "Rich and eccentric"... I prefer my standards "plain and boring".
    • Rich adj. richer, richest

      1. Having the capacity to make Microsoft's profit margin fuller, more meaningful, or more rewarding.
    • Re: (Score:3, Interesting)

      by ajs ( 35943 )
      To be fair, what Microsoft has always meant by richness is the capacity to embed unstructured (with respect to the encapsulating format) data, the semantics of which are available to specific readers only. RFC2822 mail has such a feature, for example. Headers which begin with "X-" are allowed, but are considered vendor-specific, and do not have a default semantic.

      It makes me wonder, though... does ODF not have vendor-specific data hooks? If it does, then Microsoft is just blowing air, here.
    • It's like eating a whole stick of butter with mayonnaise to dip it in. MS "richness" can't be good for you.

      It makes you think of "Super Size Me" doesn't it?

      The only thing OOXML does for M$ that ODF won't is make M$ rich.

      There's nothing really new here. M$ has issuing the same bullshit about translators and "different purposes" for months. They won't ever tell you what their different purpose is, of course, or what good translation that will never be perfect is. They just blather on about how "rich

    • Re: (Score:2, Funny)

      by whoop ( 194 )
      Dude, you'll be the laughing stock at the family reunion picnic if you send the announcement in a format like ODF. Grandma will be like, "Your announcement just doesn't have the richness I have come to expect from documents I usually read."

      You're Powerpoint-type presentations at the office just won't have that flair when you put up six words on a huge projector. The senior vice-president of foozlages will get all up in your grill and stuff.

      So sure, go ahead and save a document in ODF. Microsoft can't hel
  • Standards (Score:5, Insightful)

    by Silver Sloth ( 770927 ) on Tuesday July 17, 2007 @10:01AM (#19886853)
    From TFA

    Standards, Robertson told BetaNews, "are a very important tool to use to address interoperability. But I would note that they're not the only tool, and they may not be the most appropriate tool in a particular set of circumstances.
    Sorry, no, standards are the only tool.
  • by D-Cypell ( 446534 ) on Tuesday July 17, 2007 @10:06AM (#19886895)
    Microsoft Will Support ODF If It Doesn't 'Restrict Choice Among Formats'

    It is very noble of Microsoft to complain about all these restrictive document format that seem to be so pervasive in the IT world. I applaud them for looking out for my interests and freedom to choose. I have to say though, I am a little worried about them. All this goodwill stuff is well and good, but I can't help feel that until they start to get a little bit more militant about protecting their own IPR and file format, their business will never get off of the ground! :(
  • by McNihil ( 612243 ) on Tuesday July 17, 2007 @10:07AM (#19886907)
    in Airplane II where the warning light is flashing with a man with a shovel behind a bull.
  • by Anonymous Coward on Tuesday July 17, 2007 @10:11AM (#19886927)
    "richer functionality" = setSpacesLikeWord95
  • My Needs (Score:3, Insightful)

    by MCSEBear ( 907831 ) on Tuesday July 17, 2007 @10:15AM (#19886977)

    This is not to say that one is better than the other -- just that they meet different needs in the marketplace.


    Dear Microsoft,

    Thank you for your input. However our needs in the marketplace seem to be different than your own. Most users don't find being locked into a Microsoft proprietary document format to be their most important need. How about you quit bitching about Apple locking people into their proprietary music player long enough to quit locking users into your Office document formats, or your Exchange email sever, or any of your products that refuse to support open standards. After all, Apple's MP3 player will let me play a standard MP3 and will allow me to rip a standard CD. How about you let us open an open standard document format?

    Fuck you very much,

    Your Users
  • by kebes ( 861706 ) on Tuesday July 17, 2007 @10:15AM (#19886981) Journal
    The good news is that if Microsoft is changing their tactics, it means that they are admitting (partial) defeat in their previous attempts. Essentially they have lost the technical argument. Many groups have weighed-in on the subject and agreed that ODF is a more open format, and actually meets the needs of a standard. OXML is not winning that particular competition.

    So they have a new tactic. This tactic basically amounts to saying: "Let's just have both standards, and let people pick the one they want. Oh... did we mention that OXML will be the default in all of our products?" Moreover, they are strongly implying that ODF is a lame duck, and that OXML has "more features" and is "richer." They are trying to paint ODF as the poor-man's format, with OXML being the format you use when you're serious.

    The bad news is that this tactic will probably work. If OXML is the default format (in the dominant Office suite), people will view it as being the "serious" one and anything else as being "dumb." It doesn't matter that the additional "richness" is a bunch of features that these users will never activate. It also doesn't matter that the additional "richness" won't be maintained cleanly across platforms, during filetype conversions, and possibly even across software version changes. All that matters is building mindshare that truly believes that OXML is "the real deal" and that anything else is "that weird thing that geeks use."

    So the counterattack from those of us who would prefer a true standard (such as ODF) to become the default need to use ODF as much as possible, and encourage others to do the same. ODF is the one that guarantees readability into the future, and that guarantees interoperability. We need to make this clear to everyone else.
    • Re: (Score:3, Interesting)

      by loconet ( 415875 )
      Another bad news is that MS will somehow manage to "interpret" the ODF standard incorrectly and cripple its functionality making it look inferior in the eyes of the user. Maybe, it will magically mess up the formatting, printing, exporting to other types, who knows what else. What I do know is that this one sour experience will stir users away from using ODF and force them to stick with OXML. Watching MS do "business" has become like watching a Mexican soap opera, I already know the plot and ending even bef
      • by jimicus ( 737525 )
        Of course they will. And as soon as any technical journalist asks them about it, the response will be some boilerplate about how they've "done the best they could within the limitations of the format - we did say that OOXML would be richer..."
      • by alexhs ( 877055 )

        Another bad news is that MS will somehow manage to "interpret" the ODF standard incorrectly and cripple its functionality making it look inferior in the eyes of the user.

        I can see that as good news, if it takes "the Firefox way" : You have the choice between a free office suite that render ODF correctly and a paid for one that does render ODF incorrectly. People have no qualms about having many software installed (they can and do already read PDF documents with Adobe Acrobat Reader). Therefore increased mindshare for OpenOffice.org, and the start of the decline of MS-Office market share.

    • Re: (Score:3, Insightful)

      by jkrise ( 535370 )
      Essentially they have lost the technical argument.

      The ISO is supposed to be a technical organisation - a wtchdog for global interests and standards. If Microsoft's proposed format does not meet the technical requirements of a document standard, they must simply reject it, since it has been fast trcked.

      "Let's just have both standards, and let people pick the one they want. Oh... did we mention that OXML will be the default in all of our products?"

      Even if the ISO rejects the OOXML, Microsoft can still sup
  • by MarkWatson ( 189759 ) on Tuesday July 17, 2007 @10:18AM (#19887005) Homepage
    If ODF support were perfect, I might consider buying an updated OS X version of Word when a native Intel version is available - I would want to try a 30 day demo first, however. I own licenses for older versions of Word/Office for Windows and OS X (I am an author and most of my publishers like manuscripts delivered in Word formats). I have written several books using OpenOffice.org, and at the last minute converted to Word.

    That said, at least for my work on Mac OS X, the best writing tools are: TexShop with OmniGraffle for technical diagrams. Latex and OmniGraffle are a great combination!
  • A plug-in that supports Open Office formats in M$ Office. I would like to think that it works and that M$ cooperated in its development. I suppose it could have been reverse engineered. I would respect M$ a lot more if they just would stop breaking their previous products with so-called upgrades. Word processors are mature products, there is no reason that there should be any struggles over file formats.
  • by Tuoqui ( 1091447 ) on Tuesday July 17, 2007 @10:20AM (#19887029) Journal
    Just as the automobile can co-exist with the airplane, ODF and Open XML can and should co-exist, the team writes. They go on to imply that standards agencies should not place themselves in a role similar to restricting transportation solely to the ground level.

    Sorta like the Department of Homeland Security and the 'No Fly Lists' that they put out to limit people to ground level transportation? I'm sorry but if ODF becomes the standard everyone uses/wants then Microsoft can adapt or die like anyone else in the marketplace. We dont owe them any favors for half assed OSes with bugs all the way up and down the spectrum and trying to force DRM onto people and make themselves out to be the Piracy Police.

    The fact they're putting so much time and effort into trying to kill ODF just goes to prove that the standard *IS* a much better designed one and that Microsoft cannot compete on a level playing field. Oh dont worry I fully expect that sooner or later they'll find a way to make it so you cant install open office or any alternative text editors onto their machines (what you thought that computer you bought was YOURS?)
  • by pubjames ( 468013 ) on Tuesday July 17, 2007 @10:21AM (#19887031)

    Personally, I think file formats will become irrelevant to the end user.

    It's really dumb that (for instance) we produce documents in Word, convert them to PDF, email them to someone else, who will read them on a computer screen. We are stuck in last generation technology, and people growing up with the web today just won't do it. Although many of us find it hard to believe, on-line systems will eventually replace Microsoft Word, OpenOffice etc. completely.

    When that happens, the file formats will be irrelevant to the end user, just as web page formats are pretty much irrelevant to current web users. This is bad news for Microsoft, since they have an incredible amount of lock-in at the moment due to their proprietary formats. However, they are not going to be able to transition that lock-in to the web.
    • Oh, so that naturally explains why the internet is full of Microsoft IE ONLY web sites. Microsoft won't be able to transition lockin to the web ? That must explain Microsofts rush to implement open web standards!
      • Re: (Score:2, Informative)

        by pubjames ( 468013 )
        Oh, so that naturally explains why the internet is full of Microsoft IE ONLY web sites.

        It is?

        Maybe for you, but I haven't used IE for over a year and I don't recall coming across a single site that I haven't been able to access. Although I've read that in the US lots of banks require IE - perhaps that's what gives you the impression that there are lots of IE sites?
      • Re: (Score:3, Informative)

        by Shados ( 741919 )
        The only IE-only sites I've seen in years were internal corporate intranet applications, and even those are starting to be rare...
        • It's true that things have improved but until recently, the hotmail site was a sod to access if you weren't using IE on Windows. My local government web site had been IE (on Windows) only for years and they just fixed it about 2 months ago.

          Embedded media has long been an issue. These days a lot of sites are using flash-based players rather than serving WMV files that can't be viewed on other platforms. That's a definite improvement.

          A lot of work done, some fine-tuning left to do.
          • by jcgf ( 688310 )

            the hotmail site was a sod to access if you weren't using IE on Windows.

            Really? I've never had a problem and I've been using hotmail since before MS bought them. I never use IE and only use windows at work.

            what problems did you run into? Sluggish loading, buttons not lined up?

        • by sconeu ( 64226 )
          The only IE-only sites I've seen in years were internal corporate intranet applications, and even those are starting to be rare

          I don't think that US Customs [gripe2ed.com] is an internal corporate intranet app.
    • Web sites are definitely going in the right direction. There is still a certain amount of MS lock-in regarding the use of features (and bugs) only present on Windows but most sites have fixed those. I credit Firefox with helping a great deal in opening up the web for people who don't use Windows.

      Fonts are going to hold compatibility back for some time though. PDF embeds the necessary fonts which makes it a nice format for sending to others. It's not easy to edit them though and even if you could edit it, yo
  • by FedeTXF ( 456407 ) on Tuesday July 17, 2007 @10:24AM (#19887067)
    Yes, OOXML is richer, specially when you want to represent dates: http://www.openmalaysiablog.com/2007/06/malaysias_ histo.html [openmalaysiablog.com]
    • Re: (Score:3, Informative)

      by KarmaMB84 ( 743001 )
      The date format is backwards compatible with Excel 2003 and earlier which represented dates in days since Jan 1 1900 and also considers 1900 a leap year (it was not) in order to remain compatible with Lotus 1-2-3 which incorrectly considered it a leap year.

      The rest of the linked article is mostly bullshit. It isn't a problem with the XML format, it's a legacy limitation with Excel due to compatibility with the previous broken leader. Hash marks mean the date won't fit into the cell (increase the width of
  • So actually... (Score:3, Interesting)

    by yogi ( 3827 ) on Tuesday July 17, 2007 @10:24AM (#19887075) Homepage
    Well, after reading TFA, I get the impression that Microsoft hasn't really gone for "active support" as such. What they have said is that they didn't object to ODF going through the standards bodies.

    Of course, with ODF being a fairly well documented open standard, there wasn't really any convincing way that they *could* object.

    What makes MS very, very scared is widespread ODF adoption. Once state governments started to mandate open standards in government documents, it looked pretty much like ODF would get adopted. Not because ODF was superior, but because they had bothered to go through ANSI/ISO etc.

    Since then, there has been a two pronged solution for microsoft. One has been to get OOXML to become a "proper standard", and the other is to browbeat state governments into giving up their policies. The former ran into problems, when IBM and others pointed out to ECMA that the OOXML spec was anything but open.

    Microsoft cried foul straight away. Their argument "We didn't object to ODF, why are you objecting to OOXML?". The answer from IBM et al. was -- the OOXML standard sucks, and can only be implemented by someone who has the source code for all versions of MS-Office. It's not open, and until it is, we are not supporting it.

    This "announcement" by MS, is nothing more than a warmed over restatement of this position, and mentions some esoteric features of OOXML that are not in ODF.
  • by JustNiz ( 692889 ) on Tuesday July 17, 2007 @10:31AM (#19887145)
    OpenXML definition allows it to contain BLOBs (binary large objects) in undocumented formats.

    This reduces OpenXML to just marketing bullshit with no real substance, because we all know Microsoft will just use/store their old formats as a BLOB in an OpenXML wrapper which continues to ensure no-one else can read it, yet allows them to say that they are using a publically available standard.
  • Since I can't find it in the article itself:
    http://www.microsoft.com/interop/letters/userchoic e.mspx [microsoft.com]

    It's a month old, but who's counting..?
  • by Compenguin ( 175952 ) on Tuesday July 17, 2007 @10:56AM (#19887497)
    Microsoft did the same this with VC-1, they sat on all the MPEG committees but then took their own similar but semantically different standard to a different body.
  • Business will support it.

    Microsoft is not changing their tactic. Their tactic was this: push for a proprietary standard and if one cannot exist, accept what does exist, and then start making suggestions so it becomes clear MS are experts in that field.

    Very few large businesses have a single option when they're pushing hard for something.

    Business will support anything that can be made profitable. History shows us this. Governments support both oppressive governments and civil rights, both conservative Chr

  • I really have to get the "For Sale" signs up on my bridges.

    The consensus here seems to be that, for some reason, Microsoft is afraid of ODF. Does anyone honestly believe that Microsoft is not capable, or believes it is not capable, of delivering the best and most able word processor producing ODF files?

    Thanks for the chuckle.

    • Re: (Score:3, Insightful)

      by kebes ( 861706 )

      The consensus here seems to be that, for some reason, Microsoft is afraid of ODF. Does anyone honestly believe that Microsoft is not capable, or believes it is not capable, of delivering the best and most able word processor producing ODF files?

      Actually maybe you should direct that question to Microsoft. If Microsoft is confident that they can deliver the best and most capable Office Suite that opens/writes ODF, and the users are asking for ODF, then what's the problem? Why doesn't Microsoft just shut up,

      • Scared? Hardly. (Score:3, Insightful)

        by Petersko ( 564140 )
        "Microsoft is scared to death of the free market. In a fair competition of various products, MS would still make money, but not nearly as much as they do now, where they have the entire market captured due to file-format lock-in. This is what makes Microsoft scared. This is why they are being pulled kicking and screaming into the world of open and standards-compliant file formats."

        Yeah. Sure. Microsoft is scared of competition in a free market. Because they've failed at it so dramatically in the past.
    • Does anyone honestly believe that Microsoft is not capable, or believes it is not capable, of delivering the best and most able word processor producing ODF files?
      Yes
    • Wether they are capable or not is not the point. (Although quite frankly, as far as I'm concerned, most MS software is bloated crap - and that includes Windows)

      They are afraid of ODF because, unlike with the MS proprietary formats, one does not have to buy MS Software to be able to read and write it. This means that if ODF becomes popular or even mandatory in some cases, they then have to compete for real in that market, which they'd really rather not have to do.
  • by jkrise ( 535370 ) on Tuesday July 17, 2007 @11:22AM (#19887867) Journal
    From TFA:

    "We should expect the creation of new formats in the future as technology evolves, and, as has always been the case, users should be able to choose the formats that work best for them," reads the team's open letter this afternoon. "Microsoft has consistently supported choice, so it took no steps to hinder ISO/IEC's ratification of ODF 1.0 and supported ODF 1.0's addition to the American National Standards list. Microsoft will continue to support recognition of ODF 1.0 and other formats on such lists around the world as long as doing so in no way restricts choice among formats."
    Someone should tell Microsoft that both ODF and OOXML are supposed to be based around XML, short for eXtensible Markup Language. In short, both formats ought to be expandable and extendable without the need for breaking entire legacy applications built around earlier standards or versions of ODF or OOXML. It is Microsoft's behaviour to discontinue support for legacy formats / make such support quirky and clunky, as to make it meaningless / unusable.

    The pledge to support 'ODF and other formats' is just a carrot - it's like .Net supporting all languages - but the basic idea of .Net wa to be a Java killer. Which will be the fate of other formats if OOXML is ratified by the ISO.

    Besides, America is not the only country in the planet, so if the ISO is indeed the International Standards Organisation, it must not be influenced by a single commercial entity.

    Open XML may be more attractive to those who want richer functionality, the ability to integrate business data into their documents by defining their own document schema, or a format that was designed to be backwards compatible with existing documents.
    The XML spec does not need permission from Microsoft in order to be extensible and adaptable, by changing default schemas - in fact, I think the ISO must request Microsoft to rename the format without using the words Open and XML simultaneously.
  • People don't care about which format is better, they care about who controls it.

    Organisations are trying to move away from Microsoft controlled formats for their documents, simply so they can choose which software to run and not have to use Microsoft simply because they are forced to.

    Given the huge cost of Office it's no wonder many are trying alternatives.
  • Open XML may be more attractive to those who want richer functionality...

    The tone of this is not encouraging.

    You ever import something into Word that it technically supports, but only as much as NT supported POSIX? The result is generally pretty craptastic. Who believes that even the simplest ODF document wont look like it was formatted by monkeys compared to the MS endorsed version?

  • Just as the automobile can co-exist with the airplane, ODF and Open XML can and should co-exist, the team writes. They go on to imply that standards agencies should not place themselves in a role similar to restricting transportation solely to the ground level.

    Since they're likening themselves to an airplane, does this mean they will expect users to take off their shoes, empty their pockets, etc. and go through a metal detector and X-ray search before using their Open XML format? Inquiring minds want to know ...

  • by rs232 ( 849320 ) on Tuesday July 17, 2007 @12:57PM (#19889345)
    "open source ODF format as perhaps trying to monopolize the standards process [betanews.com]"

    translation: An open format that anyone can write to without conceding licensing restrictions to a single commercial company is in actuallity a monopoly.

    "Certainly there's a place for ODF in the world, the interoperability team continues, and users are free to make that choice for whatever reasons they'd want to do so"

    translation: We want to own the standard.

    "We ensure our ability to add value by ensuring that we are masters of the schema [edge-op.org]"

    "Microsoft perceives the standards process as one of four "toolsets" .. to achieve interoperability .. when the standards process fails, he said, the other three "toolsets" could be relied upon as a backup plan"

    translation: We'll pretend to support open standards while covertly working to push our own non-standard standard.

    'Standards, Robertson told BetaNews, "are a very important tool to use to address interoperability .. cycle of innovation that's more rapid than the cycle of standardization .. and shouldn't you look to some of the other tools that you have available to you, to address interoperability?'

    translation: We'll continue to play hunt the piñata with the formats as it's worked very well up to now in maintaining our monopoly on the desktop.

    How about publishing an RFC the next time you 'innovate'?
  • by Trestop ( 571707 ) on Tuesday July 17, 2007 @01:09PM (#19889535) Homepage Journal
    From reading the article, its clear that the summary above is quite misleading - Microsoft will not "support" ODF in the sense that they will offer a version of their office productivity suite which allows for opening or saving ODF files.

    Microsoft will "support" ODF in the sense that they will not contest the standardization of ODF as an ISO/IEC/ANSI standard if ISO/IEC also accepts OOXML as an international standard. Nobody at any point said anything about Microsoft releasing software that understands ODF.
  • Haha (Score:3, Insightful)

    by Vexorian ( 959249 ) on Tuesday July 17, 2007 @02:22PM (#19890771)

    MS said that they don't want to get "locked-in" with ODF... That's rather ironic, anyways:


    Recipe for a good standard format:
    • A good specification (as, in the standard actually specifies things... as it anyone is able to implement it correctly after reading the specification...)
    • Minimalistic: Seriously, an standard should be as small as possible to let it be easy to implement.
    • Open: As in, you don't require patented code to read the format.
    • Unique : "More than one standard" would be the most retarded idea ever.

    The fact you are the largest software company in the world shouldn't mean you should "own" any "standard". We don't need an standard that would function exactly the same as the defacto-standard from old office, that would be useless and will only make the world waste resources in the migration from one closed defacto-standard towards a closed "standard".

    ISO will show a lot of incompetence if they actually approve two standards for exactly the same thing... If that happens we will have to replace ISO, really

    No offense to MS, they make great products and all, but I would love to see people use their products because they are the best products and not because they are the only ones that implement their format correctly, I hate self-feeding monopolies.

Anyone can make an omelet with eggs. The trick is to make one with none.

Working...