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?"
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.
I wonder what Microsoft had in mind?
Why, global domination, of course!
Do you like German cars?
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?
Never confuse volume with power.
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.
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
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."
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.
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.
-----
The Kai's Semi-Updated Website Thingy
I wonder what Microsoft had in mind?
Rebranding the planet Microsoft Earth®
There's an old saying that says pretty much whatever you want it to.
IANAL, but it would seem to me if Sun changed the name of OpenOffice, this exemption for MS would no longer apply?
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?
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?
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
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.
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.
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!
visa versa? is that like the back side of your credit card?
10 ?"Hello World" life was simple then
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.
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...
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.
visa versa
I can see the VISA ad: "Because Microsoft won't take American Express"
Open Source Java Web Forum with LDAP authentication
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?
Blarney Quality Restaurant, Plants
I don't think the SEC plays around with April Fool's jokes.
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.
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:
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
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.
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.
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
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?"
Disclaimer: I am a Mac OS X community developer for OpenOffice.org and a founding member of NeoOffice
.doc and other Office formats. So they were clever...
.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.
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
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
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
>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.