Skip to content

us supreme court releases bilski decision on patents

2010 June 29

The US Supreme Court yes­ter­day released its decision on the Bil­ski v. Kappos case.

The bot­tom line:

Busi­ness meth­ods can still be pat­en­ted in the U.S.

The sum­mary:

Bil­ski attemp­ted to pat­ent a method of hedging energy com­mod­it­ies, primar­ily in the form of a math­em­at­ical for­mula. The US Pat­ent Office rejec­ted the applic­a­tion. The rejec­tion was upheld by the Board of Pat­ent Appeals and the Court of Appeal for the Fed­eral Circuit.

Most not­ably, the Court of Appeal rejec­ted the pre­vi­ous test which had enabled the claim­ing of busi­ness method pat­ents (the State Street Bank & Trust case), instead hold­ing that “a claimed pro­cess is pat­ent eli­gible [only] if: (1) it is tied to a par­tic­u­lar machine or appar­atus, or (2) it trans­forms a par­tic­u­lar art­icle into a dif­fer­ent state or thing”.

Need­less to say, this new test would have put a bit of a damper on busi­ness method patents.

The Supreme Court did not agree with the Court of Appeal. It held that the “machine or trans­form­a­tion” test is not the only test for pat­ent eli­gib­il­ity for a pro­cess and that busi­ness method pat­ents are in fact per­miss­ible under the Pat­ent Act.

That being said, they non­ethe­less agreed with the Court of Appeal that Bilski’s pat­ent should be rejec­ted, not because it failed to meet the “machine or trans­form­a­tion” test, but rather because it was an attempt to pat­ent an abstract idea rather than a busi­ness method. The Supreme Court affirmed that abstract ideas are not patentable.

Com­ments:

Many like the EFF seem to be dis­ap­poin­ted, but from a jur­is­pru­den­tial per­spect­ive the judge­ment makes sense to me. The Supreme Court’s rationale was that courts “should not read into the pat­ent laws lim­it­a­tions and con­di­tions which the legis­lature has not expressed” and there was no reas­on­able basis on which the term “pro­cess” had to be spe­cific­ally tied to a machine or the trans­form­a­tion of an article.

In other words, it’s not the job of the courts to make up new stuff when it comes to the law — their job is only to inter­pret the law cor­rectly. And if there’s any issue with the Pat­ent Act, then it should be dealt with through legis­lat­ive change rather than a judi­cial decision.

Per­haps not quite the inter­ven­tion­ist approach that some might have been hop­ing for.

So, as the EFF notes, all of you out there that have a glim­mer of inspir­a­tion on how to make your for­tune from, for example, a sys­tem for reserving toi­lets, (or suing oth­ers who come up with the same thing but didn’t apply for a pat­ent) can still pur­sue that dream.

Bil­ski v. Kappos (PDF)

  • Google Bookmarks
  • Digg
  • del.icio.us
  • Facebook
  • email
  • LinkedIn
  • Slashdot
  • Technorati
  • Live
  • Print
  • Reddit
  • StumbleUpon
  • Yahoo! Buzz
  • Twitter
  • FriendFeed
  • MSN Reporter
  • NewsVine
  • Posterous
  • SphereIt
  • Sphinn
  • Suggest to Techmeme via Twitter
  • Tumblr
  • Yahoo! Bookmarks

fusenet’s employment/entrepreneur program

2010 June 3

A very inter­est­ing story in IT World Canada about a com­pany called Fusenet that has put into place a novel approach to busi­ness. In effect, it is empower­ing its employ­ees to become entre­pren­eurs and giv­ing them equity in their cre­ations. Fas­cin­at­ing approach. Inev­it­ably com­par­is­ons can be drawn with a sim­ilar pro­gram Google runs, but as far as I’m aware Google retains own­er­ship of everything cre­ated by its employ­ees. Not so with Fusenet’s model. From the article:

Every Fri­day, the Pet Pro­ject Pro­gram (P3) goes into effect. “If you’ve been approved into the pro­gram, on Fri­day, we don’t expect to see you at your desk. You’ll be in our lab or you’ll be col­lab­or­at­ing with other people,” said Singhal.

The P3 model is codi­fied into employee agree­ments and the intel­lec­tual prop­erty developed dur­ing this time does not belong to Fusenet, he said.

If an employee spends three months work­ing every Fri­day to develop a new tech­no­logy for bet­ter video com­pres­sion, for example, and then presents it to the com­pany, the idea still belongs to the employee, said Singhal.

