(Just started reading? See part 1, part 2, part 3, part 4, part 5, and part 6.)

Back in April I visited Washington, D.C.. I visited partly to pick up some bobbleheads at an opportune time (just before Easter, and just before visiting family nearly as far eastward from California) and partly to attend Supreme Court oral arguments while I had the chance. The two cases I saw argued were Tapia v. United States and Microsoft v. i4i Limited Partnership. Shortly after I made some minor predictions for the cases, following up on an introduction of the cases and thoughts from oral argument. Let’s take a look at how the cases turned out, before the October 2011 term arguments start. (At this point on Monday, October 3, there’s probably already a line outside the Supreme Court building for the first arguments of the term.) If you need a refresher on the cases themselves, read my introductions noted above: for space reasons I won’t review much here.

Tapia v. United States

The Court unanimously ruled for Tapia, deciding that a judge may not consider the availability of rehabilitation programs when imposing a sentence of imprisonment or in choosing to lengthen a sentence.

The opinion

Justice Kagan wrote the opinion for a unanimous Court. Tapia had been sentenced to 51 months in prison, seemingly because the sentencing judge thought she should take part in a particular drug treatment program: a program she’d only be eligible for if she were in prison for a longer sentence. Justice Kagan’s concluded that a sentencing court can’t impose a prison term, and it can’t extend a prison term when it has decided to impose one, to foster a defendant’s rehabilitation.

Justice Kagan first briefly reviewed the history of the Sentencing Reform Act which enacted the relevant statutes (displaying almost professorial affection in noting that, “Aficionados of our sentencing decisions will recognize much of the story line.”). She concluded that the Act was intended to make sentencing more deterministic and consistent by eliminating much discretionary authority during sentencing and prior to release.

Justice Kagan next turned to the text of the relevant laws. She examined the text of 18 U.S.C. §3582(a), which reads:

The court, in determining whether to impose a term of imprisonment, and, if a term of imprisonment is to be imposed, in determining the length of the term…shall consider the factors set forth in section 3553(a) to the extent that they are applicable, recognizing that imprisonment is not an appropriate means of promoting correction and rehabilitation.

Justice Kagan concluded that, “§3582(a) tells courts that they should acknowledge that imprisonment is not suitable for the purpose of promoting rehabilitation.” While Justice Kagan noted that the text could have been more commanding — “thou shalt not”, say — she thought that Congress had nonetheless made itself clear. Justice Kagan also considered the argument that the “recognizing” clause applied only when determining a sentence, not when possibly lengthening it. She rejected this argument, noting that standard rules of grammar argued that a court considers the relevant factors both when deciding to imprison and when determining the length of imprisonment, and from this concluding that a court must “recognize” the inappropriateness of imprisonment for rehabilitation both when sentencing and when choosing a duration of imprisonment.

Justice Kagan also noted context supporting her interpretation. She led with 28 U.S.C. § 994(k), which I previously noted could shed light on the proper interpretation. She also noted the pointed absence of statutory authority for courts to ensure offenders participated in rehabilitation programs. (Tapia didn’t participate in the relevant rehab program because she wasn’t sent to the prison the judge recommended and because she wasn’t interested in the program.) Finally, she noted that those willing to consider legislative history would find support for her interpretation in the relevant Senate Report.

Justice Kagan next rejected arguments that the “rehabilitation model” which the SRA supplanted referred only to undue belief in “isolation and prison routine” causing the prisoner to reform. She called this reading “too narrow”, citing an essay which characterized the rehabilitation model more broadly. This was Part III, section B, if you’re interested in more detail — I’m not going to attempt to summarize any further than that.

Justice Kagan last noted that the sentencing judge may have improperly considered rehabilitation in determining the length of Tapia’s sentence. Thus the Court left open the possibility that the sentencing judge might not have done so. Finally, the Court sent the case back to the Ninth Circuit for further action.

The concurrence

Neither Justice Sotomayor nor Justice Alito was convinced that the sentencing judge actually did improperly sentence Tapia. Evidently unsatisfied by Justice Kagan’s noting that the sentencing judge only might have acted improperly, Justice Sotomayor wrote a concurrence, joined by Justice Alito, explaining why she thought the sentencing judge had not acted improperly. At the same time, she noted that the sentencing judge’s rationale was less than clear, and that she wasn’t completely certain that he hadn’t acted improperly. Thus both justices nonetheless joined Kagan’s opinion in full.

