7 ms·
There are specific exceptions for compatibility. Android Java never tried to be compatible, various required APIs were replaced or are just flat out missing fro
by josefx 6y ago
There are specific exceptions for compatibility. Android Java never tried to be compatible, various required APIs were replaced or are just flat out missing from the runtime library.
- ysleepy 6y agoOf course it's about compatibility, about code-reuse of existing libraries. – Which is done a lot to this day.
- curt15 6y agoWhere are such compatibility exceptions articulated? Section 107 lists four factors for fair use, including "the amount and substantiality of the portion used in relation to the copyrighted work as a whole." Trying to achieve full compatibility would seem to require copying more of the original API, not less.
- wtallis 6y agoUsually when someone on Oracle's side brings up compatibility, they are referring indirectly to the test suite required for using the Java trademarks. And they usually are also implying that compatibility should be defined solely by Sun/Oracle, ie. that Oracle should be allowed to require your own Java implementation to be fully functional and 100% compliant to their spec before it is in any way legal, and implementing a mere subset of relevant functionality is not permissible.
- josefx 6y agoAfter going over the laws(i am not a lawyer) my reasoning might be a bit backwards. I think it would not be a 107 exception but an argument over the technical facts and the creative work contained in an API. To be compatible you have to create a copy of the facts an API describes and copyright is rather limited on collections of facts.
- gpm 6y agoI don't believe there is any existing specific exception that allows for completely compatible API s (which you appear to be claiming sql is) but not partially compatible ones (Java). Can you cite a source for this claim?