11 ms·
What's the difference between "a method for sorting an array of integers by doing <steps of Quicksort>" and simply patenting Quicksort? Or do you mean something
by baddox 14y ago
What's the difference between "a method for sorting an array of integers by doing <steps of Quicksort>" and simply patenting Quicksort? Or do you mean something more specific to a particular product, like "a method for sorting a list of restaurant recommendations by doing <steps of some machine learning algorithm>"? Either way, all I'm seeing is algorithms.
- JoshTriplett 14y agoBecause you can't directly patent an algorithm, software patents use all sorts of fascinating workarounds to pretend like they've patented something else instead. A typical software patent will include the same patent claims written several different ways, based on legal precedents used with software patents in the past. A patent on an algorithm for fooing bars via steps A, B, and C, with the additional claim of doing D while fooing, might have one set of claims: 1. A method for fooing bars, comprising A, B, and C. 2. A method in accordance with claim 1, wherein said fooing further comprises doing D. 3. A system for fooing bars, comprising A, B, and C. 4. A system in accordance with claim 3, wherein said fooing further comprises doing D. 5. A computer program product for fooing bars, comprising A, B, and C. 6. A computer program product in accordance with claim 5, wherein said fooing further comprises doing D. This covers several different legal precedents; even if "method" gets invalidated as an approach, the patent may still work under the "system" or "computer program product" theories. This gets taken to a ridiculous extreme; many such patents describe the computer program product as a physical object consisting of bits on a medium such as a CD or disk, and include as a figure an illustration of such a medium.
- diminoten 14y agoIt's not pretending, they actually are patenting the method rather than the code itself. It's a critical distinction, as code is actually copywritten. There's a huge difference between design and implementation.
- hackinthebochs 14y ago(I'm no expert at software patents so take what follows with a healthy dose of NaCl) It seems to me the difference is a question of "real world implications". For sorting integers using quicksort, yes that's just a mathematical algorithm: an algorithm that performs operations on mathematical entities. The moment you apply that algorithm to something that affects the real world, that's when it becomes patentable. E.g. sorting restaurant recommendations by applying quicksort to the individual rating. This is no longer simply a mathematical algorithm; the entities being manipulated have a 1:1 correspondence with entities in the real world. It is recognizing the usefulness of this particular correspondence between mathematical entities and real world results that is patentable.
- uxp 14y agoI'm no expert either, but I will take offense at your statement. It's everything I think is wrong with the patent system. Sorting is a mostly solved problem. You take a group of numerical things and end up with a group of numerical things that are now sequential. You can either do it slow, fast, or stupidly. If you have the example of ratings of restaurants, you're going to have some kind of group of numbers. If you want them sorted, you use a predefined and should-be unpatentable algorithm and sort the damned list. But your business model shouldn't be sorting a predefined list, because that's a really stupid business model and any fucking person can do it. Your business model should be to find a unique and novel way to rate restaurants (social graph, Zagat, number of cockroaches found in soup, etc.). The outwards facing UI of that rating system should be entirely disconnected from what your patent does. The order of that list is, yes, directly connected to how you rate restaurants, but the end result itself is not exactly how you rate them, it's just representative of the end result of your rating. Think of Page Rank. Anyone can crawl the web and get a list of pages on the internet. Anyone can then sort that list by whatever means they want. It's not the sorting that is patentable, it's the association of some qualifier into a numerical representation of which gets sorted by another un-patentable system that is the "secret sauce".
- hackinthebochs 14y agoI think you misunderstood my comment. My point wasn't to justify patenting sorting (that would be stupid). It was just an example to clearly show the difference between an algorithm and an application of an algorithm. In the case of sorting (replace with arbitrary algorithm X if you prefer), its discovering a unique and non obvious mapping from the mathematical entities that are manipulated to the real world that is patentable, rather than the algorithm itself. The point I'm making is simply that patenting an application of an algorithm is fundamentally different than patenting the algorithm itself, so claiming software patents are invalid "because math" is missing the point.
- rayiner 14y agoIn the second case, you're not patenting the algorithm, because people remain free to use the algorithm to do things other than sorting lists of restaurant recommendations. Which is ultimately why "its all just algorithms" is a uselessly reductionist view of things, in the same way "all creative works are just strings of bits" is uselessly reductionist, or even "all physical objects are just globs of atoms" is uselessly reductionist. It's not a useful level of abstraction at which to view the issue. Ultimately you have to tie it back to the purpose of the property right. Why does someone have a legal right to a particular glob of atoms, or a particular string of bits, or a particular series of steps of some algorithm in some specific context?
- georgemcbay 14y ago"In the second case, you're not patenting the algorithm, because people remain free to use the algorithm to do things other than sorting lists of restaurant recommendations." That doesn't make the situation any better, in my mind. In fact, in many ways that makes it worse. Step 1) File patent for using algorithm (everyone knows) to do (some obvious application of that algorithm). Step 2) Wait around for some other poor sucker to do the hard work of actually implementing "your" idea. Step 3) Profit!
- rayiner 14y ago1) In theory you wouldn't be able to file patents without a working prototype--we've unfortunately gotten away from this requirement; 2) That assumes "implementing the algorithm" is the hard part.
- georgemcbay 14y agoIMO/IME, implementing is always the hard part. I agree with your #1 though in that I think you should absolutely be required to have a working prototype to file a successful patent. A lot (though not all) of my objections to software patents would go away if that were enforced.
- deleted 14y ago
- baq 14y agoyou patent "a method for sorting an array of integers by doing <steps of Quicksort> on a computer". want to use the algorithm? go ahead, doing it with a pencil and some paper is ok (i believe).