The outcome

None of this means that Tapia will necessarily get what she presumably wants: a shortened prison sentence. The Court reversed the judgment of the circuit court that upheld her sentence, and it remanded so that court would take a second look, but it didn’t specify the actual outcome. Justice Kagan’s opinion doesn’t conclude that the sentencing judge improperly lengthened Tapia’s sentence for the purpose of rehabilitation: it merely says that the judge may have done so. Justice Sotomayor’s concurrence, joined by Justice Alito, only further emphasizes this point. So on remand, the lower court might conclude that the sentencing judge didn’t improperly lengthen Tapia’s sentence to 51 months. Or it might not. Either way, Tapia’s done well so far: getting the Supreme Court to hear your case, and to rule in your favor, is no small feat.

Even if Tapia convinces the Ninth Circuit that the sentencing judge improperly lengthened her sentence, Tapia might be unsuccessful. Justice Kagan’s opinion concludes with, “[w]e leave it to the Court of Appeals to consider the effect of Tapia’s failure to object to the sentence when imposed.” So Tapia might have missed her chance to win that argument.

Thoughts

I’d gone into this case understanding it to be a nice concise demonstration of statutory interpretation, and I wasn’t mistaken. I wasn’t certain of the correct outcome on first reading the briefs, but §994(k) sealed it for me. It was nice to be vindicated in my thoughts on the case.

It’s easy to overread a case, picking out extremely nitpicky details and magnifying their importance. At the same time, a few details in Kagan’s opinion stuck out at me. First, in analyzing the statutory text, Kagan turned to the 1987 Random House dictionary for definitions. The Sentencing Reform Act was enacted in 1984, so the 1987 dictionary is contemporaneous. Second, Kagan prefaces the paragraph dealing with legislative history, “for those who consider legislative history useful”. The textualists on the bench will insist that the proper dictionary to interpret language is one contemporary with its writing, as a 1987 dictionary would usually be for a 1984 law. And Justice Scalia in particular rejects any reference to legislative history: he believes the law is what was passed, not what was not passed, as the aforementioned Senate Report was not. I think Kagan probably wrote as she did as gestures of comity to her fellow justices, such that everyone would be happy with the resulting opinion. Maybe that’s an overread, but I would guess it isn’t.

It’s also worth noting that this case was unanimous. Remember, a plurality to (more often) a majority of all Supreme Court decisions are unanimous. The Justices are not as fractious a bunch as you would believe from the cases and decisions that receive significant airplay.

Microsoft v. i4i

The Court unanimously (minus Chief Justice Roberts, who had recused himself apparently because his family owned Microsoft stock) ruled that the standard of proof for patent invalidity was clear and convincing evidence, not the lesser burden of merely a preponderance of the evidence. Further, it concluded that this standard was consistent both for evidence which the Patent and Trademark Office had reviewed, and for evidence which it had not reviewed.

Justice Sotomayor’s opinion for the Court

Justice Sotomayor wrote the opinion for all but Justice Thomas (more on him later). Her opinion relied on Justice Cardozo’s opinion in RCA v. Radio Engineering Laboratories, Inc.. Justice Cardozo in 1934 had described the standard of proof for finding invalidity as “clear and cogent evidence”. By the time the language at issue in Microsoft was added, Justice Sotomayor deemed this language to have become part of the common law (roughly: judge-made law, when some dividing line or another must be set for consistency but no laws have specified one). Moreover, she deemed Congress’s language to have used terms of art with well-known meanings to judges, which codified the “clear and convincing” standard. Thus until Congress says otherwise, “clear and convincing evidence” is the standard of proof for declaring a patent invalid.

Justice Sotomayor disagreed with the various narrow views Microsoft took of prior patent decisions, both at the Supreme Court and in lower courts, which would have set different standards of proof for certain forms of evidence. (Curiously, those forms happened to be the ones Microsoft was trying to use.) She said that even “squint[ing]” the Court couldn’t see qualifications of when clear and convincing would apply as the standard.

Justice Sotomayor also disagreed with Microsoft’s alternative argument that a reduced standard of proof applies to evidence not reviewed by the PTO. She thought that prior cases at the Court and elsewhere had consistently at most concluded that evidence reviewed by the PTO could be deemed to have “more weight” than evidence not seen by it.

