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
Reverse engineering vs. copying | 238 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Reverse engineering vs. copying
Authored by: Anonymous on Tuesday, April 24 2012 @ 06:41 AM EDT
Would it depend on how you did the reverse engineering?

If you take the published header files or documentation it would be copyright
infringement. However if you take example programmes that are meant to work and
create the necessary calls underneath them or observe the communications on the
wire and emulate them fully reverse engineering the functionality with no
copying process you would be legal.

This approach would probably mean that Samba is safe but WINE is not.

My preference is for the API itself to be usable to better allow competition and
compatibility but I don't see any reason that at least the UK copyright law
would allow it although I believe the US law has wider and stronger fair use
rules that could potentially cover this public good.

What I really don't understand is why Google chose Java for Android rather than
any of the other possible languages. Sun were known to restrict the profiles
that could be deployed on different sorts of platforms and expected license fees
(and other restrictions such as having to use the logo) on hardware including
the JRE such as Blu-ray players and TV's supporting MHP (still used in Italy).
I guess that there were also fees for the mobile platform too. Sun were always
reluctant in opening up the development process and the platform.

If I had to guess they may have expected that they would be the ones to buy Sun
but Oracle got there first.

[ 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 )