|
Authored by: Anonymous on Monday, May 21 2012 @ 11:28 PM EDT |
> For purposes of this subsection, the term
> “interoperability” means the ability of computer programs
> to exchange information, and of such programs mutually to
> use the information which has been exchanged.
Yeah it feels like we are having to try and stretch their narrow definition of
interoperability. Compiled programs can't operate on both systems and so are
therefor not interoperable. New or existing source code and custom libraries
can operate on both systems though.
Now you could argue that Java source code IS a computer program as the compiled
version is just another version of the same thing represented in a new form.
Now clearly the source code exchanges information with the Java libraries back
and forth. And it is a requirement that the interface between them which is the
Java API's has to be much the same or they will not be able to exchange or use
information. So clearly this would be interoperable by that DMCA definition of
interoperability. However because they have not implemented all the API's and
had to implement new android API's to make it useful for its market this makes
it not fully interoperable. Parts of the source code written using the core
Java API will of course be interoperable between the two platforms but not
complete applications unless they are specially recoded so that the any required
differences are compiled in correctly when you select the target platform
(Android or J2SE).
Now if they had chosen not to use any of the Java API's then the source code
programs would have no level of interoperability at all.
Michael[ Reply to This | Parent | # ]
|
|
|
|
|