Finally, Justice Sotomayor addressed the competing policy arguments of both parties: “We find ourselves in no position to judge the comparative force of these policy arguments.” Instead she said the ball was in Congress’s court: if a different standard of proof was to apply, it was up to Congress to enact it.

Justice Breyer’s concurrence

Justice Breyer, joined by Justices Scalia and Alito, wrote separately to emphasize that the clear and convincing standard of proof applied only to questions of fact, not to questions of law. What’s the difference? A jury will decide the facts of a case, but it won’t decide what the nature of the legal issues are in it, or how those issues map onto the facts. Those legal issues are determined by judges, consistent with statutory and common law, at least partly to ensure consistency in application. Quoting from Breyer’s concurrence (citations omitted) will probably illuminate the difference better than I can summarize it (or at least illuminate no worse):

Many claims of invalidity rest, however, not upon factual disputes, but upon how the law applies to facts as given. Do the given facts show that the product was previously “in public use”? Do they show that the invention was “nove[l]” and that it was “non-obvious”? Do they show that the patent applicant described his claims properly? Where the ultimate question of patent validity turns on the correct answer to legal questions—what these subsidiary legal standards mean or how they apply to the facts as given—today’s strict standard of proof has no application.

Justice Thomas’s concurrence in the judgment

Justice Thomas in his opinion agreed with the result, but he didn’t agree with the reasoning used to reach it. Unlike the other justices, he thought that when Congress said a patent should be “presumed valid”, that did not clearly indicate to judges that Congress intended to codify the clear and convincing standard. But since Congress had not specified a standard of proof, Justice Thomas concluded that the common law rule from Justice Cardozo in RCA applied. So in the end Justice Thomas held that the standard of proof of invalidity was clear and convincing evidence, but he reached it in a different manner.

The outcome

On the face of it, Microsoft losing here means that if they want to avoid a $300 million judgment, they’re going to need to try another argument in the lower courts. But since they’ve already gone through once, they’re mostly limited to whatever arguments they’ve already made, and preserved to be argued further. I don’t know how many that is, but at this point I’m guessing it’s pretty small. So Microsoft is likely out $300 million at this point, plus a bunch more for the legal costs of litigating this matter for as long, and as far, as they did.

Thoughts

This was another fun case to follow, although unlike Tapia it was much harder to follow, and it required more knowledge of the surrounding law to really understand it. Policy-wise, I tend to think it might be better if patents were easier to overturn. Thus for that reason I think a lower standard of proof might be a better thing, although it’s hard to be sure if such a change wouldn’t have other adverse effects negating that benefit. But as far as the actual law goes, and not what I wish (however uncertainly) might be the case, Microsoft seemed maybe to be stretching a little. (Maybe. It was hard to be sure given the extent of my experience with any of the relevant laws, cases, &c.) Looking at the opinions in retrospect, that intuition seems to have been right.

As far as the opinions go, I find something to like in all of them, to some degree or another. The “clear and cogent” language in the Cardozo opinion did seem fairly clear in explaining a standard of proof, if one assumed Microsoft’s narrow read of the conditions when it applied to be a stretch. All the justices agreed on that. Breyer’s opinion distinguishing questions of fact and law seemed pretty smart, too: given how complex this area of law seemed just trying to read up for one case, probably nobody would be very happy if questions of law got lumped in with questions of fact for juries. And I liked the way Justice Sotomayor brushed off all of the policy arguments both sides made (arguments so lopsidely unbalanced and cherry-picked that relying on either completely would be destructive to the ends of the patent system). Ideally courts should merely interpret the law, not make policy or choose amongst policies, and the legislative and executive branches should decide policy.

But Justice Thomas’s opinion, lumped in with the parts of Justice Sotomayor’s opinion with which he agreed, seems like the best reading to me, at least based on what I (think I) know. I didn’t really think the words “shall be presumed valid” clearly referred to a particular standard of proof such that they could be a term of art, as all the justices but Thomas would have. At this point, assuming I understand how the law works correctly in the absence of legislative action, reverting to the state of the matter as it was before — that is, Justice Cardozo’s position — seems the right move to me.

Again, that’s just how I’m reading the law. It’s not really what I want in the patent system, which I think could use a good number of changes to adapt to the modern world.

