Microsoft Is Sued For Patent Violation Over .NET

randomErr writes "As reported by Info World, Microsoft was issued a cease and desist order on February 7 of this year by Vertical Computer Systems. The order was for patent infringement by the current implementations of the .NET framework. Both the .NET framework and Vertical Computer Systems' SiteFlash use XML to create component-based structures that are used to build and operate web sites. Vertical Computer Systems is requesting a full jury trial. If VCS prevails, .NET technology implementations as we know them may completely change and Microsoft would probably have to pay out a hefty sum."

Comments

Some basic background information

[udippel]

As former patent examiner I am appalled that something like this was granted; or had to be granted:

Claim 1. A method for generating a computer application on a host system in an arbitrary object framework that separates a content of said computer application, a form of said computer application and a functionality of said computer application, said method comprising: creating arbitrary objects with corresponding arbitrary names of various object types for generating said content of said computer application, said form of said computer application, and said functionality of said computer application; managing said arbitrary objects in an object library; and deploying said arbitrary objects from said object library into a design framework to create said computer application.

This grants the patent owner all rights to royalties to a system that any third party brings to the market within the time frame of validity of this patent, and that uses this method.
In technical terms it is obvious; and probably anticipated a few hundred times. In legal terms this is different. As patent examiner you'll find yourself in a quagmire: you may have prior art for the concept, but not for the wording. I agree, that anticipating the concept should be enough. But the vultures of lawyers will pull you apart within minutes, and the chambers and courts of appeal will usually folllow (and your bosses rebuke your rejection of the application). You will be asked for a document to anticipate the wording, and that might not exist.
Only in high-profile cases will the parties drill down to the concepts. Why ? Because that is very costly, and if nobody forks out these costs, the average examiner will have to grant.
Of course, the wording is overly broad. But try to cite a 'library' against it: would it be a 'object library' ? Is pulling in a function ('printf') pulling in a function of a 'object library' when C is doubtlessly not object oriented ? Let us continue with the 'object framework'; more so one that separates: content - form - functionality. Where in the 'prior art' cited here can we make out 'various object types' (not one, that is !). How do you anticipate the 'managing ... objects ... in a library'; as well as 'deploying ... objects ... into a design [!] framework' ?
FYI: All this would have to be anticipated in a (usually) single document, before October 1, 1999.

No, I am not all trying to defend the vultures of applicants. This patent ought to never have been granted.
But one should keep the following in mind as well: The USPTO was never willing to grant software patents, actually refused to do so, but was - in the 1981 case of Diamond v. Diehr - forced to do so by the U.S. Supreme Court. It was not the - then - P.T.O. that started the insanity. It wasn't your House of Representatives or the Senate. Though the House would be very much encouraged to change the legal framework ... !