shaver asks some interesting questions about Microsoft and legal liability

First off, I Am Not A Lawyer And This Is Not Legal Advice. If you go to Microsoft (or to anyone) and say ‘but this law student on a blog told me so’ then you will be laughed out of the room, or sued, or both, and you’ll deserve it. :)

Mike Shaver blogged early this month about Microsoft’s new tactics in the HTML5 discussion– basically, that ‘we can’t do that because our customers will sue us for not being backwards compatible.’

I should start by saying this is not completely implausible. If your sales guys told your customers ‘this will always be compatible until the end of time’, or your sales contract said the same, then yes, you could possibly be sued for violating the terms of the contract under either circumstance. And of course (especially with large customers) contracts may not be the standard ones we’re used to seeing- months or years of salesmanship and legal work can go into such deals, with extensive custom promises and clauses involved. Without knowing exactly what was said, and/or exactly what contracts were signed to, it is impossible to know whether or not Microsoft’s claims have merit- reading their standard EULA terms would be insufficient.

Note that Mike asks specifically about EULAs; I’ve specifically mentioned sales guys as well as EULAs/contract because in some cases/states/jurisdictions/etc., verbal commitments not reflected in the contract can be interpreted as part of the contract. This is generally not the case, and in fact a well-written contract will go to great pains to ensure that this is not the case. But despite such efforts, sometimes those verbal terms can make their way into court- which makes answering a question like this with a simple ‘yes or no’ even more difficult.

Of course, if your sales guys said that, or your lawyers wrote it into the contract, probably someone should be fired for gross incompetence. It certainly shouldn’t be in the standard contract- opening yourself up to liability to millions of people would be insane. It might make it way into a custom contract, but unless your competitors are so dumb as to make the same promise, and hence force you to write a custom clause promising such a thing, then there is no good reason to promise such a thing. This is software, and backwards compatibility breaks, even at Microsoft. Lawyers and/or sales guys who make such promises are creating liability where there shouldn’t be any, and that is a cardinal sin. Microsoft may be many things, but they aren’t incompetent, particularly on the legal side. So- it isn’t impossible they could have created such liability for themselves (particularly in a deal with their biggest customers) but it is unlikely.

Outside of what Microsoft may have done to themselves with their contracts or actions, it is possible a court system could write such a term into a contract. This is basically how minimum warranties of product quality are created by governments- the government says ‘but of course you’re liable for X, regardless of what the contract says’, and then boom- you’re liable. But in the US the trend is to allow contracts to ‘opt out’ of such terms, and even where that is not the case, it seems unlikely (given the presumption that software is not compatible) that a court or a legislature would create such a huge responsibility- no matter how reasonable the idea might be, any court that tried would quickly have the entire software industry weighing in on the other side.

Finally, keep in mind that Microsoft has every incentive to fight this legally. If a customer of theirs goes to court to say ‘we are owed money because this product was not backwards compatible’, Microsoft would fight it utterly and completely tooth and nail- any court which read that term into a Microsoft contract would create huge liability for Microsoft for every succeeding product release they ever did. So the incentives cut strongly in favor of Microsoft fighting this tooth and nail (unless the liability comes from a custom-written contract which is so specific that it wouldn’t extend to other customers.)

Now, Microsoft certainly has a hard-earned reputation for backwards-compat, and they have every reason, from a marketing perspective, to fight to keep that reputation. But to answer your question, Mike, it seems possible but highly, highly unlikely that there is legal liability.

[Ed. later: see also my response to Mike in comments, on the question of whether or not this type of liability is something Mozilla should be worried about.]

10 thoughts on “shaver asks some interesting questions about Microsoft and legal liability”

  1. Luis Villa’s Blog / shaver asks some interesting questions about Microsoft and legal liability4 hours ago wearehugh : Luis Villa’s Blog / shaver asks some interesting questions about Microsoft and legal liability – basically, microsoft is either full of shit or has insanely incompetent lawyers. dunno about you, but i’m leaning towards

  2. I think I’d like to be the first to say, who the hell cares if microsoft gets sued, its not exactly a new thing :) and either way they can hardly use that as a defense for not updating an antiquated standard.

  3. Robert: it should have been about 1/2 the length, on re-reading. As we all know, that takes much more time. ;)

    Karl: if you’re trying to deal with someone in good faith, you sort of have an obligation to not get them sued if you can. I think implicit in Shaver’s question was ‘is Microsoft dealing with us in good faith’ or ‘do we need to deal with them in good faith’; you can draw your own conclusions on that after this post.

  4. Thanks, Luis; that’s a great read. I know we need to deal with the standards groups in good faith, and I’m not sure it helps us much to determine whether or not MSFT is doing the same. (I have my suspicions, but they don’t really help inform decisions.)

    I was mostly wondering if this is a concern that Mozilla or other browser developers should have as well — if Microsoft has created their own liability through custom contracts, as you say, then that’s their unusual bed to lie in, and not a burden that should be imposed on the rest of the process or industry.

  5. I was mostly wondering if this is a concern that Mozilla or other browser developers should have as well

    Oh! That’s not how I read it at all, though your second question (that I deliberately glossed over here) should have tipped me off.

    The ‘I am Not A Lawyer’ and in particular ‘I Am Not Your Lawyer’ disclaimers apply in full bloom here.

    First, all of the things above should apply to you. As long as you’ve made no special deals with particular customers, you’re probably in fairly good shape. The rest of the industry would surely join in supporting you if a case came to court.

    Second, I’ve never seen or heard of anything cases like this, though admittedly have not looked hard for it nor taken any applicable courses.

    Finally, you’re not selling anything, so even if there were court-created liability, it isn’t clear what kinds of damages you’d be liable for. Courts are still fairly sensitive to ‘get what you pay for’-style arguments, and I have to imagine they’d be particularly sensitive in the FLOSS context. So it is entirely possible a court could say ‘Mozilla is liable… for a zero dollar penalty.’

    But yeah… definitely recommend talking to Your Lawyers about the question before one goes about blithely relying on my opinions on this. Vast difference on my part between saying ‘you should be suspicious of another party’s claim’ and ‘hey, you’re fine, don’t sweat it!’

  6. Luis: The following is a comment I just posted on Shaver’s site… I’m cross-posting here just to make it easy to read.

    As others have said, if backwards compatibility was a claimable issue, Microsoft would be out of business by now.

    The only way that Microsoft (or any other organization) would be liable for this would be if they contractually agreed to such a constraint. And, having been working with Microsoft’s agreements for over a decade, I can tell you without a doubt that they don’t have this in their template (and that they don’t come too far “off” their template, even for REALLY big deals).

    The net-net on this is that unless there’s a larger agreement in place (for example, if Microsoft has an agreement with the W3C to keep IE compliant with the standards), Microsoft has ZERO liability (of any sort).

  7. Very amusing negotating tactic. Kind of “i’ll have to ask my wife” on steroids. I just love the idea that the entire industry’s standards making efforts would have to conform to unknown commitments made by Microsoft sale people.

Comments are closed.