Filed under: Developer, News, Windows, Microsoft
Microsoft tells Supreme Court: You Can't Patent Source Code?
by Victor Agreda, Jr. Feb 22nd 2007 at 9:30AM
My, what an interesting year we're having. First the Wow! starts, now the Wha? starts in earnest. It seems Microsoft might be arguing itself into a corner in front of the Supreme Court regarding software patents. How? Well, Microsoft uses a little bit of code from AT&T to make some speech recognition magic happen in Vista. The catch? they might not have licensed this code for use overseas. So AT&T sues, claiming MS violated the patent on the code itself-- saying they illegally copied it overseas, essentially. The arguments in front of the nation's highest court might finally settle the debate of software patentability. At issue is when source code becomes patentable or, if it ever is.AT&T's position is that Microsoft is stealing the code, just as a copycat manufacturer might steal Ron Popeil's magic Hair-in-a-Can.
But the arguments get pretty tangled when the court presses the issue of what, exactly, is patented. The resulting case has Microsoft arguing a point you may not have expected them to argue; You cannot patent source code or object code. Justice Souter keeps it real by comparing code to a blueprint, and ultimately saying that the copying of code onto hard drives using this blueprint, or the mere exportation of this code for such purpose, could constitute infringement. To defend itself, MS initially tried to claim that since the physical devices used to manufacture the PC's running said code are all made overseas and therefore are out of US jurisdiction (nice try). Failing that, they are taking this position: you cannot patent the series of instructions themselves, only the mechanism that delivers the functionality can be patented. Therefore, since they only shipped a master disc with code, they ain't violatin' nuttin' yer honor. The crux they claim, is that software doesn't become software until it's installed by the end user.
It's an interesting argument. AT&T has to now prove that the methods, the procedures, the instructions in the code, and not just the manifestation of said code, is indeed patentable. Thus, code is patentable (when created in a form that is executable), and just because you're only sending the blueprint via disc overseas but don't make the computer that executes the code it doesn't exclude you from the infringement. Clear as mud, isn't it?
Bear in mind, splitting hairs is what the Supreme Court is supposed to do. This time, they have a whopper of a case on their hands and there is no telling what will happen. The Justices are doing a great job so far trying to pin down exactly when the code become patentable, if at all. I have little doubt this will finally bring some closure to a hotly-debated topic, and will have ramifications throughout the tech world.
What does this mean for open source developers? Indeed, what does this mean for any developer who creates a novel methodology in their software, no matter how it is delivered? Stay tuned, right now there are more serious questions than there are solid answers.
[via BetaNews]
It's an interesting argument. AT&T has to now prove that the methods, the procedures, the instructions in the code, and not just the manifestation of said code, is indeed patentable. Thus, code is patentable (when created in a form that is executable), and just because you're only sending the blueprint via disc overseas but don't make the computer that executes the code it doesn't exclude you from the infringement. Clear as mud, isn't it?
Bear in mind, splitting hairs is what the Supreme Court is supposed to do. This time, they have a whopper of a case on their hands and there is no telling what will happen. The Justices are doing a great job so far trying to pin down exactly when the code become patentable, if at all. I have little doubt this will finally bring some closure to a hotly-debated topic, and will have ramifications throughout the tech world.
What does this mean for open source developers? Indeed, what does this mean for any developer who creates a novel methodology in their software, no matter how it is delivered? Stay tuned, right now there are more serious questions than there are solid answers.
[via BetaNews]