The forces backing and opposing software patents in Europe have a new football to kick around. It's called the European Patent Litigation Agreement or EPLA, a proposal for an international treaty that would establish a new European patent court.
Florian Mueller, the founder of the NoSoftwarePatents campaign that last year defeated the proposed directive that would have sanctioned software patents in the European Union, claims this tactics is more dangerous than the last.
"From a software patents point-of-view," he says, the EPLA would have far worse consequences than the rejected patentability directive would have had: not only would software patents become more enforceable in Europe but patent holders would also be encouraged to litigate."
He also complains about an expected "doubling or tripling of the total cost of litigation" per patent dispute.
Despite the downfall of last year's directive, the European Patent Office (EPO) has since 1973 granted tens of thousands of software patents, which can only be enforced country-by-country. Mueller says the anti-patent crowd figures the government officials who support patents would stuff the EPLA with like-minded jurists and that software patents would become further entrenched.
At a hearing in Brussels on Wednesday the EU's internal market commissioner Charlie McCreevy, regarded by anti-patent folk as a pawn of Microsoft, supported the EPLA as a "promising route" and said that he had instructed his staff to move forward with the proposal. McCreevy was a big supporter of the defeated directive.
EPLA supporters include the Fraunhofer Institute, which invented the MP3 format, Bosch, Qualcomm, Siemens, Thomson, the European Aeronautic Defense and Space Company NV (EADS), the aerospace company, and ProTon, the organization of university researchers.
Mueller expects the European Commission to ask the European Court of Justice whether the EU has to get involved in ratifying the EPLA proposal or whether it could be done by any member state to avoid an upset in the European Parliament like last year.
(This story appeared originally in Client Server News.)
About Enterprise Open Source News Desk Enterprise Open Source News Desk trawls the fast-growing world of Professional Open Source for business-relevant items of news, opinion, and insight.
keerthi wrote: Hi Duncan and Frank,
This article is really an interesting one. I found it at a right moment of time as I was trying to implement Page level security in a Project based on JSF.
I was wondering the article is based on Container-Managed Security or reading roles from web.xml. I have a requirement where I need to read the roles from database and not from web.xml, can I achieve this security feature by implementing the points mentioned in this article.
Awaiting for your response.
Thanks and Regards,
Keerthi.
SYS-CON Italy News Desk wrote: Application security - the art of applications defending themselves - represents an important line of defence in an overall in-depth security strategy. Web applications that follow the Model-View-Controller (MVC) architecture can, and should, have security implemented on all three layers. Normally it's the controller component that handles page authorization in MVC, the view layer that hides controls and information based on user authorization, and the model that enforces the business rules and input validation. However, it's up to the developer, based on an individual security policy and the programming technology used, to decide where to put security. Using pluggable validator components in JavaServer Faces (JSF), for example, developers may decide to verify user input on the view layer as well as on the model layer.
AJAXWorld News Desk wrote: Application security - the art of applications defending themselves - represents an important line of defence in an overall in-depth security strategy. Web applications that follow the Model-View-Controller (MVC) architecture can, and should, have security implemented on all three layers. Normally it's the controller component that handles page authorization in MVC, the view layer that hides controls and information based on user authorization, and the model that enforces the business rules and input validation. However, it's up to the developer, based on an individual security policy and the programming technology used, to decide where to put security. Using pluggable validator components in JavaServer Faces (JSF), for example, developers may decide to verify user input on the view layer as well as on the model layer.
JDJ News Desk wrote: Application security - the art of applications defending themselves - represents an important line of defence in an overall in-depth security strategy. Web applications that follow the Model-View-Controller (MVC) architecture can, and should, have security implemented on all three layers. Normally it's the controller component that handles page authorization in MVC, the view layer that hides controls and information based on user authorization, and the model that enforces the business rules and input validation. However, it's up to the developer, based on an individual security policy and the programming technology used, to decide where to put security. Using pluggable validator components in JavaServer Faces (JSF), for example, developers may decide to verify user input on the view layer as well as on the model layer.
JDJ News Desk wrote: Application security - the art of applications defending themselves - represents an important line of defence in an overall in-depth security strategy. Web applications that follow the Model-View-Controller (MVC) architecture can, and should, have security implemented on all three layers. Normally it's the controller component that handles page authorization in MVC, the view layer that hides controls and information based on user authorization, and the model that enforces the business rules and input validation. However, it's up to the developer, based on an individual security policy and the programming technology used, to decide where to put security. Using pluggable validator components in JavaServer Faces (JSF), for example, developers may decide to verify user input on the view layer as well as on the model layer.
Money is being made with Open Source. Some make spectacular money by exploiting Open Source (Google, Apple) and some things wouldn't even exist without it (Internet, Software as a Service, Cloud Computing) - so it really boils down to finding the right business model.
ELASTRA announced Elastra Cloud Server support for the Eucalyptus platform. ELASTRA’s products are designed for portability across compute clouds and currently provide support for the Amazon EC2 and S3 compute and storage environments. Because Eucalyptus exposes its virtual machines ...
Jitterbit has announced the availability of Jitterbit 2.0 Enterprise, which includes new capabilities, scalability and management tools. With this new release, organizations have the ability to solve integration challenges between legacy, enterprise, and on-demand applications and data...
A new API is supposed to integrate LinMin Bare Metal Provisioning 5.2 into environments that haven’t been able to do bare metal provisioning of Windows, Red Hat, Novell, Ubuntu, CentOS, Fedora or Asianux on physical systems or virtual machines before. The rev also features single-com...
The United States Court of Appeals for the Federal Circuit Wednesday overturned a year-old San Francisco district court decision that deprived the aggrieved plaintiff in a dispute over open source software governed by the Artistic License of the right to sue for copyright infringement ...
Google has waded into the encryption business with an open source cross-platform toolkit called Keyczar that’s supposed to make it easier for ISVs to put cryptography in their applications. It says Keyczar supports both encryption and authentication with both symmetric and asymmetric...
SUBSCRIBE TO THE WORLD'S MOST POWERFUL NEWSLETTERS
SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
Click to Add our RSS Feeds to the Service of Your Choice: