Slashdot Mirror


MS-Sun Agreement Leaves Opening For OO.org Suits

newentiti writes "We all know Microsoft paid $900,000,000.00 to Sun and they also signed a LIMITED PATENT COVENANT AND STAND-STILL AGREEMENT. The agreement basically states that Microsoft will not sue Sun for any patents for the next 10 years and vice versa. What's really interesting is that according to this story the agreement had a special provision that lets Microsoft sue anybody, including Sun, over OpenOffice.org. I wonder what Microsoft had in mind?"

89 of 407 comments (clear)

  1. Lawsuits ala Lindows by netcrusher88 · · Score: 5, Funny

    Maybe Microsoft wants to sue them for the "Office" part? Appearently they thought they could sue Lindows for the "indows" part...

    --
    There's an old saying that says pretty much whatever you want it to.
    1. Re:Lawsuits ala Lindows by Agent+Green · · Score: 2, Funny

      Nah...They want to sue them for the "Micro" part...so we'll have Sun Systems when it's all said and done. :)

      --
      // Agent Green (Ian / IU7 / KB1JQO)
      // IEEE 802.3: All 10base Are Belong To Us
    2. Re:Lawsuits ala Lindows by johnnyb · · Score: 4, Insightful

      I honestly think that this was just because Sun doesn't necessarily have a say in what goes into OpenOffice.org. Without this, the open-source world could simply just stick any technology into the OpenOffice.org codebase, and viola, Microsoft can't sue for infringement. I'm not a fan of software patents, but I think this really does make sense from a legal viewpoint, and is not necessarily an underhanded legal move by Microsoft.

    3. Re:Lawsuits ala Lindows by MikeMacK · · Score: 4, Funny

      No, I think it's the "Open" part that bugs them the most.

    4. Re:Lawsuits ala Lindows by Senjutsu · · Score: 4, Informative

      File formats are not patentable, trademarkable or copyrightable. However, certain algorithms used to generate their contents may be patented.

    5. Re:Lawsuits ala Lindows by Halo1 · · Score: 4, Insightful

      You think wrong. Copying (source or object code) is covered by copyright. Patents apply even if you developed something entirely on your own in a remote cave on a desolate island. No distinction is made between software and other things in US patent law. Reverse engineering has nothing to do with patents either, that's covered by copyright as well (and at least in Europe is explicitly allowed for interoperability purposes, I don't know about the US).

      --
      Donate free food here
    6. Re:Lawsuits ala Lindows by FlutterVertigo(gmail · · Score: 3, Interesting

      I don't know if the approval has occurred yet or not, but Microsoft did apply for a patent to cover the XML format of their Office files. They obviously want to make it so no one can create software to write new Office files. I would presume reading them wouldn't be an issue because you aren't creating a structure which would be compatible with their file.

    7. Re:Lawsuits ala Lindows by BlueTooth · · Score: 2, Informative

      They would have to be selective with this. Its in their best interest for 3rd parties to be able to (easily) use the Office file formats, just as it is in Microsoft's best interest for 3rd parties to (easily) develop Windows software. Office is a ver extensable package.

      See: The Office Developer Center and XML in Office

      They lay it all right out there. I've done work in the past that required me to integrate with Office (i.e. web app needed to make current data from a DB available in Office formats) and their guide to the XML format not only made it possible, it made it really easy.

      --
      SPAM
    8. Re:Lawsuits ala Lindows by FlutterVertigo(gmail · · Score: 3, Insightful

      Nope. If Micro$oft is alone in any suits, they're just "being Microsoft". If someone else is with them, "it must have merit".

      Microsoft has started drafting talent they think can teach them the mindset of OS. Unfortunately, Microsoft is so set in their ways WRT capitalism (to an extreme) they don't know how to deal with things which aren't done for the [sole] purpose of money. They seriously do not know. They've tried to employ the overused FUD by making the suits think ownership is an issue because someone can write code, sell the package and the source, the new owner can modify the source, sell the result and the source, etc. This bothers Microsoft - again, they don't understand this and it bothers them. It's like trying to sleep with sand in their bed and they can't sweep it out. And that just makes them more frantic. So now they're going to look at the same ownership cycle and throw the law at it. The question is: why should they care? They're selling things, OS folks are selling things.

      Perhaps they feel they can compete on that one level but worry all subsequent "generations" of the OS making the repeated sales + builds somehow threaten their business model? If so, they're going to have to admit they've lost a competitive edge. That won't bother them because that then removes the label monopoly.

      How can you have a monopoly if you don't always (or nearly always) have the competitive edge [on the grand scale]?


      Just remember...
      ______________________________________
      My Trunk Monkey can beat up your Trunk Monkey.
      http://www.suburbanautogroup.com/ford/trunkmonkey. html

    9. Re:Lawsuits ala Lindows by Theatetus · · Score: 4, Informative
      but I thought that if, say, OO.org develops their own version of features that M$ has, then it's not patent infringement (for software) if they didn't copy the source, reverse-engineer, or rip any data.

      Nope, that's how trade secrets work. A patent is a state-granted artificial monopoly on a certain device/technique/whatever that applies regardless of how any other party develops it. This is why patents are not secret -- in fact, anything you patent must be published and available to the public (IIRC, this includes source code or at least pseudocode for software patents).

      If I have a trade secret (which, along with copyright, were the "traditional" ways software IP was protected), I have legal protection against corporate espionage and certain types of reverse engineering. But, if someone develops a device or technique that duplicates my trade secret on his own, he can use it. This is in contrast to a patent, where I must give all of my competitors the specifications of my device or technique in return for legal protection from their implementing such a device or technique without a license from me.

      --
      All's true that is mistrusted
    10. Re:Lawsuits ala Lindows by Jim_Maryland · · Score: 3, Interesting

      Check out MS Office 2003 XML Reference Schema Frequently Asked Question for details on licensing. In particular, expand the section on How much does the license cost?. Another FAQ ask If Microsoft obtains a patent for the Office 2003 XML Reference Schemas, does that in any way affect the royalty-free license? and the response is No, the license is unaffected. Under the patent license for the Office 2003 XML Reference Schemas, Microsoft offers royalty-free rights both to its issued patents and patents that may be issued in the future.. IANAL but this seems to allow for open source projects to use the schemas.

    11. Re:Lawsuits ala Lindows by ColdGrits · · Score: 3, Informative

      " I like to explain it this way... copyright covers the implementation while patents cover the idea itself."

      Not true.

      You specifically can NOT patent an idea. You can on;y patent methods of imnplementing an idea. Your patent must describe in detail everything necesasry to recreate your specific implementation (although you can cover many different implementations of the same idea within the one patent).

      That is why patents describe "A method for blah blah blah" - it's the methods which are patented, not the concept of blah blah blah itself.

      A subtle but VERY important difference.

      --
      People should not be afraid of their governments - Governments should be afraid of their people.
    12. Re:Lawsuits ala Lindows by Lodragandraoidh · · Score: 2, Insightful

      Because Sun has the deepest pockets. Who else will they sue for OpenOffice? The developers, most of who make much less than the cost of pursuing such a case?

      Finally, Microsoft would lose for many reasons (prior art, fundamental differences between the implementations etc...)

      --

      Lodragan Draoidh
      The more you explain it, the more I don't understand it. - Mark Twain
    13. Re:Lawsuits ala Lindows by Reteo+Varala · · Score: 3, Insightful

      Actually, there's a very apt quote from the movie the American President:

      "I'd been operating under the assumption that the reason Bob spends so much time and energy shouting at the rain was that he simply didn't get it. Well, I was wrong, Bob's problem isn't that he doesn't get it; Bob's problem is that he can't sell it. We have serious problems to solve, and we need serious people to solve them. And whatever your particular problem is, I promise you, Bob Rumson is not the least bit interested in solving it. He is interested in two things, and two things only: making you afraid of it, and telling you who's to blame for it. That, ladies and gentlemen, is how you win elections."

      Replace Bob Rumson with Microsoft, and you have a clear match.

    14. Re:Lawsuits ala Lindows by Java+Pimp · · Score: 4, Informative

      how do you explain problems with GIF and JPEG file formats...

      I believe the big issue was with the patented LZW compression algorithm that GIF uses rather than the file format itself. Here's the first link I found on Google.

      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    15. Re:Lawsuits ala Lindows by Hinhule · · Score: 2, Funny

      Yeah, mom always used to tell me to "Close the doors/windows/etc there is a draft!"

      Microsoft obviously doesn't want a draft.

    16. Re:Lawsuits ala Lindows by baggins2002 · · Score: 3, Funny

      So maybe we could make a OO template for all of the documents required to file suit in the United States. And then write a script which uses these templates to create a completed document.

      #perl FileLawsuit.pl
      Which State? Washington
      Plaintiff? Geeks of America
      Defendant? Microsoft (forewith referred to as scumbags )
      Reason? Infringement of patented algorithm to
      create legal documents. Shown to have submitted
      legal documents with likeness of documents
      like those produced by the program FileLawsuit.pl,
      which is a patented algorithm.

    17. Re:Lawsuits ala Lindows by killjoe · · Score: 4, Funny

      replace "it" with terrorism and you get George Bush.

      --
      evil is as evil does
    18. Re:Lawsuits ala Lindows by budgenator · · Score: 2, Interesting
      Microsoft Says

      Q Can the licenses for the Office 2003 XML Reference Schemas be used by open source developers?
      A Yes. You can distribute your program in source code form. But, note that the patent and copyright provisions in the license for the Office 2003 XML Reference Schemas require you to include a notice of attribution in your program.
      Q. If Microsoft obtains a patent for the Office 2003 XML Reference Schemas, does that in any way affect the royalty-free license?
      A. No, the license is unaffected. Under the patent license for the Office 2003 XML Reference Schemas, Microsoft offers royalty-free rights both to its issued patents and patents that may be issued in the future.

      Now I haven't done a lot of digging, but I suspect that the licenses are non-transferable( the web site does imply they are), so if your Using OO you might want your legal people look at the terms of the license and get your own licence.
      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  2. Objective by Scoria · · Score: 3, Funny

    I wonder what Microsoft had in mind?

    Why, global domination, of course!

    --
    Do you like German cars?
    1. Re:Objective by justsomebody · · Score: 2, Funny

      I think that I'm much more in favour of "Pinky and the Brain" than "Steve and the Bill" kind of domination.

      At least cartoons made more sense than Microsoft publications.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    2. Re:Objective by TheSpoom · · Score: 5, Funny

      Are you pondering what I'm pondering, Pinky?

      Well I think so, Brain, but didn't SCO already patent that way of doing business?

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
  3. Perhaps... by Mr+Guy · · Score: 3, Funny

    including Sun, over OpenOffice.org. I wonder what Microsoft had in mind?"

    I'm going to go out on a limb here, and say, perhaps, suing?

  4. Hardly seems sinister by Dav3K · · Score: 5, Insightful

    Please notice that items like Star Office ARE included in the agreement, so I don't think this belies any patent cases against end-users. The biggest difference between Star Office and Open Office is that one is under the control of Sun, and one is not (or at least less-so). Therefore, Sun would obviously not want to be held responsible for things beyond it's control, such as outside coders blatantly putting in patented/copywrited material into Open Office.

    1. Re:Hardly seems sinister by parcel · · Score: 2, Insightful

      The way I understand it (after RTFA) is that Sun would have been protected from responsibility for OpenOffice only if it had been written into the agreement. So, by not including OpenOffice in the agreement, Sun could (theoretically) be held responsible for OpenOffice.

      I can't think of any other reason for this exclusion to be made other than Microsoft planning legal action against someone related to OpenOffice. It seems very odd to me that an OpenOffice clause would be written into this agreement with Sun, since it doesn't seem like Sun could be held liable for anything that OpenOffice does anyways. This is where I could be wrong... I couldn't find on openoffice.org what kind of ties to Sun remain, so I'm assuming there are very few if any.

    2. Re:Hardly seems sinister by silicon+not+in+the+v · · Score: 2, Insightful
      The fact is simply that for some reason, Open Office was not included in the covenant (either because Microsoft insisted on this for some reason, because Sun didn't care enough for some reason or a combination of the two).
      The "reason" is fairly simple. Sun doesn't own OpenOffice.org. Therefore, they have no right to make any decisions for them or sign any contracts on their behalf. OpenOffice.org originally came from Star Office at the point at which it was released open source, but OOo was completely independent from that point on, and has developed on its own.
      --
      We may experience some slight turbulence and then...explode. -Capt. Mal Reynolds
  5. Possible Simple Explanation by donscarletti · · Score: 5, Insightful
    It could simply be that Microsoft does not trust the open source community not to flagrantly disregard all microsoft patents when modifying OO.o if they were given immunity from civil action.

    That said, I this is Microsoft and their legal actions have rarely been that benign in the past.

    --
    When Argumentum ad Hominem falls short, try Argumentum ad Matrem
    1. Re:Possible Simple Explanation by iamdrscience · · Score: 2, Interesting

      While that is true, and is one of the more sensible explanations provided so far on here, it still doesn't quite answer all the questions. Wouldn't Microsoft want to avoid all Open source projects from Sun disregarding their patents?

      More importantly though, this path of thinking brings up some disturbing ideas in my head about ways GPLed projects could be controlled. Example: Suppose a company decides to start a GPL/BSD/etc. licensed project and this company has many software patents, and/or a cross-licensing agreement with another company that has a number of software patents. Since this project was started and is maintained by the company, it can obviously use their patents, but if somebody else decided they wanted to fork this GPLed code, they would not be allowed to without removing the patent infringing code, correct? Even if they are, it's somewhat of a legal grey area, is it not?

    2. Re:Possible Simple Explanation by OoSync · · Score: 2, Insightful

      It could simply be that Microsoft does not trust the open source community not to flagrantly disregard all microsoft patents....

      As a general rule-of-thumb, this is already true of most FOSS developers. Let developers concentrate on technology, let the lawyers concentrate on patents.

      Well, its true except for the "flagrant" part, as I'm pretty sure most FOSS developers don't know about patents in their relevant products.

      --

      I always get the shakes before a drop.
    3. Re:Possible Simple Explanation by deck · · Score: 3, Informative

      NO! The GPL expressly prohibits distributing code that is encumbered with a patent. If GPL code is released with something under a software patent, then the use of that patent must be allowed where ever that code goes.

    4. Re:Possible Simple Explanation by antiMStroll · · Score: 2, Insightful
      "...Microsoft does not trust the open source community not to flagrantly disregard all microsoft patents when modifying OO.o..."

      They don't have need to rely on trust, they can see the code. LGPL, remember?

  6. Office is their cash cow obviously by Serveert · · Score: 2, Insightful

    They want to leave any dirty trick open just in case.

    --
    2 years and no mod points. Join reddit. Because openness is good.
    1. Re:Office is their cash cow obviously by netcrusher88 · · Score: 3, Funny
      Office is their (cash) cow
      Beef...it's what's for dinner
      --
      There's an old saying that says pretty much whatever you want it to.
  7. Sec Doc by mlmitton · · Score: 3, Informative

    Here's the original SEC document: http://sec.gov/Archives/edgar/data/709519/00011931 2504155723/dex10109.htm

    --
    "My girlfriend's got sodium laureth sulfate hair."
    1. Re:Sec Doc by mlmitton · · Score: 2, Informative

      Oops--there's an extra space between the 1 and 2. Should have checked the link. I'l try again: http://sec.gov/Archives/edgar/data/709519/00011931 2504155723/dex10109.htm

      --
      "My girlfriend's got sodium laureth sulfate hair."
  8. Holy #$#@$ by Anonymous Coward · · Score: 3, Insightful

    visa versa

    Jesus Christ. How hard is it to use simpler terms if you don't know that the *complex* ones mean? Lets atleast try to keep it a little professional editors. Please.

    1. Re:Holy #$#@$ by OrangeTide · · Score: 4, Informative

      What is up with people saying 'visa versa' rather than 'vice versa' (pronounced VICE-uh VERSE-uh, but I hear no -uh on VICE more often, which I think is okay)

      vice/vix is latin for position. I don't think visa is anything in latin, or if it is I don't think it would make sense.

      No dictionary lists 'visa versa' or 'visa verse'. Most of them list 'vice versa'. I wish I knew why so many people say/spell 'visa'. (I'm guessing they say "vice-uh", and think it's spelled 'visa'. but in english visa would be 'vee-za')

      Here's a hint to everyone. Whenever you use a word or phrase, even a simple one you've used since you were a child. Look up it's meaning. It only takes a few minutes and you can use language more effectively if you have a more precise idea of a word's meaning. If you do this consistently, when you go to look up "visa versa" and find it's not there you'd realize the mistake. :)

      --
      “Common sense is not so common.” — Voltaire
    2. Re:Holy #$#@$ by Anonymous Coward · · Score: 4, Funny

      visa versa

      Jesus Christ. How hard is it to use simpler terms if you don't know that the *complex* ones mean? Lets atleast try to keep it a little professional editors. Please.


      OpenOffice.org software download: free

      Patent agreement between Sun and Microsoft: $900,000,000

      Getting flamed by an AC for misspelling "vice": priceless

      There are some things money can't buy. For everything else, there's visa versa.

    3. Re:Holy #$#@$ by Gannoc · · Score: 2, Informative

      Here's a hint to everyone. Whenever you use a word or phrase, even a simple one you've used since you were a child.

      The one that always drives me insane is when people write "For all intensive purposes" when they mean "For all intents and purposes"

  9. It is simple - FUD by filesiteguy · · Score: 3, Insightful

    Microsoft is great at spreading FUD. They have a stated goal to rid the desktop world (since they can't compete on a server level) of other OS's. Hence, they wish to have us stop using OO. I personally say, bring it on.

    They can go ahead and sue a non-profit organziation. I wonder what kind of goodwill that'll bring.
    -----

    1. Re:It is simple - FUD by zymurgy_cat · · Score: 4, Insightful

      Uh, shouldn't any for-profit company want to grab the largest market share they can? Of course they want to be #1. That's good business.

      Actually, no. Companies that go for market share often lose sight of the most important thing: profitability. Granted, getting the most market share can lead to economies of scale, but the costs to get that market share (from reduced prices, marketing expenses, etc.) can easily swallow any increase in profits. This is one of the reasons why slashing prices to gain market share almost always results in lower profits.

      Smart, successful companies know when to walk away from market share in order to maintain profitability. Dumb ones blindly go for the "sell at a loss and make it up on volume" mantra.

      --
      -- Fugacity: Confusing chemists since 1908
  10. MS Earth by michael+path · · Score: 3, Funny

    I wonder what Microsoft had in mind?

    Rebranding the planet Microsoft Earth®

    1. Re:MS Earth by grunt107 · · Score: 4, Funny

      Well, there IS alot of Blue... Hmmm - How do you reboot a planet (Ctrl-Alt-Nuke?)?

    2. Re:MS Earth by maxwell+demon · · Score: 4, Funny

      As long as they don't remove the planet from the sphere of influence of the Sun ...

      --
      The Tao of math: The numbers you can count are not the real numbers.
    3. Re:MS Earth by Dirtside · · Score: 4, Funny
      Rebranding the planet Microsoft Earth®
      Would this leave us vulnerable to the Blue Sky of Death?
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    4. Re:MS Earth by silicon+not+in+the+v · · Score: 2, Funny
      Rebranding the planet Microsoft Earth
      Somebody already has an answer to that one. It's called MS Planet Exploder 5.0.
      --
      We may experience some slight turbulence and then...explode. -Capt. Mal Reynolds
  11. Change the name by BigDish · · Score: 5, Interesting

    IANAL, but it would seem to me if Sun changed the name of OpenOffice, this exemption for MS would no longer apply?

    1. Re:Change the name by Gaewyn+L+Knight · · Score: 3, Funny

      Just please don't let them change it to Firemoth or Thundercat!

      --
      Telcos have alot of dark fibre in the States. Most people assume that's optical fibre...but it's actually moral fibre.
    2. Re:Change the name by Dynedain · · Score: 2, Insightful

      Sun can't change the name of OpenOffice.org (the .org is part of the name btw). They can change the name of StarOffice which is their branded version of OpenOffice.org.

      And I doubt the legal agreements are so loose that simply changing the name of the product invalidates the contract. They pay the lawyers big money for a reason.

      --
      I'm out of my mind right now, but feel free to leave a message.....
    3. Re:Change the name by ricotest · · Score: 5, Funny

      IANAL

      With reasoning like that, you should be! I think you could really help SCO's case.

  12. Optimism by iamdrscience · · Score: 2, Funny

    Maybe I'm putting too much faith in Sun, but I'd like to think that if Microsoft sued OO, then Sun would help them out.

    1. Re:Optimism by Alsee · · Score: 2, Interesting

      According to the agreement Sun is required to be on Microsoft's side suing OO.

      Of course Sun is free to hire a second set of lawyers and join the other side of the case attacking itself. Sigh, what a sad sad commentary that that sentence almost makes sense.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  13. legal strategy? by belmolis · · Score: 3, Insightful

    Its pretty obvious that Microsoft wants to preserve their right to sue, but I'm surprised that the deal with sun provides an exception. If the two agree that there is a real prospect of Microsoft winning a suit over OpenOffice.org, I would think that Sun would want to be protected and would have held out until Microsoft agreed. And I would think that Microsoft would have agreed, if they really wanted the deal with Sun, perhaps with the likely damages subtracted from Microsoft's payment to Sun. So what this suggests to me is that Microsoft's legal strategy involves a suit in which for some reason it would be difficult to avoid naming Sun as a defendant but in which Sun does not anticipate actually have to pay any significant damages or litigation expenses. I'm not sure how this situation would arise - maybe a situation in which MS has to name everybody initially but would then drop Sun as a defendant after discovery?

  14. Respect Me in the Morning by 4of12 · · Score: 2, Funny

    I wonder what Microsoft had in mind?

    No wonder. It's clear that Clippy is going to sue erstwhile Office users under the "Alienation of Affection" provision of the EULA you clicked through so quickly under the heated passion of the moment.

    --
    "Provided by the management for your protection."
  15. Could be... by ElGuapoGolf · · Score: 5, Interesting


    What could happen is this...

    I remember reading that MSFT was going to tie some DRM into future versions of office... only "authorized" people could view documents. You'd, of course, need a MSFT policy server somewhere on your network to make sure you could set these permissions, and view documents, and all that good stuff...

    If OpenOffice decided to reverse engineer this, the loophole lets MSFT sue them.

    Does anyone remember the good old days when you could save your Word 6 doc, open it in WordPefect, and work on it there? Or, hell, when you could save your GeoWrite document, open it it Word Writer, and work on it there? What the hell happened?

    1. Re:Could be... by twos · · Score: 2, Insightful

      You can still do that, for the most part. Just save your documents in Rich Text Format.

      --
      Phear The Phat Penguin
  16. Server melting... by Anonymous Coward · · Score: 5, Informative

    Quote...
    According to the recently released financial documents to the SEC, besides the 900,000,000.00 being paid to Sun, a LIMITED PATENT COVENANT AND STAND-STILL AGREEMENT was also enacted.

    IV. PROVISIONS RELATING TO OPEN OFFICE

    1. Notwithstanding the other provisions of this Agreement, with respect solely to the product developed by Sun and generally known as Open Office, the Covenants of Section II above and the Releases of Section III above shall apply fully to Sun but shall not apply to Authorized Licensees of Open Office or any other third party. Accordingly, Microsoft shall not be foreclosed by this Agreement from seeking damages from Authorized Licensees of Open Office for copies of Open Office made or acquired prior to the Effective Date of this Agreement. Nor shall Microsoft be foreclosed from seeking any damages from Sun, its Affiliates, Authorized Licensees or any third party for any copies of Open Office made or deployed by a User after the Effective Date.


    So basically, while Microsoft will not sue Sun for any patents for the next 10 years and visa versa (Cross Licensing Agreement). Microsoft can sue anybody, including Sun over Open Office (Sun's Star Office is protected). This is probably as close as Microsoft can legally get to buying Open Office.

    The rest states that Sun has to give Microsoft legal aid in bringing lawsuits against users of Open Office. Also, Microsoft will pay Sun a confidential sum for its troubles for providing that legal aid.


    2. In the event that Microsoft elects to sue or otherwise seek recovery from an Authorized Licensee of Open Office for copies thereof that were made and deployed by a User prior to the Effective Date of this Agreement ("Deployed Copies"), upon request, Microsoft agrees to promptly reimburse Sun for any reimbursable Damages. Sun shall promptly notify Microsoft of any Claim, shall provide Microsoft with the opportunity to take control over and responsibility for the defense and/or settlement of such Claim, and shall reasonably cooperate with Microsoft in litigating the defense of such Claim, including in all discovery and trial preparation efforts. Microsoft will not have any obligation to reimburse Reimbursable Damages unless Sun abides by the foregoing requirements. Microsoft shall also be relieved of its obligation to reimburse Reimbursable Damages if Sun breaches any warranty in Section VII.4. As a condition to accepting control and responsibility for such defense, Microsoft shall acknowledge in writing that such third party claim constitutes a "Claim" and, as such, would give rise to Reimbursable Damages if determined adversely. In the event that Microsoft accepts control and responsibility for such defense, Sun shall be entitled to participate in such defense at its own cost. "Claim" means any claim that Sun is liable to indemnify or otherwise reimburse any Authorized Licensee or third party for damages it has been ordered to pay by final judgment or settlement arising from a claim asserted by Microsoft against such Authorized Licensee or third party that any Deployed Copy of Open Office infringes any patent of Microsoft. "Reimbursable Damages" means the amount of any adverse final judgment awarded by a court of competent jurisdiction, or Microsoft approved settlement, against Sun that is based on the Claim.

    3. The Parties acknowledge that the product currently marketed by Sun as Star Office shall not be affected by this Section IV.


    LIMITED PATENT COVENANT AND STAND-STILL AGREEMENT

  17. Could Be by michael.teter · · Score: 2, Interesting

    Could be that MS does fear that OO will blatantly "steal" patented MS Office technology.

    Or it could be that MS has intent to sue OO after MS receives a patent for something novel (like using a Tab key to jump between items) and then chooses to sue OO for _stealing_ their critical technology.

    Sadly, I'm thinking it's the latter.

    --
    /Not for internal use/
  18. Re:Sun should get sued... by ravenspear · · Score: 2, Funny

    Yeah, because java is so much worse than .NET.

  19. FUD by fmaxwell · · Score: 4, Insightful

    The most obvious reason to have such an exemption is the FUD (Fear, Uncertainty, and Doubt) factor. Microsoft is probably deadly-afraid of small busineses (that will someday be big businesses) standardizing on OO rather than paying a king's ransom for MS Office licenses. By leaving these businesses to wonder if they will be sued or whether OO will disappear due to litigation, some of those businesses will consider ponying up the money for MS Office.

  20. OpenOffice is nothing to do with Sun surely?... by Numen · · Score: 4, Insightful

    Ummm, isn't OpenOfice administered seperate from Sun? In which case why would an agreement with Sun cover OpenOffice?

    One could equally say the agreement left open the possibility of suing people over Linux, or indeed washing machines.

    I doubt Sun wants to enmesh itself as responsible for washing machines anymore that they would OpenOffice... yes I understand where OpenOffice comes from, but ask yourself if you;d want blurry lines if you were Sun.

    Perhaps the spin on the reportage is a little askew. I'm not sure one can infer any intent on Microsofts part.... unless of course MS are planning on suing makers of washing machines.

  21. Sinister? Or SNL plot? by Roadkills-R-Us · · Score: 4, Funny

    Part of the analysis reads:

    The rest states that Sun has to give Microsoft legal aid in bringing lawsuits against users of Open Office. Also, Microsoft will pay Sun a confidential sum for its troubles for providing that legal aid.

    So, MS can sue Sun for using OO, and require Sun to help MS sue Sun, but then MS has to pay Sun for such aid???

    That series of stories could be almost as entertaining as te SCO Follies!

  22. visa versa? by spectrokid · · Score: 4, Funny
    Microsoft will not sue Sun for any patents for the next 10 years and visa versa.

    visa versa? is that like the back side of your credit card?

    --

    10 ?"Hello World" life was simple then

  23. Open Office vs. OpenOffice.org by Derf_X · · Score: 4, Insightful

    I RTFA, and it mentions Open Office, not OpenOffice.org, which are actually different things if I'm not mistaken. I wonder if the name difference would stand in court.

    1. Re:Open Office vs. OpenOffice.org by bvdbos · · Score: 2, Informative
      openoffice.org emphasises that open office is not the same as openoffice.org: Because of trademark issues, OpenOffice.org must insist that all public communications refer to the project and software as "OpenOffice.org" or "OpenOffice.org 1.0," and not "OpenOffice" or "Open Office."

      But the text says "generally known as open office" so here's a catch. On the other hand, Sun will never be able to remove code from openoffice.org:
      From thje openoffice.org website:
      3. Can Sun ever take away the code? The simple answer to this is NO. Once code is released under the LGPL, it can never be taken away. Once LGPL, always LGPL. Sun has no plans to return to a closed-development model. Sun is subject to the same rules as the rest of the community, including giving back modifications under the LGPL (or a specification and reference implementation under the terms of the SISSL). Thus, Sun can never take away the code and the community's contributions to it. This code belongs to the community as guaranteed by the LGPL and the SISSL.

  24. war of attrition by OklaKid · · Score: 5, Insightful

    they only way to deal with the tyrant of Redmond is a war of attrition...
    no quarter, no mercy, just cut em off completely, send msft to the recycle bin of history forever...
    msft is not to be trusted under any circumstances...
    this has already been done both in my office and at home...

  25. That's a April's fool joke by shailu · · Score: 2, Insightful

    Haven't you noticed agreement's effective date - This Limited Patent Covenant and Stand-Still Agreement (the "Agreement") is entered into as of this 1st day of April, 2004 (the "Effective Date") See this url http://sec.gov/Archives/edgar/data/709519/00011931 2504155723/dex10109.htm

    1. Re:That's a April's fool joke by timothv · · Score: 3, Insightful

      I don't think the SEC plays around with April Fool's jokes.

  26. What happened is... by Mike+Hawk · · Score: 2, Funny

    People wised up and realized that the internet is an evil place. Noone can be trusted. Least of all open source software users and developers. The only way to be secure in one's information is to trust MS and MS alone. Its really the natural evolution of things. Me thinks you doth protest too much.

  27. It may be reasonable after all by CTalkobt · · Score: 4, Insightful

    Consider that Microsoft may reasonably be looking after their own self-interest. In this case, I think it may be fair for them to try and prevent individuals outside of Sun to incorporate something into OpenOffice that is owned by them. I don't see it as a "pre-emptive" strike but merely a reservation of rights. Sun is still free to utilize what they wish for SunOffice - they just can't distribute it back to the open source community.

    This is not a troll. I don't like Micro$haft but I don't see this as the evil, bad thing everyone else says it is.

    What it will eventually boil down to is, how do they utilize (if they do) this provision?

    --
    There's a gorilla from Manilla whose a fella that stinks of vanilla and has salmonella.
  28. Visa versa by Espectr0 · · Score: 4, Funny

    visa versa

    I can see the VISA ad: "Because Microsoft won't take American Express"

  29. Not really important, except to Sun by euphorik_ · · Score: 2, Interesting

    I read that to say that MS has the right to seek damages (sue) from all those people who
    had something to do w/OOo before this agreement and after it. They'd still have to win a lawsuit
    that proved they incurred damages, possibly to IP, patents, who knows.

    So that little provision doesn't really change anything for users. It simply tells Sun
    that MS can sue them for actions they have taken (and future action they take) w/OOo regardless of
    this agreement not to sue them for 10 years.

    -euphorik

  30. Re:Sinister? Or SNL plot? by Phisbut · · Score: 2, Interesting
    I actually quite like a comment posted on the story that goes :

    Perhaps that is why the proper name is OpenOffice.org. To quote:
    Because of trademark issues, OpenOffice.org must insist that all public communications refer to the project and software as "OpenOffice.org" or "OpenOffice.org 1.0," and not "OpenOffice" or "Open Office."
    Perhaps the Sun lawyers pulled a fast one over Microsoft!

    Indeed... the quote comes from here, and it looks like it's been posted there more than a year ago. So technically, there is no such thing as OO or OpenOffice, there is only OOo or OpenOffice.org.

    I really wonder how well that can hold up in court.

    --
    After 3 days without programming, life becomes meaningless
    - The Tao of Programming
  31. Can Microsoft protect thier patents with DRM? by blackest_k · · Score: 3, Interesting

    There are two problems with open office,
    1) being the file requester interface it is ugly and scary to a lot of users.

    This is probably the first thing people see and it scares them word is like an old friend, even with clippy, they are familiar with it.

    2) Less than perfect conversion of word documents into and out of OpenOffice.
    word is a defacto standard, people see word compatability as essential since thats what is most commonly used.

    As long as word format import and export is less than perfect Openoffice is always going to be on the losing side.

    Microsoft are well aware the small problems with using anything other than their products keeps their user base. Should OpenOffice finally manage 100% word compatable import and export then there is certain to be a microsoft patient which can be used to hit openoffice and if there isn't they can just change the word document format just enough using incorperating a patented concept and then beat them with a big stick.

    Perhaps the only way to beat this is if openoffice kept its import and export filters as plugins and perfect word format conversion would be an unknown 3rd party written plugin.

    However even this might not be possible with DRM incorperated into Windows XP and Longhorn. Just as media player recognises infringing audio files it is probably no great leap to being able to isolate a patent infringing plugin.
    Windows update will be able to ensure that Microsofts patents can be protected

    Can Microsoft do this almost certainly, will they do this what do you think?

  32. I'd like to see it happen by Moth7 · · Score: 2, Insightful

    Major cock-up on the MS legal team's part - unless they wish to sue for inclusion of patented technology in a defunct product. No, I'm not trolling, it's just that the agreement mentions "Open Office" and not "OpenOffice.org" (the name OO.org had to take for trademark reasons). Unless their ambiguous wording ("the product developed by Sun and generally known as Open Office") would hold up in a court of law, they really have no-one to sue - unless they want to litigate against the product which got to the name first (highly unlikely).

  33. Hardly "funny"... by ites · · Score: 4, Interesting

    Insightful, yes.

    Microsoft make money from exactly TWO products. Windows, and MSOffice.

    Windows is under fierce attack from internet malware on the consumer desktop, and Linux in the enterprise. MSOffice is being eroded by the unbreakable OOo.

    I said this a while ago when Microsoft and Sun announced their happy settlement: the goal is to squash OOo. SCO and Lindows demonstrated that lawsuits are not just about recovering damages: the mere threat of litigation is enough to kill a product.

    OOo will not survive a SCO. It's not got enough grip yet. Microsoft must realize this.

    So: they will use a stick and a carrot. The stick: lawsuits against prominent OOo developers for patent infringement. The carrot: MSOffice for Linux. I predict within the next 6 months, since every day that OOo is free makes it harder for MS to squash it.

    And then... patents to make sure no-one can ever write a free office application again.

    "Illegal software" is going to take on a whole new meaning by this time next year.

    --
    Sig for sale or rent. One previous user. Inquire within.
    1. Re:Hardly "funny"... by sterno · · Score: 4, Insightful

      So: they will use a stick and a carrot. The stick: lawsuits against prominent OOo developers for patent infringement. The carrot: MSOffice for Linux. I predict within the next 6 months, since every day that OOo is free makes it harder for MS to squash it.

      MS Office for Linux is not going to happen. Microsoft's power comes through control of the desktop platform. If they ran office on Linux, a lot of people would lose their only reason for sticking with Windows. Besides, the vast majority of people using OOo are using it on Windows, not Linux.

      Sure their desktop is under assault from Internet malware but has this eroded their market share in the slightest? No. As long as the applications people want to run only run on Windows then Microsoft will continute to dominate the market. I hate Windows but I run it at home because the games I play don't run on Linux. As for Malware, I'm behind a firewall, and I don't use IE or Outlook so what do I care.

      --
      This sig has been temporarily disconnected or is no longer in service
  34. This clause doesn't apply by j-turkey · · Score: 4, Insightful

    According to one of the posts in the article, there is no such product called "Open Office" (4th post down as of 9/15/2004 6:00 GMT). The product mentioned in the agreement (legally speaking) may or may not refer to OpenOffice.org, which is what the news story is referencing. Why can a news story get it wrong and not a legal contract? Because legalese is all about semantics. News stories don't have to be to have a Slashdot discussion.

    The post in question states:

    Because of trademark issues, OpenOffice.org must insist that all public communications refer to the project and software as "OpenOffice.org" or "OpenOffice.org 1.0," and not "OpenOffice" or "Open Office."
    This is stated here, in the Trademark section (which they claim was last updated 2003-07).

    Did Sun's legal department pull one over on MSFT's legal department? Was it a mistake? Was Oo.o defined earlier and then said "referred to herein as 'Open Office'"? Was the agreement between Sun and Microsoft dated before the official communication of Oo.o? I don't know, but it appears to be pretty clever, and raises some intriguing questions.

    One way or the other, this won't stop me from deploying Oo.o. It's an excellent product, and saves $400 per PC (nearly 40% of the cost of a complete system).

    --

    -Turkey

    1. Re:This clause doesn't apply by Alsee · · Score: 3, Insightful

      Did Sun's legal department pull one over on MSFT's legal department? ...referred to herein as 'Open Office'

      No, and you should become very very worried if any judge lets you spend more than 30 seconds arguing it. If he does it's probably because he's already decided to rip your case apart limb by limb and is just looking for an excuse to stomp it into a bloody pulp and shove it down your throat one spoonfull at a time. Chuckle.

      A contract is an agreement of good faith intent. You, me, the judge, everyone at Sun, everyone at Microsoft, and everyone here on Slashdot knows that the item "referred to herein as 'Open Office'" is clear and obvious refference to Sun's OpenOffice.org. Any attempt by Sun to argue that the use of "Open Office" was a trick refference designed to deceive Microsoft would place Sun in a position of bad faith. Every other term and clause in the contract would then likely be interpreted in the light least favorable to Sun.

      For similar reasons, when there is a real and reasonable confusion in the meaning of a contract written by only one side (such as EULA's), those terms are generally interpreted in favor of the person who did not write the contract. You can't write confusing terms and then claim ownership of any car that uses your parking service.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  35. OOo = "Open Office" ! by ites · · Score: 4, Insightful

    There is no product called "Open office".

    The agreement refers to 'the product developed by Sun and commonly known as "Open Office"' and this most certainly refers to Openoffice.org.

    The name "openoffice.org" was chosen because "open office" was trademarked by some other company, but not for software.

    --
    Sig for sale or rent. One previous user. Inquire within.
  36. Here is the plan... by Anita+Coney · · Score: 3, Insightful

    We know that Sun cannot be sued by Microsoft for patent violations. We know that Sun is looking at buying SUSE Linux.

    When and if Microsoft unleashes its patent war against open source in general, against Linux and OpenOffice in particular, Sun and all customers of Sun will be immune.

    Thus, Sun will be the only company allowed to sell Linux and OpenOffice, aka, StarOffice and will be Linux's sole distributor.

    What does Microsoft get out of the deal? First, Microsoft does NOT want Linux destroyed. It needs to have at least the appearance of competition to keep government regulators off its back. That competition will come from Sun.

    Second, Linux will be greatly hobbled because instead of the entire world working on Linux, there will be only one source with which to compete.

    Basically, Microsoft will destroy Linux but keep the appearance of healthy competition in the marketplace.

    --
    If someone says he and his monkey have nothing to hide, they almost certainly do.
  37. File Format Troubles by mrbcs · · Score: 2, Insightful
    IMHO, this is where the DOJ should have slapped M$. Make them make their .doc format open. It is the defacto standard and is proprietary. This is ridiculous. This would stimulate competition and M$ would actually have to compete with someone.

    It would be so nice in a perfect world if users just used rtf or something a little more compatible, but that's not gonna happen any time soon. I think this is the single biggest threat to moving people off windows...they can't read their files.

    --
    I'm not anti-social, I'm anti-idiot.
  38. My USian friend... by hummassa · · Score: 4, Informative

    Some countries' laws (like my own) FORBID patenting of software. We will welcome OOo developers down here and treat them like kings, for our Large government is using more and more.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  39. Re:Have a reality check by sillybilly · · Score: 3, Insightful

    This isn't gonna work unless the rest of the world, and especially EU will do software patents. MS might be able kill Linux in the US, but it's no good if they can't kill it in the EU, and JP, and BR, and everywhere else. And right now there is a tremendous resistance against it in the EU, and different comittees are overturning each other's decisions. There is huge money in it, and there is a huge fight going on.
    Software patents go like this: the way of obtaining the number 3 by adding 2+1 is hereby patented. Therefore if you're in a school, you must do 3+0 or 4+(-1), unless you're willing to pay license for 2+1 additions, at $0.05/action. You're welcome to prove that it's prior art, if you got the lawyers, but beware, we got more lawyers and deeper pockets and we can drag it out for 10 years in court. We will patent the stupidest things, because the patent examiner is on our team, we regularly take him out to golf, plus we inundate him with so many stupid claims, that even if he tries to pick on the details and fight them one by one, something WILL get through, sooner or later, and what doesn't get through, we'll keep reapplying until it gets through, SOONER OR LATER.
    Real inventions don't happen in patents, they happen at universities, in published science articles, and they come out no matter what, out of ego, whether patented or not. Talk about stupid things patented like the 1-click shopping patent for amazon? Can you say "DUH?"

  40. people making money by kardar · · Score: 2, Interesting

    I think that the injustice that is sort of being looked at or thought about here is when an innocent yet enterprising group of individuals comes together and decides to make software, and then a large organization, or an opportunistic organization destroys the effort to their own, perhaps percieved, benefit.

    On the other hand, if such a group of enterprising individuals were to come together for the purposes of turning a profit, it is at least equally likely that they would choose Windows as a platform, and not choose open source or free because they have no desire to donate anything. There are plenty of enterprising individuals who would rather go with MS Windows, and to be honest, there are some good third party Windows applications out there.

    Therefore I doubt that Microsoft would do anthing that would start a patent war. They might be afraid of Oo.org, they may want to keep an eye or two on it, they may want to protect themselves, but I seriously doubt that they will attack it. The message that Micrsoft wants to send to the world, I think, is that if you want to make software, and not give it away for free, in other words... if you want to make software for profit, then choose our platform. If Microsoft were to unleash a patent wars on anyone - open source, free, they would be placing the stability of the entire software industry, and the reliability of their own platform as a "money maker", as a place where small enterprising software developers can feel confident they will be reasonably secure from ligitation, at risk. Microsoft might not be about giving away things for free, but by no means do they want to create a litigous atmosphere for those profit-driven individuals who choose to develop third-party applications for their platform.

    I say don't worry about it.

  41. Microsoft XML Schema Patent by soullessbastard · · Score: 4, Informative

    Disclaimer: I am a Mac OS X community developer for OpenOffice.org and a founding member of NeoOffice

    There is one obvious reason for this clause that I can think of off of the top of my head. Microsoft Office XP has a feature by which Office documents can be saved in an XML format. Obviously, this means that the information in the resulting Microsoft Office generated files is not as obfuscated as it is in a binary format (provided key information isn't just base64 encoded into elements). Microsoft knows this feature can negate the lock-in to .doc and other Office formats. So they were clever...

    Microsoft has patented their XML schemas. In order to write software that uses these Microsoft Office XML schemas, you must sign a patent license with Microsoft.

    Obviously, OOo will want to be able to open these new Microsoft Office XML formatted files similar to its support for the .doc format...but Microsoft has prevented anyone from using their patented schema in a "free as in beer" environment. These clauses in TFA allow Sun a cop-out: Sun can freely write code and use it in OOo that uses the Microsoft Office XML schemas. In the Sun-branded OOo distributions (Linux-x86, Solaris, Solaris-x86, Windows only...they have a Sun logo on the startup screen) Sun is free to use the patented Office schemas as well. Because of this, Sun will most likely contribute the code to work with these schemas into the core source code of OOo.

    Other companies make derivatives of OOo too (Red Hat, Novell/Ximian, BSDMall), individuals like myself, and even just translators non-Sun builds for mainline platforms who don't program at all. The Sun-MS agreement says that Sun's patent licensing for the Office Schemas does not apply to any OOo derivatives or builds that are done outside of Sun. Either all of these companies and individuals need to sign the Patent License Agreement with Sun or else they are open to lawsuits from Microsoft and potentially pay royalties to Microsoft in the future to use their schema.

    It's really another clever way Microsoft has come up with to continue to ensure their file formats remain closely guarded and their own property.

    As to whether a patent of an XML Schema can stand up in court, well, I know I personally as a single developer don't have the kind of money to challenge Microsoft on patent litigation if they sue me as an individual. Unfortunatley I have neither the time nor the skills to scrutinize all of Sun's contributions to OpenOffice.org's source code to see if they use Microsoft's patents in such a way that's legal for them, but not legal for me. I either must take my chances or stop being a non-Sun developer of OpenOffice.org. Unfortunately now any non-Sun entity working on OOo has to make that choice for themselves.

    ed

    1. Re:Microsoft XML Schema Patent by soullessbastard · · Score: 2, Interesting

      In order to contribute code into OOo that gets committed and incorporated into the main product, you (or your company) must file a Joint Copyright Form (warning: PDF. No HTML version is available). It is essentially dual-copyright assignment. Both you and Sun have a copyright to your contributions, so Sun can continue to do whatever they want with your contributions including relicense them under different terms.

      The work I've done in my projects outside of the OOo source code repository falls outside of the jurisdiction of the JCA. I and I alone own the copyright to that work and choose to license it as I wish.

      So no, I can't get recompense for anything I've contributed back into the OOo source code repository itself since Sun owns it too. If I find any of my other outside code in the repository and I myself haven't committed it there, then it's a violation of coypright provided it's not compatible with SISSL licensing.

      As OOo is LGPL licensed, the reverse isn't true...Sun can't do anything to me if I use the code in other outside projects, provided they're compliant with LGPL or SISSL licensing. Submarine patents, however, are a different story. Neither LGPL nor SISSL provide patent protection for derivative works.

      ed

  42. Re:File format's not patentable? Better tell Adobe by Senjutsu · · Score: 3, Informative

    >5,634,064

    Method and apparatus for viewing electronic documents

    >5,737,599

    Method and apparatus for downloading multi-page electronic documents with hint information

    >5,781,785

    Method and apparatus for providing an optimized document file of multiple pages

    Etc,etc. They're patents relating to the use and distribution of pdfs, rather than the format of the file itself.

  43. Beware OpenOffice Registration by edward.virtually@pob · · Score: 2, Informative

    A critical aspect not mentioned in the summary that users should be aware of is mentioned in this article:

    Not only is Microsoft allowed to sue any company.including Sun.for
    alleged patent violations connected with OpenOffice, but Sun is required to
    provide Microsoft with legal help in bringing such lawsuits against OpenOffice
    users.


    I.E.: When MS asks (and it will), Sun will be giving it their OpenOffice registration database. So unless you want to get sued later, beware of the answers you give when downloading (which you should do now while it's still available).