I don't know if this has been mentioned previously, but I've not seen it in any of the previous debate about software patents. Quoting from the article: Patents are meant to foster innovation by protecting the inventor and then upon expiry providing a library of information for others to build on. To this end, going forward, if a patent doesn’t actually tell you enough information to understand and build the inventio…
The patent to invalidate software patents
11–17 of 17 posts
Re: The patent to invalidate software patents
#12I don't know if this has been mentioned previously, but I've not seen it in any of the previous debate about software patents. Quoting from the article: Patents are meant to foster innovation by protecting the inventor and then upon expiry providing a library of information for others to build on. To this end, going forward, if a patent doesn’t actually tell you enough information to understand and build the inventio…
Re: The patent to invalidate software patents
#13Re: The patent to invalidate software patents
#14I don't know if this has been mentioned previously, but I've not seen it in any of the previous debate about software patents. Quoting from the article: Patents are meant to foster innovation by protecting the inventor and then upon expiry providing a library of information for others to build on. To this end, going forward, if a patent doesn’t actually tell you enough information to understand and build the inventio…
Re: The patent to invalidate software patents
#15I don't know if this has been mentioned previously, but I've not seen it in any of the previous debate about software patents. Quoting from the article: Patents are meant to foster innovation by protecting the inventor and then upon expiry providing a library of information for others to build on. To this end, going forward, if a patent doesn’t actually tell you enough information to understand and build the inventio…
I really like that idea, I am sure I am missing some important part that makes it not so easy to do. When you file a patent for invention like (dishwasher) you have to supply all the design drawings for the project. I do not see why they could not do that with software patents.
Actually, you don't. Look at some patents, such as http://www.google.com/patents?id=TdUkAAAAEBAJ&zoom=4&... .
Notice that the drawings for that showshoe binding patent are not "design drawings" for a snowshoe binding. (Those drawings are lacking a lot of dimensions that one would need for such a product.)
You have to provide information that tells someone skilled in the art how to do what you claimed. That's it.
FWIW, "What you claimed" is rarely a complete product. Instead, it's an aspect that can be used in multiple products. (While I don't know where else one might use that snowboard binding mechanism, I'm sure that someone else does.)
Re: The patent to invalidate software patents
#16I don't know if this has been mentioned previously, but I've not seen it in any of the previous debate about software patents. Quoting from the article: Patents are meant to foster innovation by protecting the inventor and then upon expiry providing a library of information for others to build on. To this end, going forward, if a patent doesn’t actually tell you enough information to understand and build the inventio…
What about software that relies on proprietary hardware etc.?
Though a general solution to proprietary hardware that you have rights over would be to include an FPGA implementation... whether that should be required or not is another story, especially if you don't have rights over it.
Re: The patent to invalidate software patents
#17I don't know if this has been mentioned previously, but I've not seen it in any of the previous debate about software patents. Quoting from the article: Patents are meant to foster innovation by protecting the inventor and then upon expiry providing a library of information for others to build on. To this end, going forward, if a patent doesn’t actually tell you enough information to understand and build the inventio…
"Actual, working code" might be prohibitively context-dependent. Working code to detect credit-card fraud would be pretty dependent on your financial infrastructure. In many cases though, that would not be as big a problem, and in others it might be satisfactorily overcome. I think this is a good idea.
I can't think of a single approach that would work everywhere, but logically isolating it as a library or service might work, similar to the way in which you can implement an IPC/RPC shim for interfacing to GPL'd code from your proprietary app.
Inventions that don't fit that model (Operating Systems, Embedded Firmware, Massive Scale, etc) complicate the matter, but I imagine a set of disclosure options could be devised, and the inventor/patent office would select the most appropriate.