decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Subset | 393 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Directional compatibility
Authored by: Anonymous on Friday, May 25 2012 @ 10:55 AM EDT
Maybe it's the phase of the moon or something, but just why is
it Android's responsibility to not fragment Java? It's not
like they are claiming to BE Java. They are only claiming to
be similar (syntax, functionality) at the source code level.

As far as compatibility goes, to borrow and paraphrase a bit
from MS, it doesn't need to be fully compatible, it just needs
to be "compatible enough" to make developers comfortable and
productive without enduring a big learning curve.

[ Reply to This | Parent | # ]

Directional compatibility
Authored by: rkhalloran on Friday, May 25 2012 @ 11:02 AM EDT
Can we expect a suit from Lucent/Alcatel against Microsoft for infringement of C
by C#?

Oh wait, they're not trolls, sorry...

---
SCOX(Q) DELENDA EST!!!

------
"They who can give up essential liberty to obtain a little temporary safety
deserve neither." - Benjamin Franklin

[ Reply to This | Parent | # ]

Pot Calling the Bumper Black
Authored by: mcinsand on Friday, May 25 2012 @ 12:18 PM EDT
(BTW, I like that subject line, because I'm using the bumper for Google, bumpers
are usually chromed, and, well...)

For those of you that remember records, I'm going into broken record mode,
especially with Oracle accusing someone else of fragmenting Java. As I said a
couple of days ago, I was using Sun/Oracle Java to avoid headaches until I
started having headaches after a recent upgrade. One of the key Java
applications I use is KoLmafia, which makes managing a KingdomofLoathing (<a
href="http://en.wikipedia.org/wiki/Kingdom_of_loathing/">silly
online game</a>) accounts far, far easier. When I started using it, the
project page warned Ubuntu users, in particular, to only use the Sun version.
Since my sons got me started playing <a
href="http://www.minecraft.net/">Minecraft</a> last year, I
have also been running the client and server software. Both of those are Java
applications, so I have three apps that run regularly, with the server running
whenever the computer is on.

February of this year, I ordered the following PC assemblage, with the intent of
also moving beyond Kubuntu 11.04:
Biostar N68S3B GeForce 7025 Motherboard - Micro ATX,
NVIDIA MCP68S Chipset, 1333MHz DDR3, SATA 3.0 Gb/s,
RAID, 6 Channels Audio, GeForce 7025, Fast Ethernet

Then, it hit the fan to make for a horrible weekend where the apps just would
not run. Since Sun/Oracle Java had always been the safest way to go, I spent
days in frustration to look elsewhere for the culprit. It was only in
desperation that I tried using OpenJDK instead. This isn't just an Ubuntu
issue, but it was the same in Debian Squeeze and Fedora 16.

If Oracle is concerned about Java fragmentation, then maybe they ought to stop
fragmenting Java!

[ Reply to This | Parent | # ]

Directional compatibility
Authored by: Anonymous on Friday, May 25 2012 @ 01:24 PM EDT
Android apps can't run in Java, either. They use Android APIs that aren't part
of the Java platform (in addition to the 51 Apache Harmony packages that do have
compatible equivalents in the Java platform).

[ Reply to This | Parent | # ]

Directional compatibility
Authored by: PJ on Friday, May 25 2012 @ 02:41 PM EDT
Wait, guys. Take a look at that footnote about the appellate brief [PDF] by Connectix. It tells us more about exactly what Connectix did. Can you please read it and tell me if it matches as closely as Google describes?

[ Reply to This | Parent | # ]

Subset
Authored by: Anonymous on Friday, May 25 2012 @ 03:17 PM EDT

Not a subset. A platform with an non-empty intersection in the libraries, but, as I think I'm understanding from comments, a different way of entering a program from java's standard method "public static void main(String[] args)." That right there, if I understand it correctly, means unmodified java programs will not run on Dalvik. As a practical matter, source code in a higher level language requires transformation into machine code: one could design a compiler that accepts both styles of entry points, so the entry point convention, in a sense, is not a part of the language, but a part of java's compiling program, javac. The GNU compiler, gcc, understands quite a few languages. All to saying, what, exactly? If keywords and syntax rules match, two languages are the same. A choice in keywords and syntax rules cannot be protected, because these are ideas. They can't be patented because they are the mathematics of a formal language and grammar.

PJ asked a question.

I think Google does a nice job of explaining how Sony v. Connectix supports their claim that what they did is allowed under commonly understood legal precedents.

Oracle, though, makes a good point that java is not a device, so that case was about something else.

Oracle may be faulted by not acknowledging the real issue, which is not whether java affinity for Android development is a virtualized game player, but whether the method of copying and the key point regarding Connectix's fair use by virtue of not using (or decompiling) Sony's source code applies.

Or in other words, it's not enough to say it was about something else, Oracle has to seriously address the point that the legal concept has zero application to this case.

Failing to do so, I think Oracle by omission highlights the correctness of Google's briefing regarding Question III.

[ Reply to This | Parent | # ]

Directional Compatibility Summary
Authored by: Anonymous on Sunday, May 27 2012 @ 05:39 PM EDT
Sega situation: An alternative implementation of the game production programming libraries that can be used to produce games that run on a Sega console. J. Alsop Question: Can Android products run on a JRE?

Sony situation: An alternative implementation (virtual) of a Sony Console that can execute existing game programs. J. Alsop Question: Can Java products run on Android?

What are the contested products?
Sega: Game Title (Application).
Sony: Game Console (Runtime).

Oracle: An Application is equivalent to a Game Title. A Runtime is equivalent to a console. Dalvik does not execute java JRE programs therefore Sony does not apply; Android programs do not execute on a JRE therefore Sega does not apply. If neither Sega or Sony applies, then what does apply? Why infinging SSO of course.

Oracle's Problems:

  1. Many JSE programs do run at the android command line.
  2. The JDK and Android SDK are product production platforms. Both platforms include the concept of library and application as products. Oracle's attempt to limit the definition of product to application has generated much derision on this site, nothing else needs to be said, except:
    Oracle's Pure Java JDBC drivers, a library product, work on Android in bytecode form, no source code required. So what? Well, this is a very important peice that enable Java Applications to interoperate with Oracle's database products.

    See here:Android - Oracle JDBC example

  3. Since all Android applications and libraries are compiled into .class format and then converted into .dex format, many libraries built for Android are compatible with JRE execution.
Therefore, if a library is a product (and Oracle does produce library products) then Sega and Sony both apply in their entirety. Many products (planes, trains, automobiles and computers to name a few) are assembled from subassemblies, which are products in their own right (motherboard, memory, disk); The same is true for software products where the subasemblies are called libraries.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )