decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books
Your contributions keep Groklaw going.
To donate to Groklaw 2.0:

Groklaw Gear

Click here to send an email to the editor of this weblog.


To read comments to this article, go here
Microsoft Files Emergency Motion to Stay Execution of Judgment in i4i
Sunday, August 16 2009 @ 08:00 PM EDT

Microsoft on August 14th filed a sealed motion, in response to the August 11 judgment and injunction against it in i4i v. Microsoft. I can't show you a sealed motion, obviously, but here's the docket entry, to at least give you a clue:
415 - Filed & Entered: 08/14/2009
Sealed Motion
Docket Text: SEALED MOTION Microsoft's Emergency Motion To Stay Execution of Judgment and Waive Bond Requirement by Microsoft Corporation. (Attachments: # (1) Exhibit A - Damon Declaration, # (2) Text of Proposed Order)(Kudlac, Kevin)
I've been seeing a lot of experts saying how easy it will be for Microsoft to work around the ruling, but I gather Microsoft is of a different opinion.

If you recall, there was a final judgment [PDF], which referenced an injunction, and then separately there was a permanent injunction [PDF], which set forth the terms.

By stay of judgment, then, I assume they are referring to the first item, about the money Microsoft is supposed to pay i4i, but it's not clearly the case, in that the judgment includes reference to the injunction.

Microsoft is the sealing-est litigant ever. Even the exhibits attached to Microsoft's motion are sealed, including the proposed order, so all we can do is guess. Here's mine: Microsoft would like a stay on paying the money, while it appeals, and so would you want that. Whether it gets it from East Texas... well, stay tuned.

It's impossible for me to know from just this entry if it also asks for a stay of the injunction. I would, if I could, if I were Microsoft. But Patently O says you can't get a stay of an injunction easily, that there is no automatic right to a stay on that:

Stays pending appeal: Under the Federal Rules of Civil Procedure, Microsoft has a right [to] obtain a stay of relief pending appeal after it posts an appropriate bond. However, that right only applies to monetary damages. There is no right to stay injunctive relief pending appeal. On occasions, both District Courts and the Federal Circuit will stay injunctive relief pending the outcome of an appeal.

Like I say, this is all guesswork, but my point is this: to anyone out there thinking that Microsoft won't fight, I think this indicates that it will. One way, obviously, is by an appeal, and that's the big-picture significance I get from this filing, particularly the request for waiver of a bond. I think it is confirmation that when Microsoft said it would appeal, it meant it.

Speaking of opinions about this litigation and the underlying patent claims, Rob Weir has a great piece on how not to read a patent. Thanks to the CC license, I can reproduce it here. He mentions something called a Markman hearing, in connection with explaining how to interpret claims. In this case, there was a Joint Claim Construction and PreHearing Statement [PDF], that will at least give you a ballpark idea of what he's talking about. Of course, some of you should avoid reading about this or all patents, so I'm providing it only for those who are free to explore.

**************************

How Not to Read a Patent, by Rob Weir

There is perhaps no occasion where one can observe such profound ignorance, coupled with reckless profligacy, as when a software patent is discussed on the web. Note the recurring pattern, which is repeated every two weeks or so. A patent issues, or a patent application is published or patent infringement suit is brought, and within minutes the web is full of instant pundits, telling us what the patent covers, how it should not have been granted, how it is entirely obvious, or how it applies to everything in the world, and how it presages a self-induced mutually assured destruction that now leads us on to the plains of Armageddon. If I had a nickle for every time this happens...

By way of disclaimer, I am not a lawyer, but I am blessed that my self-avowed ignorance in this area is coupled with a certain knowledge of the limits of my understanding, a handicap seemingly not shared by many other commentators. I know what I do not know, and know when to seek an expert.

In the past few days we have had a bumper crop of pontification on the significance of two XML-related patents, one nelwy issued to Microsoft (7,571,169), and another older one (5,787,449) owned by i4i, whose infringement has resulted in a large judgment and injunction against Microsoft. I've found the web coverage of both patents to be an unmitigated muddle.

I'm not going to comment on the merits of either one of these patents, but I'd like to make a few basic observations that may be of some assistance to those who comment on future patent issues.
  1. A patent has a description known as the "specification". And it has a list of numbered "claims". Although the specification can define terms that are then referred to in the claims, it is the granted claims that define the scope of the patent, not the specification.
  2. If all you do is read the abstract and the first few paragraphs of a patent, then you may know the general topic of the patent, but you do not really know its scope. If you then go off and cry, "Oi vey, this patent covers XHTML, SVG, RDF, Pringles and Obama Healthcare Plan" then you do your readers a disservice. You must parse the very specific and often obtuse language of the claims in order to understand exactly what a patent covers. There is no short cut. This is not like a book where you can understand the plot by reading the back cover. But over and over again, I see people who just read the abstract, maybe glanced at a diagram, and then feel equipped to hold forth at length on the substance of the patent.
  3. When you try to understand patent claims, you will encounter a dense form of legal English. Claims are not written for a layperson and do not presume that you will understand it easily. The drafting of patent claims is a black art, like writing device drivers, and if you are not versed in its intricacies, then your statements on any given patent are apt to be wide of the mark. Claims are full of magic words. Know what you do not know. If you do not recognize at sight and know the interpretation requirements of a means-plus-function claim (which is key in the '449 patent), or you are not crystal clear on the distinction between the verbs "consist" and "comprise", then you probably should not be the first (or loudest) person to speak on what a patent claims.
  4. If you are reading an application, know that during the "prosecution" of that patent, when it is reviewed by the USPTO, some of the claims of the patent may be thrown out, for any of several reasons, including prior art identified by the examiners. However, the specification of the patent is unlikely to change much. So an issued patent often has a very broadly-written specification, that covers the entirety of the originally claimed invention, though the the issued patent might have only a subset of the original claims allowed. So if you are have an issued patent and you look at only the specification, you can easily be fooled into thinking it covers far more than it does. For example, the '169 patent from Microsoft had half the original claims thrown out in the prosecution. If you don't know that and are reading only the specification, not the granted claims, then you will incorrectly think the patent is far broader than it actually is.
  5. Know what a priority date is, and how that is affected by a continuation. I've read all sorts of nonsense based on not appreciating that. Take a look at the '169 patent, for example. It says it was filed in 2004. But if you look closely you see it was a continuation of a 2002 application. You can moan and groan all you want about prior art, but if you don't get your dates right you're off to a bad start in your analysis.
  6. In an infringement suit, like with the '449 patent, be sure to look at the actual court record. Typically there is a Markman (claim construction) hearing, where the court will determine the meaning of terms used in the patent claims. If you have not read the court's claims construction opinion in the i4i versus Microsoft case, then your commentary is uninformed by probably the most important document in this case (well, next to the patent itself).
Well, that's enough for tonight. Repent. Sleep on it. And realize that making sense of a complex patent takes time, if you're going to do it right. Ergo, the first impressions you read from the instant pundits on the web will tend to be shallow, imperfectly informed and often wrong. Heck, even everything I said in this post may be wrong.

  View Printable Version


Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )