stories filed under: "database"
Creating A List From A Database? Prepare For A Patent Infringement Suit
from the promoting-what-progress? dept
Thanks to the whole slew of folks who sent this in: TechCrunch has the details on Channel Intelligence, a company that owns a ridiculously broad and obvious patent on creating a list from a database and is now suing a whole bunch of small websites that offer things like wishlists. Read through the claims of the patent and see if you can explain how a single one is possibly new or non-obvious to those in the space. As TechCrunch notes, the lawsuits are all targeted against smaller websites, rather than the big players like eBay or Amazon. There are a variety of reasons why this might be. Channel Intelligence may have approached those companies and actually received a token payout (cheaper than a lawsuit for those companies). Or, perhaps more likely, it's using these smaller lawsuits to bring in some additional cash and to establish the myth that this patent is valid. That was common a few years back, before people started suing everyone at once for patent infringement. Patent holders would mostly target a few small companies, who wouldn't be able to launch a strong legal defense -- use those "victories" to build up a warchest while also claiming that it showed how the patents are "valid."Filed Under: database, lists, obviousness, patents, wishlist
Companies: channel intelligence
The Problem With A Database Of Prior Art Is You Don't Know What's Worth Putting In
from the not-so-easy dept
Dan Berninger, who I almost always agree with, has tossed out a suggestion for how tech companies can deal with situations like the one where Verizon was able to squeeze millions of dollars out of Vonage using patents that clearly never should have been granted, as there was tremendous amounts of prior art on the patents (much of which was brought to light by Berninger himself). His suggestion is that tech companies should create "a formal process of contributing software innovations to the public domain." It's one of those ideas that sounds good in theory, but won't work in practice. In the past, we've explained why similar ideas (such as a database of "obvious ideas" for the sake of prior art) will never work.The main reason: if you're not in the business of generating patents, you generally don't think all of the little things you do are worth patenting or dropping into a database. They just seem obvious and natural, so you don't even bother. It's only in retrospect -- when someone else has patented the concept -- that people start to realize that they wish they had some sort of record of the obvious ideas they had or things they did years before the patent was filed. Sure, people will submit some ideas here or there, but it simply won't seem worth it to many people, especially on very minor things, or very broad things like setting up a hands-free kit in a car. That seems so obvious, why would you even think to patent it... or put it in a database of prior art? So, while it's a nice idea in theory, it will fail in retrospect, because the ideas and concepts that need to be in a database will seem so obvious that people won't bother entering them until it's too late and someone else already has the patent.
Filed Under: database, patents, prior art, public domain
Spying On Your Ex-Girlfriend Not Quite What Homeland Security's Database Is For
from the just-saying... dept
Every time we hear of yet another plan for the government to set up yet another database of information about people, we wonder about how it will be misused. Supporters always talk about how helpful such databases are (which is debatable), but rarely are willing to take into account how such systems are going to be abused -- and they're always abused. The latest such case involves an employee at the Department of Commerce who used a Department of Homeland Security database to track an ex-girlfriend. This wasn't just a one-off thing either. He apparently used the database 163 times to check up on her. Then he threatened to have the woman deported and her family killed. So, as the government continues to push the boundaries in trying to collect more and more data on everyone, it's at least worth asking if the potential for abuses is taken into consideration and how they're dealt with (if they're dealt with at all).Filed Under: database, homeland security, privacy