| >That's typical - otherwise, you could implement some almost arbitrary
protocol but say it was this one (and use a small amount of it) and claim that
you were shielded from Skype's patents. No, that's what standard bodies are for. No need for stupid patent licenses. Besides, this is exactly why this isn't free. Could I make a format based on Opus, but not conforming to the spec? Maybe
because I had an idea for better algorithms in some parts? No. I cannot take the
parts of Opus which fall under Skype/Microsofts patents and use them in
derivatives. This means that both the implementation as well as the standard are
free and open on paper only. In reality, I am denied freedom number 3 - the
right to distribute modified implementations. Take note that you could just solve this with a trademark on Opus (which
probably already exists). Many large FLOSS projects do that. Firefox, for
example - derivatives are not allowed to call themselves "Firefox" (which I
think is one of the very few valid uses of trademarks). If Skype/Microsoft would be actually interested in a free and open standard,
they would have pledged to let go of these patents. I don't know if you can just
say "this patent is now invalid", but if not, they could hand them over to the
standard body, which could then assure that everybody is allowed to use these
patents until they expire. >Personally I think that's fine. If you want to engage in a full-on patent war,
you should not benefit from a patent license like this. I find it quite funny that people already implictly assume that if someone
starts a patent infringement lawsuit, they are in for patent war. Please tell me
again why we haven't got rid of patents yet? |
Speaking as one of the authors of the spec here, this is very much not the intention. I personally believe a patent license should never be used to enforce standards compliance, and that's not the purpose of that term. Keep in mind, I don't think anyone involved in this standard wants to go around suing people, particularly those interested in implementing and deploying it! In addition to being a gigantic waste of time and money, it would kill the standard dead.
But we specifically included a conformance test to make it easy to know if you met the legal requirements, so you didn't have to trust us. At the request of the working group, this test was made so lax that we worried you could start deleting random lines of code (as an "optimization") and still manage to pass it (to combat this the test also displays a "quality" parameter which drops long before you get to the failure point, so implementors can start marketing that number if their competitors try this tactic, instead of being stuck in a race to the bottom).