It’s also worth noting — again — that this case, too, was unanimous. I was a little surprised that both cases turned out that way, as my half-informed readings had made me think neither case was quite that straightforward. Then again, the Supreme Court never really gets easy cases, yet even still they’re frequently unanimous. So I shouldn’t be too surprised even in these particular cases.

Conclusion

If you haven’t done it already, I’d recommend taking a look at the actual opinions in these cases. Law has this stigma of being inscrutable. In various areas of law, it doubtless is just that. But in areas not densely technical, legal opinions (particularly higher-court opinions) can be surprisingly readable (once you condition yourself to skip over all the inline citations). Both cases weren’t so densely technical that an intelligent reader couldn’t follow them. Indeed, I’d say they were generally fairly readable. Give it a shot: you might be surprised what you can learn reading the occasional legal opinion. And when a news story breaks, you’ll get a much less colored view of it if you read it from the source, rather than merely read coverage of it.

(Just started reading? See part 1, part 2, and part 3.)

On the day I visited the Supreme Court, it heard two cases each for an hour: Tapia v. United States concerning sentencing for rehabilitative purposes, and Microsoft v. i4i Limited Partnership concerning the standard of proof in evaluating patents for invalidity.

Tapia v. United States

Background

Alejandra Tapia and a friend were passing through customs while driving from Mexico to the United States. An immigration official noticed they were acting nervously and took a closer look at their car, discovering two illegal immigrants that Tapia was attempting to smuggle into the United States. She was arrested for this but was soon released, subject to court restrictions, while proceedings continued. When she failed to appear in court for a hearing, a warrant was issued for her arrest. After later apprehension Tapia was convicted on counts related to her smuggling of illegal immigrants and for jumping bail.

The judge responsible for sentencing her thought she would benefit from a particular drug treatment program, offered only in certain prisons. In order to get her into that program, he recommended Tapia be sent to a particular prison, and he increased the length of her sentence explicitly to give her the opportunity to take part in that program. In doing so he potentially fell afoul of this statutory language:

The court, in determining whether to impose a term of imprisonment, and, if a term of imprisonment is to be imposed, in determining the length of the term, shall consider the factors set forth in section 3553(a) to the extent that they are applicable, recognizing that imprisonment is not an appropriate means of promoting correction and rehabilitation.

The issue

Before enactment of the law adding this language, the “rehabilitative ideal” as implemented by U.S. law held that isolation from society and prison routine would rehabilitate criminals. Parole boards determined when prisoners were ultimately released based on subjective assessments of the progress of inmates. The Sentencing Reform Act changed the system to be more objective, while still attempting to leave judges discretion to determine individualized sentences.

The sticky wicket is in the phrase, “recognizing that imprisonment is not an appropriate means of promoting correction and rehabilitation”. Does “recognizing” this mean that when a district court sets a length and term of imprisonment, he can’t consider rehabilitation programs in determining the sentence length? If he can’t consider them, then perhaps Tapia’s sentence was wrongly lengthened. On the other hand, section 3553(a) explicitly says, “The court…shall consider…the need for the sentence imposed…to provide the defendant with needed educational or vocational training, medical care, or other correctional treatment in the most effective manner”, which arguably includes drug treatment programs like the one recommended for Tapia here. How should the “recognizing” clause be understood?

Further wrinkles in this particular instance include that Tapia wasn’t sent to the recommended prison (because doing so would place her in too close proximity to another inmate deemed likely to be a bad influence) and that she wasn’t entered into the recommended drug treatment program (as I understand it, because she refused to be enrolled). So the judge in question (more generally, any judge, as I understand it) couldn’t actually have required her to enroll in a treatment program as part of her sentence.

Laws and decisions to consider

This is mostly a case of statutory interpretation of existing laws, so there’s not much in the way of prior Supreme Court decisions to consider. It mostly comes down to how you read the text of the relevant statutes. One statute beyond those above that I find particularly interesting is 28 U.S.C. § 994(k), which states:

The Commission shall insure that the guidelines reflect the inappropriateness of imposing a sentence to a term of imprisonment for the purpose of rehabilitating the defendant or providing the defendant with needed educational or vocational training, medical care, or other correctional treatment.

The guidelines in question specify sentencing ranges from which judges generally can’t depart. Interestingly, this section seems pretty clear that sentencing to a term of imprisonment for the purpose of providing the defendant with access to “correctional treatment” (like a drug treatment program) is not acceptable. If §3582’s text is ambiguous, perhaps this text might clarify it.

