Owning a property doesn’t give you the right to sue other people who develop a property that offers the same services.
Owning a property doesn’t give you the right to sue other people who develop a property that offers the same services.
If I write a book and you read it, love it, and then retype the book, print it and sell it, you have violated my property rights.
You and many others here don't want it to be that way, but it is exactly that way.
Bad analogies are inevitable, and aren't the commenter's fault. It's the Federal Circuit's fault, for trying to blur the lines between functional matters (the domain of patents) and copyright matters. Any analogy that's simple enough to quickly understand will suffer from basically this same flaw, or else not apply to this case.
Ultimately, the problem for Oracle is that the APIs are too functional to be eligible for copyright protection, too abstract to be eligible for patent protection, and too generic to be eligible for trademark protection. But that doesn't stop them from trying to get the best features from all the above.
One is an accurate analogy, the other is a false analogy.
"Jack and Jill ran down the hill."
into
"Gil and Jacky descended the mound."
It's exactly the same story just with different implementations that exhibit the same behavior. They didn't make something compatible with Java -- they replaced Java with something exactly like Java.
It's even worse than the example above, because they kept the same names of the classes, interfaces, etc.
What is protection supposed to mean there? Happy to expand my definition of that word if I am interpreting it too narrowly.