Ask Slashdot: Open Patent Licenses?
felipe13 writes "We are working on a new piece of code that will be protected under a GPL license, this is fine for the code itself, but what about our 'innovations'? Are there any 'Open Patent License' models similar to the GPL or Creative Commons? We have Google patenting the highlight of search occurrences, Facebook protecting the word 'Book,' and Apple registering body movements. This is becoming ridiculous to a point. Now the patent trolls are making a killing as well. Does the open source community has a good way to protect its innovations and inventions? There are some initiatives to buy patents and release them to the public or at least place them is a protected area, but where would my very small company register a new way to include titles in a private message? Where could Drupal patent the use of 'hooks' to let developers interact with the core of the application? (If they invented this, I am not really sure.) I don't want to wake up in 10 years and discover that X huge company patented my innovation and that now I actually have to pay them for it." There's OpenPatents.org, there's the Open Source Hardware and Design Alliance, there's CERN's newly-updated Open Hardware license, and there are domain-specific patent sharing organizations like the Open Patent Alliance; what else is out there?
Here's a license: If somebody tries to sue you, punch them in their fucking face.
Harrumph.
GPL is based on copyright which is automatic.
Patents are not automatic, so you need to patent your invention, and worry about (free) licensing afterwards.
If you wanted something more BSD-like, publish without patenting.
The thing that kills patents is prior art. So if you're releasing something to the public domain, make sure to document every step of the way, everything that is potentially patentable. If you invented it first, then with proper documentation, nobody else can patent it...
...at least until the new "whoever files first" rules go into effect.
The CB App. What's your 20?
If you publish an innovation from which you do not intend to profit, and which you would not mind others replication or even would like others to replicate, simply do not file a patent for it. Should anyone ever attempt to do so, your work will qualify as prior art.
contradiction in terms... circuits overwhelmed... head exploding
-- Flame me and I will happily flame you back. Bring it!
Does the open source community has a good way to protect its innovations and inventions?
Innovations and inventions of FOSS? Perhaps when FOSS moves beyond reimplementing proprietary operating systems, applications and tools this will become a more important issue. Seriously, think about it, its pretty common to see FOSS projects primarily described as "A FOSS alternative to the popular and proprietary XXX application". I use FOSS every day and support various project monetarily but lets be honest. Innovative applies to FOSS about as well as it applies to MicroSoft user interface development. Clippy being a notable exception and definite MS "innovation".
As maybe "innovations and inventions" in software if you're not a huge mega corp is incompatible with being in the the US anymore.
"Because we are not employing at entry level, offshoring will kill our industry stone dead."
I'd say that it first helps to understand the differences between copyright, trademarks, and patents. From the submitters question, I'm not sure they actually have a grasp of the distinctions between these three very different areas of IP.
I do not think that is the case. I believe that under both "files first" and "invents first" prior art can cause the patent application to fail. I think the individual hurt by the move to "files first" is the inventor trying to work in secret, trying to postpone filing for the patent in order to maximize the number of years on the market during patent protection and minimize the number of years under development during patent protection.
IP 101 -
Copyright is automatic whenever you create some sort of work, be it art, software or whatever. Published or unpublished. It stops people copying your stuff and passing it off as their name. "Derived works" would include some sort of that work (copied code, your music or whatever) and is illegal unless its 'fair use'
Trademarks: A trademark is protecting a particular name to stop other people from naming their things similarly. For example, if I'm selling my "YouProduct" range, I don't want a competitor to sell "YouProduct2", because it might confuse my clients. Similarly I can't open a company called "Appell" which sells mp3 players called iiPods - even if they look totally different.
Patent: A patent needs to be obtained and protects an idea. If you protect an idea, NOBODY can make something which uses that idea. Software patents are respected in certain countries but others don't (like the EU).
To give an example:
I want to create a news aggregation website. I can't name it slashdotdot because of TRADEMARK. I can't look at slashdot's source code and copy most of it and use it for my own work because of COPYRIGHT. Now if /. copyrighted their moderation method algorithm, I can't use it in mine. REGARDLESS of whether I wrote the code independantly or whatever - this is due to PATENTS.
There.
Just release it. Once public, it become prior art and cannot be patented by someone else. After a period of time (~ one year), you can't patent it yourself anymore either.
You know, for a website that loves to pontificate about patent law every 10 minutes, Slashdot and its editors sure don't seem to know jack shit about the subject..."
(DISCLAIMER: If one of the various "patent reform" bills makes it through Congress and becomes law, and the U.S. moves from a "first to invent" system to a "first to file" system, then all this will probably change. But that's not the state of things right now.
where you might wish to consider basing your open-invention-based business.
Where are we going and why are we in a handbasket?
"Does the open source community has a good way to protect its innovations " Hard to protect that which doesn't exist. Think I am wrong? Then list 5 open source innovations.
An engineering teacher of mine once told me of the "Poor Man's Patent". It is pretty air-tight and really cheap.
As mentioned before, document heavily through the whole process, an periodically send your documentation to yourself through USPS. Because USPS is a government agency, the date stamp on the envelop is considered legit. All you have to do is know what is inside each envelope and DON'T OPEN them. If who came up with the idea first ever came into question, just make sure you present the envelope to an official that can verify that it was sealed.
This requires you to keep an eye on who is trying to patent what, but it is solid.
Where could Drupal patent the use of 'hooks' to let developers interact with the core of the application? (If they invented this, I am not really sure.)
No they did not. Hooks are ancient.
So why not just publish it, making it prior art? Or maybe what you want are Trade Secrets?
What "innovation". I didn't realize that copying Unix and other proprietary OSes and software was considered "innovating".
Thanks to everyone for the great input, what I am getting is that we can be fine with just publishing it and having some piece of mind that our innovations (if there are any) will be protected. presidenteloc: our business model will be based in Costa Rica I guess, which is where we are located. I don't think that we can talk about just one legislation, which is part of the problem here, the us may change the rules, but what about the rest of the world? UE I guess will not give much problems, but there should be a better way to protect stuff. kimvette: that was part of the question actually, where would a clerk like this look? Is there a pool of this innovations somewhere? The links provided here are great, but they don't really provide a solution for new innovations, they are working (as far as I was able to see) on current registered innovations in some countries (us mostly), that is actually part of the questions: Do I HAVE to register my inventions? can't I just do something like a GPL license, include it in my code and live goes on. bennomatic: I will start documenting everything, I will try to provide a platform or repository for this cases, and I hope that it becomes useful for others someday.
If you mean keep something from being patented or least being well enforced later then yes, just publish your source code. It then becomes prior art.
Alternately, if you wish your invention to be in the public domain, you can file for Statutory Invention Registration. This will cause the filing to be in the USPTO database and thus more likely to be found during a prior art search for future patent applications than if it was just published in a journal.
Well, if you did something that is open source, it is released into the wild, right? That makes it prior art. So your defense is that their patent is invalid if it happens more than a year later. But under the current house bill (H.R. 1549) which is now in the Senate for approval, users who were making commercial use of the invention more than a year prior to the filing date of the patent, even in secret, are protected. Also, the status of prior public use or publication is stronger under the first-to-file system than the first-to-invent system. Even one day before the patent application's filing date (with the exception of disclosures prior to your publication by the patent applicant) defeats the patent. So things are looking up if you want freedom. Now, if you want to smite greedy companies for using your idea, that is a whole different kettle of fish.
If you file for a Statutory Invention Registration (or file for a patent and drop it after 18 months), then your filing will be in the USPTO database and thus more likely to be found during a prior art search for future patent applications than if it was just published in a journal.
How about filing regular patents and refrain from enforcing them against others in the F/OSS community, just like Red Hat does?
Unfortunately that does require plenty of cash for litigation if a big corporation decides to challenge the patents anyway.
Then use the patent(s) as leverage to go after companies that don't honour the GPL. For everyone else grant a blanket licence to use the patent provided they honour the open source licence properly.
After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
You can get your patent and transfer it to the Open Invention Network. Open Invention Network (http://www.openinventionnetwork.com/) creates a pool of patents that are licensed to anyone who promises not to sue anyone in the open source community. Basically if a company promises not to sue over the use of one of their patents, they can use all the patents in the Open Invention Network portfolio too.
in copyrights, copying is relatively cheaply and efficiently proven and so people respect them by default
Is lack of copying also "relatively cheaply and efficiently proven"? Say I've written a song. How do I know whether I am the legitimate author or whether it's an unauthorized derivative work of something I had heard in grade school?
The idea behind the Open Patent License is for owners of patents (and non-patent IP that still ends up behaving like patents from a practical real-world extent--amazing how that actually happens) to be able to license them in a copyleft-type manner, ideally handling more than just the software patent situation.
The goal is for all players to be able to participate in a growing patent pool and have open and free access to this pool under copyleft-type conditions, whether they're small players or larger players.
Don't be thrown by the badly-worded license--I had it as a starting-point for discussion/work, getting ideas out there, and ended up having a few lawyers come out of the woodwork, offer to help, then realize it was a bigger project than they had expected. After a number of rounds of that I ended up putting the project on the back burner, as you can see. I need to get it more active again. Anyone who is interested in contributing in any sense, please contact me.
Also, I've since realized that a far, FAR, shorter license probably makes sense. A structure of something similar to Google's license from their CLA for instance, or Redhat's patent promise, made a bit more generic and made to cover patent-like IP, is probably a better idea, and I am planning to re-start the license wording along those lines.
I will happily accept help from anyone who is interested.
The USPTO has a free option to the standard patent application. This is called a defensive publication, which allows the inventor, in this case the OSS author, to publish the work within the USPTO's databases so that examiners will be able to reference these things when rejecting a patent. The examiners in the Patent office don't have the time to dig through all of the work done by the open source community, but if the OSS community is serious about protecting it's innovations, it can start submitting these defensive publications, which give them a more official grounding in the public domain.
If you want to keep your innovations open "always be publishing." Blog about what you intend to build or are already building. Describe the invention in enough detail for someone "practiced in the art" to duplicate it. Describe its uses, but of course do not limit the uses to only what you can think of at the moment. Describe enhancements even if you do not intend to implement them. List your references for where you got your ideas. The more dots you connect, the more someone coming along has to be truly innovative to patent.
IMHO, you need to talk to a lawyer (sometimes before you even start the project so you don't waste your time), I doubt a good one would charge you unless s/he had to file the patent themselves (lawyers file the majority of these) and if you find the right ones, they deal with it as a large part of their living (ex. defending a patent). What you may find is things get handled on a case to case basis with patents because of all the complex rules and regulations surrounding them.
Be sure to use the GPLv3 license if your primary goal is to perpetuate the openness of the patentable attributes of the work you release and its derivatives.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Release your product everywhere but the US. That is the only way to avoid the Trolls. If enough people do that, maybe the situation will change.
or even if you deliver a product containing the invention in question, without publishing a description of how it works. Publish or ship => prior art, unless they filed before you did that. If you really want it to be open, then publishing is the simplest path.
If you publicly disclose something that would make it prior art and thus not patentable if the patent office is aware of it during the application process. They're not always aware of it, so prior art being patented is not uncommon. It's happened to some stuff I put into public domain on SourceForge 3 years prior to the patent application. The patent holder in question is Oracle which acquired it through their Sun acquisition. You're perfectly welcome to take on Oracle here. You'll lose. It's an unlevel playing field tilted in favor of the patent holder, legitimate or otherwise. And Oracle's lawyers are much bigger than your lawyers.
Reform patent laws, or move to another country, are the options I see... and the former one doesn't appear to be happening in my lifetime, which leaves only the latter... It makes no difference if a patent is invalid, it takes you way more money to prove it so than pay up usually, so you just have to pay up... no pay, no live in this country, simple as that.
With so countless elegance benefits ghd uk is getting the regular of option for mind of hair salons all over the civilized world. Available in three completely different sizes: Mini, Travel Ghd Australia , and large Buy Ghd is important possession for not just females but grown up men also.
Best Ghd Hair Straightener
Under the version recently passed by the House, a person can get a patent unless "the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention..."... Instead of being "know or used" it has to be printed, patented or "otherwise available to the public."
No problem, create a small ad that describes the invention. Place that ad in your local newspaper. The letter of the law cuts both ways.
why isn't there an insurance company that insures against ms style extortion? if it were to pitch a policy to me as an android
owner that MS can't come after me as a customer for android, I'd be happy to pay 15$ (MS protection fee) to protect myself from
MS protection/extortion. It seems to me that an android user is just as vulnerable to MS extortion as music users who download
from "free" music vendors. it seems to me that they could then afford defend any company in an 8 year osl style legal system abuse strategy by MS. All it takes is a very large pot of money. I've heard the argument that MS has a lot of lawyers and money but if enough users take them to local courts the economic costs should start to seriously hurt these crooks. I'd pay a fee for protection for any programming I do that could be attacked by these racketeers. I'd pay a fee to be able to use any GPL software and not have to worry about MS extortion. I'd pay a fee if someone would stand up to these crooks. the same principle applies to music IPR issues. I'd pay a fee to use dropbox or any other music-to-the-cloud mechanism without worrying about the recording companies legal system abuse. Why haven't the vendors of these services put together an insurer for that purpose? End users will pay a small yearly fee to avoid the Music industry legal extortion. Are the vendors of these services too stupid or too greedy to come together an create such an insurer?
Why hasn't there been a class action suite based on the 15$ per device damages we suffer for this extortion? Surely the Android industry can put together a "class" that has suffered damages from MS extortion (in various forms) selecting either from end users or vendors? If vendors are still paying fees for machines shipped without windows, that is also extortion. why can't we compensate for this extortion by legally bleeding them the way they go after small vendors? The legal conflict IS sensitive to cost.
Why isn't there an insurance company that insures people/businesses/corporations from legal extortion?