Microsoft Retracts Patent
An anonymous reader writes "Microsoft has retracted their recent controversial patent application. The story was first brought to light by Slashdot on Saturday. Today, Jane Prey of Microsoft announced the retraction on the SIGCSE (Special Interest in Computer Science Education) mailing list. 'Many thanks to the members of the community that brought this to my attention — and here's the latest. The patent application was a mistake and one that should not have happened. To fix this, Microsoft will be removing the patent application. Our sincere apologies to Michael Kölling and the BlueJ community.'"
I have a tendency to believe that humans can err, but are basically good. And even Microsoft consists of humans. So my first reaction was "Oh good, they are not as soulless as we believe, this was an honest mistake." That option had already been pointed out during the discussion on slashdot as a problem within their process:
So, an honest mistake. But this being Microsoft it took me seconds to fall into conspiracy mode. How could they have such mistakes in their process, if they care about intellectual property? Was the mistake that they didn't hide it well? Did they simply try if they can get through with this? Can an entity that consists of basically good humans be not good in the end? (I'm afraid yes). So I still cannot decide if I can trust them or not, they seem to have lied too often in the past.
memomo: free web based language trainer DE-EN-ES-FR-IT
Here is the description from the linked slashdot post, if you were wondering what this patent was about:
"BlueJ is a popular academic IDE which lets students have a visual programming interface. Microsoft copied the design in their 'Object Test Bench' feature in Visual Studio 2005 and even admitted it. Now, a patent application has come to light which patents the very same feature, blatantly ignoring prior art."
-- lol pwned
but what we all really want to know is when MS will start calling for the abolition of software patents altogether. It's not this specific application, it's Software patents as a whole that should never have happened.
...to include half a sentence describing the basics of the patent in the hyperlink?
"The patent discussed on saturday" isn't significantly shorter than "the patent on a copied IDE feature" but contains more useful knowledge and less useless knowledge.
http://www.bluej.org/mrt/?p=21
Why does it not surprise me that someone named Jane Prey is involved in a Microsoft patent SNAFU?
Your acronym is missing a G. It took me all of 3 seconds to find out that SIGCSE is the Special Interest Group on Computer Science Education. You can even copy and paste from the first google result if you're feeling especially lazy. I'm guessing you are.
Microsoft recently retracted their patents on the internet and pants.
A microsoft spokesperson said 'Many thanks to the members of the community that brought this to my attention -- and here's the latest. The patent application was a mistake and one that should not have happened.'
Everyone knows Al Gore invented the internet...
"Dictator Flakes. They WILL be delicious."
I'd be a lot happier if the Empire's own minions had noticed the problem
and withdrawn the patent BEFORE the outcry arose. As it is:
"Eternal vigilance is the price of liberty." -- Wendell Phillips, (1811-1884)
Modern addendum: "And the price of open software."
Watch now for patents that come as close as possible to stepping over the line, but stop just short. Microsoft easily has the resources to toss up nuisance patents that block possible future development of BlueJ.
Anyone who thinks this was an innocent mistake in "implementing a suggestion" probably hasn't seen the screenshots comparing The VS screens with BlueJ. ( http://www.bluej.org/vs/vs-bj.html )
Personally, I'm convinced the most plausible explanation for the *extremely* close replication of the BlueJ screens in the MSFT product is that the BlueJ source was ported to C#, probably using an automated tool.
-=Maggie Leber=-
Now the slashdot echo chamber will have a moment of self-satisfaction while more theft, more corporate domination and fraud at the expense of consumers and entrepreneurs.
Most importantly: We don't have to get out of our chairs and participate in our political system to make the government we want. Woohoo!
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
Did Microsoft employees lie about inventing this? Obviously, dishonesty in the workplace is a serious offense, and I'm sure Microsoft will severely punish employees who falsify invention claims. And no doubt the in-house patent attorneys failed to catch this serious error.... what's to become of them? Sounds like a few people might end up on the streets of Redmond.
... Right?
I mean Microsoft wouldn't just want to file bogus patents
Well, maybe Microsoft will now review all of the claims submitted by these bozos to make sure they didn't screw up before. Good thing these applications are all public - transparency is a critical part of the patent system.
Microsoft's apology changes nothing about the fact that all the original factors that caused this embarrassing mistake by them are still in play. It is very lucky that Microsoft's misbehaviour in the BlueJ example was quickly noticed, carefully documented and forcefully exposed by the BlueJ people themselves, but it is not and should not be an inventor's job to police the behaviour of big companies like Microsoft. The next time Microsoft misappropriates somebody else's invention, the problem is unlikely to be exposed so quickly. Microsoft should deal with the underlying factor behind this problem: Employees are still being encouraged to file as many patents as possible on the wrong assumption that it is a good indicator of employee merit. This is part of a deeper problem in the Microsoft executive which is fanatically pushing the meretricious concept of software patents around the world to places that have studied the idea and rejected it (EU) as harmful to the interests of small businesses.
Watch now for patents that come as close as possible to stepping over the line, but stop just short. Microsoft easily has the resources to toss up nuisance patents that block possible future development of BlueJ.
After publicly admitting the misstep with the original patent, I'm not sure what the value to MS would be in aggressively trying to thwart BlueJ. It seems their strategy here is to hold themselves out as an ethical player. They have to know that they're on notice now about BlueJ, and any attmpts to block it would be immediately picked up by the technology press, not to mention by existing BlueJ users.
Maybe I'm being too optimistic, but it seems it would be monumentally stupid for Microsoft to attempt to destroy BlueJ through legal means at this point. Perhaps they'll have to suck it up and just compete on technical merits. ;)
Read the EFF's Fair Use FAQ
I disagree with the idea of just attempting to patent absolutely anything, and then only when the app comes back as "has issue", the company says, "Oops! heh heh, never mind that one..." and just keeps on going. It's pretty clear that even if the patent office was great at detecting dupe patents, prior art,etc., that if there are 10,000 patent apps a day or whatever coming in, how do you have time to check them all? Surely a lot are slipping through and being granted based on this "apply first, worry later" stuff.
stuff |
Okay, this whole thing is not too surprising. The patent system is broken and all major companies end up using a shotgun approach to get as many, mostly invalid, patents as possible. They apologized publicly for this instance. That was the right thing to do, and MS did it for a change. Good job MS.
Oh, I think I do.
The predator preys on weaker animals (like... BlueJ?).
The prey is preyed upon.
In case you're still unclear about my use of words, the important nouns have been italicized, while the important verbs have been given a bold face.
Thank you for turning a tongue-in-cheek play on words into a grammatical pissing contest.
Is everyone going to completely ignore the fact that this feature is one of Microsoft's very, very few that aren't developed in Redmond??? The Microsoft India Development Center in Hyderabad, is responsible for this whole feature area.
Draw your own conclusions, but at a minimum, it would increase the chances of mis-communication...
(A)ssimilate? (Y/Y)
Quite confident that they could buy their way out of any resulting trouble using the money from licenses for the thousands of other patent applications on which they did something like this and did not get detected.
My turnips listen for the soft cry of your love
and donate all their licensing income derived from patenting sync ram that was derivative of early standardization attempts in an industry technical committee, we might start getting someplace.
if not, hey, what the hell, it's only ethics and morals. I'm sure it did not influence any other large companies in the field, like HP and SCO.
if this is supposed to be a new economy, how come they still want my old fashioned money?
Psyche! Ya caught us. We were just kidding, anyway. He he. Move along and go buy [whisper quiet] that lease to [/whisper quiet] Vista now.
My question is, would the USPTO have issued the patent?
.. but would the USPTO have issued a patent for this? I'm sure they'd like to say "no way, we would done due diligence and known prior art exists".
We can argue over if it would have been overturned eventually or not
I still stand by my new sig:
Microsoft's new tag line for 2007: Pilfer, Plagiarize, Patent.
This is the NSA, we're gonna geet U h@x0r5! Also, what is a h@x0r5?
Personally, I'm convinced the most plausible explanation for the *extremely* close replication of the BlueJ screens in the MSFT product is that the BlueJ source was ported to C#, probably using an automated tool.
Adding a "J" after Blue Screen (BJOD) does not mean you invalidate MS's patent on the BSOD! Sorry, I think they got there first.
just yesterday I decided to check out googles new patent search engine.
I typed in "Virtual Interaction Configuration" and up pops a patent.
I'm very anti-patent when it comes to software and the virtual interaction configuration is my own project that started back in 1988. I've only glanced over the patent so far and I intend on addressing each claim and explaining how each does not qualify for patent consideration. I intend to explain it in terms of Abstraction Physics, the common human characteristic in creating and dealing with abstraction.
At some point software patents will come to their end.
So, Microsoft admitted it, no problem, let's try it again with another program!
They will keep trying with lots of these totally unfair patents, and when people respond too late, or too weak, the previous prior-arts will have to go to the court, and because of Microsoft's money and lawyers, you're risking a hell of a lot cash to guarantee something you made up, so you probably won't or have to invest a ridiculous amount of time and effort into it. Yet another new patent for Microsoft.
They will keep trying...
Microsoft could have assigned the application to the EFF or something like that. There might have been something patentable in their application and it might as well be patented as protection against some other evil empire. They already paid to have it examined, so let the examiner decide. They would have to disclose the prior art though, which is easy using an IDS (invention disclosure sheet). Still, microsoft did right by abandoning. They could have done better by assigning. Oh yeah - I am a lawyer. A patent lawyer in fact. (flame on)
What? Me? Sig?
Move along... It was "just a mistake".
What about the zillions of other patents just like this one that they apply for every day? Is the burden really on ME to make sure that Microsoft hasn't been attempting to patent stuff I've clearly got "prior art" for?
This is terrible. Stop acting like "The system works". This is one example where a prior-art holder had the means to notice someone's faulty patent claim.
I'm not even sure where the burden of proof should lie. When you hire a patent attorney to do a "prior art search", they just give you a pile of existing patents that matched some keywords. How do you do a _real_ prior art search, beyond just what has already been patented? Its not even possible. The system is so hosed that every patent that resulted from it should probably just be thrown out.
I can't believe people are buying this "It was a mistake" B.S.
Why stick up for big business?
Sorry for the profanity, but *please, people!!
P TO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch- bool.html&r=1&f=G&l=50&co1=AND&d=PG01&s1=200602944 75&OS=20060294475&RS=20060294475
"Sure, an honest mistake. But what are they doing to fix their process so it doesn't happen again?"
It happens *daily or damn near it. Give us a break!
Here's their patent (filed Dec 28, 2006) for having the opacity of your windows change when you hit Alt-Tab.
http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=
Anyone with a clue stopped giving MS the benefit of the doubt about 15 years ago. Ugh.
My turnips listen for the soft cry of your love
It's not really a question of good or evil. It's that the process you've outlined above is essentially the path of least resistance.
/. doesn't seem to let one nest more than 3 layers deep.
We can assume that for every piece of working, checking it against a given criteria (e.g. "Did we get this idea elsewhere?") costs money. Therefore adding a given check to their process implies a cost to each piece of work.
The rationale of balancing this goes something like:
1 For a piece of work does criteria X apply?
1.1 Yes Do we increase profit by performing the check?
1.1.1 Yes Include criteria check in process END
1.1.2 No Is there legislation requiring us to check?
1.1.2.1 Yes is probability of getting caught * cost of getting caught > cost of implementing check?
1.1.2.1.1 Yes Include criteria check in process END
1.1.2.1.2 No Ignore criteria check END
1.1.2.2 No Ignore criteria check END
1.2 No Ignore criteria check END Note: I tried to get this rendering nicely with nested lists, but
you see, this is exactly the problem with patents
companies just try to patent ANYTHING, because if the patent is bullsh*t, then they don't have to be afraid of any harm, except losing the patent application fee (peanuts)
if you really want to stop companies from going on crazy patent application sprees, you have to make them pay big time for trying to patent obvious or non-innovative ideas
I mean a patent gives you a lot of power on a market - if you try to get that much power without really doing something for it, it should be punished like a white-collar crime...
The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
If it wasn't for those meddling F/LOSS kids!
*ducks*
It's true no man is an island, but if you take a bunch of dead guys and tie 'em together, they make a good raft.
Microsoft and it lawyers go after people who "violate" its patents and now it needs to retract a patent after it was discover, it stole, someone else idea. It is funny that Microsoft didn't do any due diligence work on its side before submitting the patent application and with a corporation a big a Microsoft I'm surprise is did with all of the fan fare.
I call BS on that, especially seeing that the submission on /. included two links to stories related and neither was a direct link to an application. Brought to light to Slashdot? Yes, that I can believe.
to give credit to Microsoft for retracting the patent application. Your credibility is nil if you bash them for submitting the application (erroneously) and then don't at least acknowledge the retraction. It is stuff like this that drive people away from our good work like Linux, Firefox, etc. It makes us look like zealots.
Never assume malice, when incompetence will suffice.
http://www.microsoft.com/presspass/features/2005/m ar05/03-10PatentReform.mspx
Regardless of why they did it, they backed off, apologized and cancelled the application. I know I'm coming close to invoking Godwin's Law here, but imagine if Mr Bush were to back off, apologize and cancel the invasion. As in this case, I wouldn't even care why he started the process, I would simply be impressed that he had what it takes to say "whoops" and then stop it.
"There are tons of workalike tools in Unixland that look and behave just like the programs they're knocking off"
Assuming that were true, where did the Open Source developers try and patent these tools.
"Maybe the GNOME desktop is actually a port of Windows' source code, since it looks so much like Windows?"
So it's a total co-incidence that both applications look and behave uncannily similar.
was: Re:Mistake? (Score:4, Mod trolled up)
davecb5620@gmail.com
Only to apply for another (sorry, only in Swedish). According to the article, Microsoft has applied for a patent for modular operating system upgrades, which sound quite similar to the various package management schemes (Yum, Apt, etc) used in Linux and other Unix-like operating systems.
The problem is that the developers are patenting things that they know came from outside suggestions. You may argue that the layers between the idea, the developer, and the patent filers make this a reasonable mistake, but those layers should not be there! There is a reason that the inventor's name needs to go on the patent and not the name of some lawyer or corporate patent assignee: the inventor is supposed to be the person who came up with the idea. Having the inventor sign off on the patent ensures that, at the least, the inventors themselves legally attest that the idea is original.
Microsoft has other cases of patenting outside suggestions and filing patents without developer input. This is not responsible corporate behavior. But corporate behavior is determined mostly by profit motive, and there are rarely direct financial consequences for filing a patent application that the inventor knows to be unoriginal, even if it is technically illegal. So it ends up being cheaper for Microsoft to file patents without taking up valuable developer time to make sure that patent applications are legit -- not an honest mistake but a cost-saving measure.