Microsoft v. i4i Limited Partnership

Background

In the 1990s i4i received a patent on a method of storing a document whose contents are structured, say, by formatting, nesting, and so on. Broadly speaking, the patent proposes storing document contents separate from document structure to facilitate easier manipulation. (The exact trick is pretty much this: store all the textual contents of the document somewhere, then store a list of pointers into that text with associated semantic meanings, like begin-element or end-element, separately.) The idea apparently works well when used in editors, and Microsoft once (no more, due to this litigation) used it in the custom XML editor built into Word. i4i sued them for doing so, and while Microsoft claimed the patent was invalid, the jury didn’t buy it. Microsoft was required to pay i4i $200 million for infringing their patent, then $40 million for doing so willfully. (Apparently Word developers had seen a presentation from i4i about software practicing the patent, asked questions about how it worked, received marketing material from i4i that mentioned the patent by number, and discussed i4i’s marketing material in email.) With interest the total’s now around $300 million.

The issue

Microsoft pled their case up through the courts, losing at each level. Finally they appealed to the Supreme Court — but because Microsoft’s particular travails aren’t necessarily interesting to the Supreme Court as it can only selectively right wrongs (it reviews around 1% of ten thousand or so appeals every year), Microsoft tried an interesting tack: they challenged the standard of proof required to demonstrate invalidity of the patent. This got the Supreme Court to bite and hear their appeal.

The district court told the jury that Microsoft had to prove invalidity by clear and convincing evidence, a phrase not found in statutory text but rather inferred from 35 U.S.C. § 282. Microsoft argues that when the standard of proof is unspecified, the default (with rare exceptions not relevant here) is a preponderance of the evidence. Clear and convincing evidence basically means the claim is “highly probable”; a preponderance of the evidence basically means the claim is “more likely than not”, or “50% plus one”. It could be much easier for Microsoft to prove invalidity if they only had to get a jury to say that the patent in question was more likely than not (by even the smallest fraction) to be invalid.

(What was Microsoft’s evidence of invalidity, you ask? Here it turns into a mess. i4i sold software called S4 over a year before applying for the patent, and S4 might have implemented the patent in question. If S4 implemented the patent, then an on-sale bar in 35 U.S.C. § 102(b) would invalidate the patent. Microsoft and i4i disagreed about whether S4 practiced the patent. [S4’s source code, and presumably S4 itself, was no longer available to be inspected, as S4 had been obsolete before litigation commenced.] Microsoft said S4 implemented the patent, citing the software’s manual, testimony from a former i4i employee, and a letter i4i’s founder wrote to investors indicating that S4 implemented the idea he later patented. i4i’s founders said it didn’t, and one stated in court that the musings in the letter to investors were “an exaggeration, and as I said, it could be said to be a lie” and that the idea was conceived after S4 went on sale. Without S4’s source code Microsoft couldn’t prove invalidity by “clear and convincing evidence”. But it’s quite possible Microsoft could prove it was “more likely than not” that the on-sale bar applied, and that the patent was invalid.

Microsoft also attempted to claim invalidity of the patent by dint of its being obvious through combination of a couple other patents, one of which the examiner who granted i4i’s patent hadn’t seen. Should a patent be “presumed valid” in the language of the statute, and in the lower court’s understanding thus requiring clear and convincing evidence to prove invalid, if the evidence for invalidity wasn’t considered when the patent was granted? Here too could be another avenue of attack under a favorable ruling.)

Laws and decisions to consider

This case, as like Tapia, is mostly a matter of statutory interpretation. But beyond the clauses of patent law at issue there are also a few Supreme Court decisions of relevance.

First, in 1934 in RCA v. Radio Engineering Laboratories, Inc. Justice Cardozo variously described the burden to overcome a patent’s presumption of validity as “clear and cogent evidence”, that the challenger “bears a heavy burden of persuasion, and fails unless his evidence has more than a dubious preponderance”, and that “the countervailing evidence is clear and satisfactory”. (Microsoft distinguishes this language as referring to particulars of that case, specifically that the evidence being tried there had been tried once by one party and found wanting, then in that case was being tried again by an entirely separate party — so “clear and convincing” makes sense only in that rare situation.) Justice Cardozo’s opinion, and its language, precede the statutory text used to justify the clear-and-convincing standard: does the text merely codify that precedent? (Of course, Microsoft and i4i furiously disagree about what the precedent says, and about how courts interpreted that standard.) This case cuts for i4i.

