Slashdot Mirror


Microsoft Ends Era Of Closed File Formats

RzUpAnmsCwrds writes "According to an MSDN Channel 9 interview with an Office file-format developer, the next version of Microsoft Office (Office 12) will default to newly-developed XML file formats in Word, Excel, and PowerPoint. The new formats will apparently include XML files along with other files (images, etc) inside of a Zip file. Microsoft will also be providing extensive documentation of the new format to the public through MSDN. The developer likewise announced that Microsoft would be releasing updates for Office 2000, XP, and 2003 to read and write the new formats when the new version of Office is released. If this interview is correct, it could mean the beginning of the end of Microsoft's proprietary file formats." Coverage at Beta News, Information Week, and the Washington Post.

5 of 651 comments (clear)

  1. Loosing lock-in capability? by haluness · · Score: 4, Interesting

    Would'nt this approach cause MS to loose its lock-in ability based on file format?

    Of course this assumes that lock-in was one of their goals with a propietary format

    1. Re:Loosing lock-in capability? by Shalda · · Score: 4, Interesting

      The existing Office document formats are all pretty well documented by 3rd parties. It hasn't even scratched Microsoft's sales. Microsoft's vision on this takes several forms. First, Office is a suite of programs that interoperate. You can embed your spreadsheet in your Word doc or your PowerPoint presentation. Update your spreadsheet and it also updates wherever those numbers also exist. Their second angle is for developers. They want you to use .NET for your in house development. Your user needs to send out a letter? Your program will pull up a document and prefill nearly everything. Thirdly, the now have something they can take to governments and other organizations that are demanding open formats. Finally, no matter how well it's documented, there will be dozens of odd little quirks. But that's ok, so long as you're using the tools that Microsoft provides. Proprietary formats get cracked, quickly and easily. Microsoft wants an end to end lock in.

  2. Convenient... by daveschroeder · · Score: 3, Interesting

    ...now that they've all but killed off all of the commercial, vendor-supported competition.

    And whatever happened to Office Integrated Rights Management, essentially a DRM for Office documents (New Office locks down documents) that (of course) requires a Windows server to administer, and only works with Microsoft Office? You don't think that they're just going to let that go by the wayside, do you?

    And what about patents?

    Sure, OpenOffice is great, but commercial enterprises will stick with commercial solutions for which there is support. And yes, this could be built for something like OpenOffice (and indeed exists for StarOffice), just as it has been for Red Hat, but I can't see this as anything more than a much belated, empty gesture on Microsoft's part. This sums it up: "Microsoft is doing this as a way to protect its presence on the desktop." Microsoft even dug up Charles Goldfarb, "co-inventor of the concept of markup languages", for its press release to say, "Making XML the default Office file format is, for me, the culmination of a 35-year dream," Charles F. Goldfarb, the inventor of the markup language technology, said in a statement released by Microsoft. Nice touch.

    Also, "Microsoft Ends Era Of Closed File Formats" is a little overreaching, don't you think? They're looking for the biggest lock-in of all with the proprietary Windows Media formats. Microsoft wants to be everywhere there is any kind of media, and it's NOT open. Boy, I can't wait to live in a world where Microsoft controls and meters content and has everyone from the end consumer to cable, satellite, and telecom operators, movie and TV production houses, and everyone in between by the balls, which is exactly what will happen if they get their way. (And submission to SMPTE *hardly* means anything. Standards are standards AFTER they've been vetted by standards bodies, have had the patent searches and pools completed, etc., and have been, you know, actually approved. Not when they've been "submitted for consideration". Further, that gesture is nothing more than an attempt to get pinhead PHB-type managers and executives on board with Microsoft when their technical underlings are pulling for open standards like H.264 - then Microsoft can shoot back to the management, Hey, we're just as open as the MPEG family of standards! Look, we even submitted our codec to SMPTE! It's not our fault they take so long to approve things! Do you really want all that H-dot-whatever-gobbledeygook that your oddball IT guys are talking about? After all, that's what *Apple* uses. You don't want an Apple technology, do you? Go with us; you know Microsoft is the right choice for your 18-million-customer cable service! Utter bullshit. And ignores the fact that all of the codec improvements and tools will NOT be open; the SMPTE submission is nothing more than a thinly veiled attempt to put Windows Media everywhere as well by claiming to be "open" when they're anything but.)

  3. Consider this. by PsychicX · · Score: 5, Interesting

    It's interesting that they're doing this. I've been playing with OOo 2.0 beta lately, both under windows and *nix. I'm an Office user, but a home user, not a power user (I'm not a business dealing in several hundred page docs, I just do my homework). And I basically can't see any particular difference between the two packages. I have Office 2000, and so I'm using it, but I'd probably be perfectly comfortable using only OOo (2.0, I hate 1.1)

    Anyway, my point is that MS is making it clear that they're not threatened by competing packages, and I'm not entirely sure why not. OOo could easily replace Office for many (I hesitate to say most) users, and if we switch to totally open formats, they'll be able to interoperate without any difficulties. I'm not trying to say that OOo is in a position to hurt Office...but I'm curious if it might be. MS doesn't seem to think so, and I'm really, really wondering what makes them so nonchalant.

  4. Re:Heard this before by AKAImBatman · · Score: 4, Interesting

    Actually, that's not a bad point. What's to stop Microsoft from implanting things like VBScriptlets that are required for the document to render? That would put a real cramp in the competitors' ability to read the format, regardless of how "Open" it is.