Fusenet will ask the employee how much they want to sell the idea for or whether they want to start a com­pany that will sell or license the product, he said. “We’ll help you mar­ket that and say, ‘We’ll take 50 per cent of the equity, you take the other 50 per cent,’” he said.

“We will help you with money, we will give you all the resources you need – mar­ket­ing, cus­tomer ser­vice, R&D – but you get to keep a sig­ni­fic­ant chunk of the equity in the busi­ness as opposed to hav­ing just the pride of being able to say you star­ted it,” he said.

The policy applies to all employ­ees, but it’s the soft­ware developers who are most likely to come up with the ideas, said Sing­hal. “We thought this was an inter­est­ing model … 99 per cent of the com­pan­ies out there will take the soft­ware,” he said.

Fusenet has exper­i­enced one major suc­cess, one emer­ging suc­cess and two fail­ures as a res­ult of the model, said Sing­hal. Another five pro­jects are cur­rently in the R&D stage, he said.

Of course there is a caveat noted in the story about how such an arrange­ment must be care­fully doc­u­mented. I could also see a few risks asso­ci­ated with this as far as delin­eation of IP and who owns what. Very often, when new ideas spring up, they may be closely related to some exist­ing intel­lec­tual prop­erty or based upon it. The ques­tion then is where the divid­ing line is or should be drawn and how that is set out in the doc­u­ments. Not an insur­mount­able issue but one that does war­rant a bit of thought.

I cer­tainly admire Fusenet for hav­ing the vis­ion and cour­age to adopt such a model. Of course, it’s no guar­an­tee for suc­cess but cer­tainly puts all the right incent­ives in place to have an envir­on­ment con­du­cive to that. I really do hope to see some inter­est­ing things come out of their shop in the near future. They will, after all, be very likely to attract the right sort of folks with this program.

  • Google Bookmarks
  • Digg
  • del.icio.us
  • Facebook
  • email
  • LinkedIn
  • Slashdot
  • Technorati
  • Live
  • Print
  • Reddit
  • StumbleUpon
  • Yahoo! Buzz
  • Twitter
  • FriendFeed
  • MSN Reporter
  • NewsVine
  • Posterous
  • SphereIt
  • Sphinn
  • Suggest to Techmeme via Twitter
  • Tumblr
  • Yahoo! Bookmarks

new copyright act now online — updated

2010 June 3

Update: For any­one out there who: (a) pored over the pre­vi­ous incarn­a­tion of this bill (i.e. Bill C-61) back in 2008; (b) doesn’t hap­pen to have red­lining soft­ware; and © just wants to review what has changed between C-61 and C-32, here are red­lines show­ing the changes from C-61 to C-32 (Word and PDF). Happy reading.

The much anti­cip­ated Copy­right Mod­ern­iz­a­tion Act (or Bill C-32) was tabled yes­ter­day and is now on-line and avail­able for your read­ing pleas­ure. Given the broad interest in this act, it’s not sur­pris­ing that there has already been a ton of press on it, includ­ing sum­mar­ies and ana­lyses galore.  I don’t pro­pose to rein­vent the wheel, so will simply point to you a post in Michael Geist’s blog where he provides a sum­mary and vari­ous links to media cov­er­age of the bill (which also have their own sum­mar­ies) plus of course his own take on it.

My ini­tial impres­sion is that the bill strikes a rel­at­ively good bal­ance between con­tent cre­at­ors and con­tent users. Of course, given the highly politi­cized nature of copy­right reform, and the some­times fairly extreme views taken in vari­ous camps, it won’t make every­one happy. From the per­spect­ive of Geist et al. on the user side, the biggest cri­ti­cism so far has been how digital locks (or “TPMs”) are dealt with. The short ver­sion is that TPMs are per­mit­ted even if they pre­vent users from exer­cising spe­cific rights that are deemed by the Copy­right Act not to con­sti­tute copy­right infringement.

I have my own views on TPMs but will reserve that for another post.

  • Google Bookmarks
  • Digg
  • del.icio.us
  • Facebook
  • email
  • LinkedIn
  • Slashdot
  • Technorati
  • Live
  • Print
  • Reddit
  • StumbleUpon
  • Yahoo! Buzz
  • Twitter
  • FriendFeed
  • MSN Reporter
  • NewsVine
  • Posterous
  • SphereIt
  • Sphinn
  • Suggest to Techmeme via Twitter
  • Tumblr
  • Yahoo! Bookmarks

Switch to our mobile site