Second we have Grogan v. Garner and Herman & MacLean v. Huddleston. In Grogan the former Justice Stevens, analyzing a case where the statutory text was silent about the standard of proof, determined the standard to be a preponderance of the evidence. In Justice Stevens’s words, “This silence is inconsistent with the view that Congress intended to require a special, heightened standard of proof.” In Huddleston Justice Marshall determined the standard of proof in a similar situation to be a preponderance of the evidence. These cases cut for Microsoft.

Third we have KSR v. Teleflex, a 2007 Supreme Court patent case. In passing in that case, Justice Kennedy wrote in dicta for a unanimous Court that “the rationale underlying the presumption—that the PTO, in its expertise, has approved the claim—seems much diminished” in a case where the PTO hadn’t considered evidence being used to challenge a patent. So perhaps the presumption of validity that Microsoft was challenging shouldn’t apply (or should apply with lesser force) because the PTO didn’t know about the software Microsoft claims implemented the patent. This would cut for Microsoft.

Past this you have the usual arguments for and against patents: Microsoft saying that granting patents too easily is dangerous (an interesting position for them, perhaps), and i4i saying that the patent system stimulates innovation and that invalidating patents hurts that. (Each side’s argument pretty much completely ignoring the patent system’s inherent balancing act between incenting progress and retarding it.) How much weight you want to give this depends to an extent on what sort of partisan you are.

Next time, to the arguments themselves.

(Just started reading? See part 1 and part 2.)

I executed my plans and arrived at the Court at approximately 02:45. There was no obvious line, so I wandered around the Court plaza to look for a sign indicating where the line would form. (I knew it wouldn’t simply be on the front steps, alas.) I found none, and I hadn’t yet wandered up to a nearby guard to ask when the first person in line wandered up to confirm my intentions. (Note to anyone wondering exactly where the line forms: it forms on the sidewalk at the south end of the arc of waist-high columns in front of the Court, then trails south along 1st Street NE toward the corner.) Will, a patent attorney from North Carolina, flew up Sunday and arrived at the Court on the last Metro bus shortly before midnight. He too had been uncertain about timing and was playing it safe by arriving early.

Will and I talked off and on until 04:00 when the line truly began to form. (This is recommended both to pass time and to gain friends who can hold your spot in line should you need to leave to use a bathroom or get some food.) At that time a cadre of patent examiners from the Alexandria office arrived on an informal field trip. More visitors followed shortly after, and by 04:15 the line was at 15-20 people.

I’d been warned it could get cold outside, and while it wasn’t cold, later in the night it wasn’t really warm. When I pulled on a Mozilla jacket to fend off the slight chill I quickly discovered:

• Patent examiners hate IE. (And not just IE6, or IE7, or something similarly old: any version of IE. Amy, the patent examiner who told me this, was very emphatic on this point.)
• Patent examiners love Firefox.
• Patent examiners love Firefox extensions.
• Patent examiners are probably the most legitimate tab over-users I’ve encountered. (It makes sense if they’re reference-checking and researching patent applications, considering many sources of information at a time.) One examiner told me he has around 300 tabs open.
• Patent examiners are particularly interested in 64-bit Windows Firefox builds, because when you open 300 tabs you start hitting 32-bit memory limits. One had somehow found a 64-bit Windows build of “Namoroka” (Firefox 3.6) and had been using that for quite some time. I told him that there are unsupported 64-bit Windows builds of Firefox 4, and I mentioned that 64-bit Windows Firefox should happen soon.

The line grew in fits and spurts from there on. By 05:15 the line was up to perhaps thirty; by 05:40 the line had roughly passed the 50-person lower bound on nigh-guaranteed public seating. Subsequent arrivals frequently expressed disbelief at the length of the line, which made me quite glad I’d arrived as early as I did. Shortly before 06:00 a couple groups of us near the front tag-teamed watching our spots and heading to a nearby Starbucks for a bite to eat. I hadn’t planned on doing so, but I took the chance (and the caffeine) when I could. During the walk to and from it I further discovered that patent examiners have a sense of humor about the applications they see and about what they do. 🙂

