Slashdot Mirror


We're Open enough, Says Microsoft

An anonymous reader writes "Microsoft Australia has come under fire from rival vendors and open-source advocates for keeping its Office document standards proprietary. Greg Stone, Microsoft's national technology officer for Australia and New Zealand, faced criticism during his presentation at the Australian Unix User Group conference in Canberra yesterday. However, he stood firm on the company's policy of making the XML schemas for its Office 2003 document standard publicly available provided interested parties sign an agreement with the software heavyweight. "Why should I have to sign an agreement?" one audience member demanded to know."

24 of 660 comments (clear)

  1. How right they are by Anonymous Coward · · Score: 5, Funny

    Just look at IE.
    Can one piece of software possibly be more open to exploits and viruses?

  2. A better response to this by Umbral+Blot · · Score: 5, Interesting

    In reality there is no way MS will open up the .doc format. Lock-in for office file formats and the office products are central to MS's revenue scheme. The way to beat them is not to beg for them to open up their standard, but to create a better open standard backed by the community, one that is not layered in junk like the .doc standard is (why would you need to embed a video in a text document?). Then this standard could be supported by as many open source, and maybe even commercial projects as possible. With enough momentum we might be able to pull an adobe and create a format that is able to coexist popularly with the .doc format. It would be wonderful if MS would play nice; they don't have too, but we don't have to play their game either.

    1. Re:A better response to this by Bert64 · · Score: 5, Informative

      There is such a format, OpenDocument, it is supported by the upcoming openoffice 2.0 and the next version of staroffice and is listed on oasis-open.org, now if only other opensource apps would start to use it.. And perhaps commercial vendors like wordperfect and apple.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    2. Re:A better response to this by jazman · · Score: 5, Interesting

      > why would you need to embed a video in a text document?

      Why not? The other way is to distribute a bunch of files and have references in the document like "play video 1 now". If you want to distribute a document that describes a series of video clips, embedding those videos in the document itself is seamless.

      Just because the OSS community doesn't consider it necessary doesn't mean it's a daft idea. Geeks are completely at home with receiving a bunch of files and playing them as prompted within a document, but the average PHB who can't tell one end of a mouse from the other isn't going to want to mess around like that or to spend more than a microsecond trying to figure out why one of the distributed videos won't play on his system. Geeks will spend hours messing with GSpot and downloading codecs, but PHBs aren't going to fanny around with all that geeky crap.

      Plus any boss who fiddles with Linux for a bit isn't going to take long before concluding Linux is retarded because you can't embed video in docs like you can in Word. Sorry, but you have to address "what the users want" and not just "what the geeks want" if Linux is to take over from Microsoft. Windows may be the biggest pile of bugs since a very big pile of bugs but apart from keeling over once in a while it does do what most people want.

    3. Re:A better response to this by molnarcs · · Score: 5, Informative
      That's what is great about the new OpenOffice.org format. (trying to build it right now, fingers crossed). According to oo.o, it is not only supported by the community, but also the European Commission as well:

      Beginning with version 2.0 OpenOffice.org uses the open standard OASIS OpenDocument XML format as the default file format. The OASIS OpenDocument format is a vendor and implementation independent file format, and thus guarantees freedom and independence. In addition to OpenOffice.org itself, the open source office suite KOffice as well as OpenOffice.org derivatives like the StarOffice software support the OASIS OpenDocument file format. The OASIS OpenDocument file format is also one of the file formats recommended by the European Commision. oo.o-2.0 feature-guide

      Fileextensions:

      • OpenDocument Text [.odt]
      • OpenDocument Text [.odt]
      • OpenDocument Text Template [.ott]
      • OpenDocument Master Document [.odm]
      • OpenDocument Spreadsheet [.ods]
      • OpenDocument Spreadsheet Template [.ots]
      • OpenDocument Drawing [.odg]
      • OpenDocument Presentation [.odp]
      • OpenDocument Chart [.odc]
      • OpenDocument Database [.odb]

      I think that this standarization might help in persuading governments to choose this new format. Although not an office suite strictly speaking, I wonder about abiword's default file-format... Does/will it use this new standard as the default as well (seems to be a good idea).
    4. Re:A better response to this by master_p · · Score: 5, Insightful

      A printed document is a different thing than a Hypertext document. The grandparent post is right: there should be no need to embedd a video in a document that is to be printed, i.e. used as a book, as written documentation.

      On the other hand, you are also correct, but what you are referring to are not paper documents, but hypertext documents. Hypertext documents should be able to have anything in them, because their sole purpose is to pass information around through computers.

      The difference between paper and on-screen documents is what caused your disagreement. Software vendors like Microsoft have either failed to realise this difference, or they deliberately ignored it in order to lock-in their customers.

  3. Re:Feed me! by Anonymous Coward · · Score: 5, Insightful

    You are able to do so, despite MS best efforts. People had to reverse engineer the doc format to get this accomplished.

    So I don't really see your point. Just because people make great efforts to accomplish something that would be trivial if MS released the specs or adhered to an open standard, doesn't mean that MS is in the right, does it?

  4. That's their decision by Anonymous Coward · · Score: 5, Insightful
    'Why should I have to sign an agreement?' one audience member demanded to know.

    Because you want something that they have. They developed the file formats, so they own the intellectual property. If you want them to spell out how they work for you, you'll have to play by their rules. If you don't like that, that's fine too. You don't have to know now their file formats work to use their product, and when it comes down to it you don't even have to use their product.

    This seems to me a lot like the BitKeeper debacle. It's all about contracts: the people who have something of value get to dictate the terms of the contract. No matter how much you complain about it and say "but file formats should be free!", that's not going to change.

    1. Re:That's their decision by mcc · · Score: 5, Insightful

      They developed the file formats, so they own the intellectual property.

      Of course, after they developed the file formats they violated United States antitrust law and were found guilty, and in lieu of sentencing agreed to a settlement which (in spirit, even if it contains many loopholes in letter) stipulated they must open up for use by the public the file formats, APIs, etc, which they own.

      But, y'know, little niggling details.

  5. and... by Anonymous Coward · · Score: 5, Funny

    our customers are also opened enough....we only have to give them a litle more vaseline to maximize the opening

  6. Re:Feed me! by realityfighter · · Score: 5, Informative

    Actually, OpenOffice's encoding for .doc doesn't work perfectly. And it's a downright bitch if you're trying to pass files between OpenOffice and Word. I was a freelance manual writer for a while, and my copy of Word self-destructed. (It wouldn't take the activation code that was printed ON THE DISK.)

    So I thought, time to switch to an open alternative. Bad idea. I couldn't pass edits to the engineer I was working with because every time I'd get back a file with corrupted layout and images about the size of Jupiter.

    As far as I can tell, this is because they have to build their .doc encoder based on intelligent guesswork. If the standards were open, they could get compatability spot on.

    --
    A strain of paranoid prevention can be worse than the disease, whate'er the intention.
  7. Why shoud I have to sign... by drgonzo59 · · Score: 5, Interesting
    "Why should I have to sign an agreement?" one audience member demanded to know.

    What would the agreement do? The standard is either open or not (specification is published or withheld). Does it mean that any program that reads the file in this "open" format is bound by this agreement? I can see someone writting "Here, I sent you a powerpoint presentation and I also had to attach the 3 page agreement that you have to sign and send to Microsoft along with your name, date of birth, social security # and all your bank information. Then you can open and use my file. If you don't Bill Gates will come in person and take your firsborn child. Have a nice day, -Your dearest friend Jojo"

    1. Re:Why shoud I have to sign... by ajs318 · · Score: 5, Informative

      Only if you are going to modify the document, then distribute it outside your organisation; and even then, you might have to modify the actual font. Otherwise, embedding a font into a document -- provided it is done in such a way that the complete font can be recovered for use in other documents -- would be considered "mere aggregation". At any rate, a document is not generally considered to be a derived work of a font.

      --
      Je fume. Tu fumes. Nous fûmes!
  8. Worked before by Anonymous Coward · · Score: 5, Insightful

    Notice how Microsoft successfully ended all use of the word "innovation" anywhere in the late 90s by their repeated abuse of it.

    "Open" is next.

    They've found that if you don't want to do something, it's totally sufficient to not do it and then repeat to the press over and over that you did it.

  9. Madness by Anonymous Coward · · Score: 5, Interesting
    It would be madness to sign any such agreement to look at their format. I would need to have some very competent lawyer go over it and figure out what it's saying and what the risks are. If I sign it, do I have the right to talk about what I have learned? Can I build tools based on this format? Are their restrictions on how I can redistribute or use such tools? If I build such tools and sell them, do I have to pay any royalties? Am I committing to patent licensing? Are there trade secrets in the formats, so that if I learn these "secrets" I can no long do any work on other open formats like OASIS? Am I committing myself to some specific dispute resolution protocol if there is a dispute under the agreement? Am I committing to some particular jurisdiction (which may not be advantageous to me)? Am I agreeing that they have injunctive relief if they think I have done something wrong under the agreement? Injunctive relief means that they could get a judge to shut me down while the dispute is being resolved, which could take years and enormous amounts of money. Until I could get some very clear answers to these questions I would stay far away, and I would guess it would a big legal bill to get answers I am comfortable with.

    So before I would sign, I would need to find a lawyer and pay a lot of money to find out what the implications of signing it would be. I would go through enormous hassle and a lot of money, just so I would have the honor and delight to look at MS' file format specification. But wait, I might go through all that hassle and expense and come up with some answers that I don't like, like finding out that the spec does contain trade secrets, or that I am agreeing to give MS injunctive relief, and if I find those thing out, I will have spent all that money and still I won't be able to look at the spec.

    Or I could skip all of this nonsense and ignore whatever they are offering and just use one format which I know is truly open: OASIS. I don't need to sign anything, it doesn't contain any trade secrets, I don't need a lawyer, I don't need to spend any money, I am free to write whatever kind of software I want to based on it, I can do whatever I want with it, I don't have to pay, I don't have to worry about someone getting an injunction to shut me down if he thinks I did something wrong. Wow, when you look at it this way, what's there to even think about in making this decision?

    What we really need is an OASIS plug-in for MS Office so that MS Office users can use the OASIS format without any hassles. That would be cool.

  10. Re:Agreement by mcc · · Score: 5, Insightful
    If I use code that's licensed under the GPL, I have to agree to the terms of the GPL, yes?

    No.

    From the GPL:
    Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
    If by "use" you mean "redistribute" then things are more complex, but since at the moment you are trying to compare the GPL to a contract which must be signed in order merely to read a certain document, there does not seem to be any reason to focus on redistribution unless you are trying to change the subject and/or create an aimless flamewar.
  11. Re:So... by 0x461FAB0BD7D2 · · Score: 5, Funny

    And they say the GPL is viral!

  12. Re:Feed me! by Anonymous Coward · · Score: 5, Insightful

    They probably won't look the same, except in the most trivial cases. However you don't have that level of confidence if you use one version of Microsoft Office and send the document to a user with a different version of Microsoft Office, so you don't have much to lose by using OO.o instead.

  13. Makes sense... by zecg · · Score: 5, Funny

    Root is safe, beta is gold, MS is open enough and MN2004 is coming back on a corrected trajectory. All makes sense.

    --
    .i lu doi ringos.star. xu do puku'aroroi dunli dopecaku leni virnu li'u
  14. Re:Thank you, sir. May I have another? by l3v1 · · Score: 5, Insightful

    without MS you have no web/html like we have today

    And without ignorant guys like you MS wouldn't have so much revenue.

    --
    I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
  15. the extremists have it all wrong by maxpublic · · Score: 5, Insightful

    If anything the extremists should be encouraging Microsoft to be as closed, proprietary and cumbersome as they can possibly get. They seem to be shooting themselves in the foot here by trying to cajole/convince Microsoft into playing along.

    Seriously, if you're one of those folks who sees all proprietary software as a tool of Satan (says me, writing this in Opera), you don't want Satans reps on Earth to soften their image. You want them to instead impress people over and over again with their Black-Hatness so even the most clueless will eventually wake up and say "what the fuck?"

    You *want* MS to lock people in - and then bend them over and ream them good and hard once the lock-in is established. That creates enormous ill-will, especially to the PHBs who don't like anyone messing with their kingdoms. When the next opportunity comes to jump ship, they'll be that much more inclined to do so (e.g., when the next full-scale upgrade and conversion takes place).

    The harder they squeeze, the more star systems, er, customers, that'll slip through their grasp.

    So fanatics, crusaders, and all you "information wants to be free" loons (who STILL won't send me your credit card numbers, you hypocrits), reevaluate your game plan here. You're doing your cause a disservice. Every time MS screws over a customer pat them on the back and say "good job!"

    Max

    --
    My god carries a hammer. Your god died nailed to a tree. Any questions?
  16. Re:Feed me! by ajs318 · · Score: 5, Interesting

    If MS Word could import and export .SXW files natively, there would be no need for MS Word in the first place. It's only the fact that Word -- and nothing else -- can read .DOC files properly, that keeps Microsoft selling it. If Word could import and export .SXW files, an organisation could keep just one PC with a copy of Windows and Office {plus OO.o export}, all the rest using OpenOffice.org, and use just this one machine for translating legacy documents.

    Now, MS Word has a macro language -- a bastardised dialect of BASIC -- and a document object model {though not quite like the W3C ECMAscript one} that allows the canny programmer access to every feature of a document. And the code to synthesise and analyse SXW files is open source. It ought to be very possible for some third party to write a Microsoft Word plugin to do absolutely seamless import and export of OO.o .SXW files .....

    If I had a copy of Windows and a copy of Office, I'd be having a go myself. As it is, I got clean three years ago and don't intend to relapse anytime soon. Someone else can have the glory.

    --
    Je fume. Tu fumes. Nous fûmes!
  17. Re:Feed me! by AttilaSz · · Score: 5, Informative

    OOo Writer has an "Export to PDF" menu point in the "File" menu. It is ideal for preservation of the format -- unless the receiving party needs to edit it, that is. But in vast majority of cases, just sending over something for people to read, PDF is sufficient.

    --
    Sig erased via substitution of an identical one.
  18. Monopoly "competition" by Anonymous Coward · · Score: 5, Insightful

    "I still don't see how were they illegaly forced out of the markets."

    The marketplace success of MS Office had little to do with the performance of the product. It had everything to do with:

    1. Withholding the Win32 programming interface from competitors as long as possible prior to the launch of Windows 95 (i.e until Office95 was nearly completed) so that they could advertise that only Office had 32-bit apps. This is a classic example of using a monopoly in one field (Windows) to obtain a monopoly in another field (office productivity software). This is unequivocally illegal under U.S. antitrust law.

    2. Bundling agreements to get as many PCs as possible pre-loaded with Office, particularly for business use. These agreements contained strong financial incentives (in the form of discounts on Windows licensing) for offering consumers only Microsoft products and not any competing software (believe me, I know, sayeth the AC ;). This was also illegal.

    3. Obfuscated and changing file formats that ensured that competing products would not be able to read the latest versions of Office files. Once MS killed off all of the competition, this tactic lost momentum, because MS was largely competing against older versions of their own software, and people became worried that upgrading to newer versions would make their older PCs (running Office 97, for example) unable to interchange files with newer computers. This tactic is not inherently illegal, as far as I know, but it could have been legitimately prohibited as part of a remedy after Microsoft's antitrust conviction, and (to get back on topic) is clearly something that could legitimately be prohibited in government specifications for acceptable software.

    So, yes, my idea of "free and fair competition" allows one company to attempt to "outperform/outmarket" another, but only if they obey the law. Microsoft did not obey the law.