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
Java API as a whole? | 152 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Java API as a whole?
Authored by: kuroshima on Thursday, April 19 2012 @ 10:29 AM EDT
I think that the Java API could have protection as a compilation at best. To my
NAL eyes, that's how this reads.

[ Reply to This | Parent | # ]

Judge is USL vs BSDI ruled that such class items were not protectable. So why now?
Authored by: Anonymous on Thursday, April 19 2012 @ 11:03 AM EDT
Judge is USL vs BSDI ruled that such class items were not protectable. So why now?

What is the difference between such classes (lists basically) that they deserve protection now?

USL vs BSDI injunction denial ruling

After reviewing the affidavits of Plaintiff's and Defendants, experts, a great deal of uncertainty remains as to what trade secrets Net2 might contain. One fact does seem clear: the header files, filenames, and function names used by Defendants are not trade secrets. Defendants could have printed these off of any of the thousands of unrestricted copies of Plaintiff's binary object code. (Kashtan Aff. at  9-11.) Moreover, the nonfunctional elements of the code, such as comments, cannot be trade secrets because these elements are minimal and confer no competitive advantage on Defendants. The copied elements that contain instructions, such as BREAD and CPIO, might perhaps be trade secrets, but Defendants' experts have argued persuasively that these instructions are either in the public domain or otherwise exempt. As Defendants have repeatedly emphasized, much of 32V seems to be publicly available.

On the other hand, even it Defendants are correct, it is not clear whether 32V is publicly available in a form suitable to BSDI's purposes. There is an enormous difference between an expert programmer sitting down with a pile of textbooks and disjointed segments of code to write out an operating system from scratch, and that same programmer downloading the operating system intact from a public network. In the first case, the programmer could expend large amounts of time writing, testing, and debugging the newly-created system, with an uncertain prospect of immediate success. But in the second case, immediate success would be virtually assured. Thus, even if all of the pieces of the 32V code had been thoroughly revealed in publicly available literature, the overall organization of the code might remain a trade secret unless it too had been disclosed.

On the present record, however, it is impossible to determine whether the overall organization of Net2 has been disclosed. The record itself contains little information directly pertinent to this issue. Moreover, the parties' submissions hint that some of 32V's organization may already be publicly available. Berkeley has apparently released nonproprietary programs such as Net1 since 1987 (Regents Am. Opp'g Br. at 13), programs that presumably have divulged at least some information about 32V's organization.

A further consideration is that 32V's overall organization may not even be protectable in the first place. Berkeley's license to use 32V protects 32V derivatives only to the extent that they contain certain proprietary information. If Berkeley excises the proprietary information (as it attempted to do with Net2), Berkeley is free to distribute derivatives without restriction. Berkeley has utilized this freedom in the past to distribute a number of non-proprietary systems and portions of systems, all apparently without objections from AT&T. These distributions, to some degree, must have disclosed the overall organization of 32V. Thus, Berkeley's activities under the licensing agreement, and AT&T's acceptance of those activities, are evidence that Berkeley and AT&T interpreted the agreement to allow the disclosure of at least some of 32V's organization.

In summary, I find that I am unable to ascertain whether any aspect of Net2 or BSD/386, be it an individual line of code or the overall system organization, deserves protection as Plaintiff's trade secret. Since Plaintiff has failed to provide enough evidence to establish a "reasonable probability" that Net2 or BSD/386 contain trade secrets, I find that Plaintiff has failed to demonstrate a likelihood of success on the merits of its claim for misappropriation of trade secrets. No preliminary injunction will issue.

We are back to basics.

The judge, not being a programmer, seems to be confused.

Maybe should do a shout out (or call a friend)... Does anyone have the USL vs BSDI judge's phone number to give to this judge?

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