Re:Oracle v. Google and the future of software development
by monocasa on Thursday January 24, 2019 @10:31PM
(#18995324)
> I see no reason API documentation would be viewed any differently
It's not the API documentation that's at dispute here. It's literally the abstract "structure, sequence, and organization" of the API. And there's tons of ninth circuit case law that sso isn't copyrightable.
> I never said it had to be perfect, just that the reason for using the API is for interoperability -- WINE is exactly that. It allows software that was designed for Windows to run on Linux.
What's the test here that a court can use to make that distinction? And just letting you know at one of my former jobs, we modified our codebase to better run on Wine a few times.
It's not the API documentation that's at dispute here. It's literally the abstract "structure, sequence, and organization" of the API. And there's tons of ninth circuit case law that sso isn't copyrightable.
> I never said it had to be perfect, just that the reason for using the API is for interoperability -- WINE is exactly that. It allows software that was designed for Windows to run on Linux.
What's the test here that a court can use to make that distinction? And just letting you know at one of my former jobs, we modified our codebase to better run on Wine a few times.