Just after 07:00 the unofficial line moved into position on the plaza, and we settled down again to wait. Shortly after we received numeric cards indicating our place in line, and once that happened we had somewhat more flexibility about what we could do: use the Court restrooms (immaculate gray marble, hands-free toilets and sinks, all imbued with considerable gravitas) and snack area (after passing through security), go elsewhere, and so on, so long as we returned in time to enter the Court.

After a Mountain Dew (more caffeine!) from that snack area and a bit more waiting, we finally began to pass through security. After ascent up stairs to the level of the courtroom, we deposited our things at the coin locker and coat-check area. After one last security screening (the second set of metal detectors to be passed), we were finally in the courtroom.

It wasn’t obvious which seats were reserved for the public and which were reserved for other use. The first ten people in line including me were seated at audience left on movable wooden chairs between two marble columns, just past the area where the Supreme Court press corps sit. The columns partially obscured the view of people behind me (which would seem to indicate that there’s no position in line guaranteeing a good view, unless you attend as a member of the Supreme Court bar), but fortunately I had a good view of all the justices.

At 10:00 the Court was called to order as the audience stood while the justices entered the Court. The first order of business before argument was to process admissions to the Court bar, a briskly formal process except for the brief moment after George Martinez moved that his three sons be admitted, in response to which Chief Justice Roberts, after granting his motion, further wished him congratulations. Sometimes opinions in previous cases are announced before argument, and occasionally a dissenting justice will give a stemwinder from his opinion if he felt strongly enough that the result was wrong, but unfortunately neither happened today. This business complete, the Court proceeded to arguments.

But before I reach the arguments, a deeper look at the cases themselves: next time.

(Just started reading? See part 1.)

If I was to combine a trip with a visit to family for Easter, I was limited to arguments in April. One sitting stood out as particularly interesting: the April 18 sitting in which Tapia v. United States and Microsoft v. i4i Limited Partnership would be argued. Tapia concerned the permissibility of considering in-prison rehabilitative programs during sentencing — not an issue of particular interest to me. But Microsoft concerned patents, which are certainly relevant to anyone in the software industry. It made a good fit: my weekend was chosen.

Supreme Court oral arguments are open to anyone who arrives “early enough”, which depends on the interest level of the cases being argued. Tapia, as a sentencing case not touching a contentious issue like the death penalty, was low-interest. But “the showcase intellectual property case of the year” might well draw a moderate crowd. And I knew from a Mozillian who’d attended Bilski v. Kappos, the last major patent case before the Court, that arriving at 22:00 the day before a patent case could be good for a spot near the end of public seating. (Huge caveat: the other arguments that day concerned juvenile life imprisonment without possibility of parole.)

Based on one suggestion of 05:00 for “mid-major” cases (which I suspected Microsoft to be) and the effort I was making just to get to D.C., I decided to err heavily on the side of caution by waking up at 1:00. I would take a shower, get dressed in a suit purchased Friday (Visa flagged it as a fraudulent transaction, and I think they were on to something), and walk forty minutes to the Supreme Court. Better to get less sleep but be guaranteed to see the argument than to gamble and lose after making such an effort to even have a chance to see it.

Next time: sitting in line for the arguments.

Regrettably the Washington Post chose to wait until after Christmas to publish this, so this post is not quite on time. Nevertheless, in the vein of the post of Christmas past I present you with Amazon.com‘s patented method (as yet unimplemented) for ameliorating the deadweight loss of Christmas, to theirs and the receiver’s benefit, and in some sense to the giver’s benefit as well:

Amazon patents procedure to let recipients avoid undesirable gifts

Apparently returned purchases are a major cost for retailers, especially otherwise largely-automated ones like Amazon.com. So avoiding shipping bad gifts, only to then have to process them again when returned, and possibly resell them at a loss, is a good way for Amazon.com to cut costs. (And though the article doesn’t mention it, presumably this system would act as an incentive for shoppers to shop exclusively at Amazon.com rather than elsewhere — even better from Amazon.com’s point of view.) Strangely (or perhaps not so strangely in today’s newspaper world, alas) the article doesn’t link to the patent itself, but it’s not particularly hard to find. I doubt many patents these days include “mildred” in their text. 🙂

I express no position on the wisdom of permitting Amazon.com to patent this. But the idea itself is a good one.