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
Parties File Sealed Trial Briefs; Novell's Redacted Amended Trial Brief, as text
Thursday, April 24 2008 @ 03:28 AM EDT

Trial briefs have been filed by the parties in SCO v. Novell. Novell filed one originally filed back in September of 2007, but SCO filed for bankruptcy in Delaware instead of filing a trial brief in Utah. Now, having failed to escape the trial in Utah, which is now scheduled to start on the 29th, it has finally filed a trial brief, although it's not yet available in a redacted version for the public. Novell's redacted Amended Trial Brief [PDF] is available, however, and I have it as text for you.

Comparing the two versions is interesting, in that we see Novell's carefulness in answering all that SCO has raised recently, including the argument that when it said UNIX System V, it meant UnixWare, because that is where UnixWare comes from. Novell points out that it doesn't matter where UnixWare came from, since SCO has only identified Unix System V pre-APA code as allegedly being in Linux.

And we learn that SCO, judging by its briefs filed to date, isn't going to be presenting any SCOsource licensees as witnesses. Instead, Novell says SCO apparently plans to argue what the licensees *intended* to license. Novell calls that hearsay, and so, once again, Novell must raise Ye Olde Rules of Evidence, specifically the hearsay and parol rules of evidence. Some things about SCO never change.

Morrison & Foerster are not just phoning it in, in other words. They've taken care to leave no stone unturned, including presenting new cases to support the additional arguments.

Here are the filings:

521 - Filed & Entered: 04/23/2008
Notice of Conventional Filing
Docket Text: NOTICE OF CONVENTIONAL FILING of TRIAL BRIEF ON BEHALF OF THE SCO GROUP, INC. filed by Counter Defendant SCO Group (Normand, Edward)

522 - Filed & Entered: 04/23/2008
Redacted Document
Docket Text: REDACTION to [519] Sealed Document Novell's Amended Trial Brief by Defendant Novell, Inc.. (Attachments: # (1) Exhibit A, # (2) Exhibit B)(Sneddon, Heather)

523 - Filed & Entered: 04/23/2008
Notice of Conventional Filing
Docket Text: NOTICE OF CONVENTIONAL FILING of Novell's Amended Trial Brief filed by Defendant Novell, Inc. (Sneddon, Heather)

Here are the other tweaks I note to Novell's trial brief:

  • Regarding the Microsoft SCOsource revenue, there is now a breakdown, with Novell seeking the entirety of Section 2 and 4 revenue, but not Section 3 (although Novell states it believes it could make a case that at least some of the Section 3 monies are due to Novell; it just doesn't want to bother for this trial).

  • There is a new category: namely that SCO can't carry its burden to show entitlement to SCOsource revenue. More on that in a bit.

  • A dropped category, where the original asked for prejudgment interest at 7%. But it's dropped only from this trial; Novell in footnote 4 says "Novell will address additional recovery, such as prejudgment interest and attorneys' fees, in post-judgment briefing." It's still listed in the Conclusion section, but I think that's an oversight.

  • New cases cited (Donovan v. Bierwirth; Confederated Tribes of Warm Springs Reservation of Or. v. United States; New England Mut. Life Ins. Co. v. Anderson; United States of America v. Zelonky; Wootton Land & Fuel Co. v. Ownbey), and some dropped (Cassinos v. Union Oil Co. of Cal.; Bullis v. Security Pac. Nat'l Bank; Irwin v. Mascott; Nordahl v. Dep't of Real Estate; Stan Lee Trading, Inc. v. Holtz) and two that are neither but which Novell has chosen to attach as exhibits (In re Unisys Corporation Retiree Medical Benefits Litigation, which is Exhibit A; Evolution Inc. v. Prime Rate Premium Finance Corporation, Inc., which is Exhibit B). Most of the cases are presented to prove that it is SCO that has the burden of showing what it owes Novell, not the other way around, and that any uncertainties should be resolved in Novell's favor. You can see that most clearly in footnote 3.

  • Statutes no longer referenced are Cal. Civ. Code Sections 3287, 3288, and 3336.

  • New evidence rules are cited, Fed. R. Evid. 801, 802, again because Novell sees now from the briefs that apparently "SCO will not offer any testimony from an actual SCOsource licensee and will not offer any expert analysis of the value of UnixWare rights supposedly contained in SCOsource licenses."

  • This sentence removed: "Novell acknowledges there is ambiguity in this picture." Instead, it expands its argument that any uncertainties in the picture are created by SCO.

  • Novell references its summary judgment motion on its 4th claim, filed after the original trial brief, but says in the alternative, it is prepared to try the claim.

  • Where the original said SCOsource "was" such and so, now it reads "is", I assume because Novell noticed that SCO's SCOsource page on its website is still there, still active.

The new section on SCO's inability to carry its burden to show it is entitled to keep the SCOsource money is intriguing because it gives a hint of what Novell thinks SCO's strategy will be at trial:

E. SCO Cannot Carry Its Burden to Show Entitlement to SCOsource Revenue.

Critically, SCO will not offer any testimony from an actual SCOsource licensee and will not offer any expert analysis of the value of UnixWare rights supposedly contained in SCOsource licenses. Instead, based on the briefing to date, it appears that SCO will, in large part, attempt to support its case through testimony purporting to show its licensees' "intent" in entering into a SCOsource license. This is classic hearsay, and inadmissable. Fed. R. Evid. 801, 802; New England Mut. Life Ins. Co. v. Anderson, 888 F.2d 646, 650 (10th Cir. 1989)(reporter's out-of-court statements properly excluded as hearsay where declarant "was unavailable for cross-examination, and the statements were offered to prove the truth of the matters asserted."). Moreover, the testimony that Sun was seeking rights to UnixWare proves nothing about the license that eventually issued. See United States of America v. Zelonky, 209 F. Supp. 305, 307 (D.C. Wis. 1962) (defendant's testimony about how parties orally characterized contract at time of signing "cannot be given any credence in this action because it is not only hearsay but also is an attempt to vary by parol evidence the terms of a clear, unambiguous, and complete contract").

Such a bar is especially appropriate here, where the issue is the apportionment of funds wrongfully retained by a fiduciary. It is fundamentally unfair to allow a fiduciary in such circumstances to apportion revenue based on the supposed statements or intent of third parties not present in court. As discussed above in Section II.A, a fiduciary must meet a high standard of accountability and transparency as to how those funds were managed:

[The duty to account] is not fulfilled... by a general denial that any of the principal's money was taken for the personal use of the trustee. Such statements are but the conclusion of the witness, and afford no reasonable opportunity to the principal to test the fact or the propriety of the expenditures, and give the court no basis for determining from the facts of each transaction whether the trustee has faithfully performed his duty.

Wooltton Land, 265 F. at 99-100. SCO seeks to buttress a "general denial" that the SCOsource licenses primarily conveyed rights to SVRX with third parties' out-of-court settlements, the reliability of which cannot be ascertained. This tactic cannot help SCO meet its burden of proof on accounting. If anything, it demonstrates how little proof SCO has.

There are two redactions in this document of material visible in the original. The first, on page 15, relates to the Microsoft and Sun SCOsource licenses, and in the original it stated the "licenses convey broad rights to use, distribute, sublicense, etc. SVRX in both binary and source form, and contain no mention of CPU limitations." That is now redacted. And the following was in the original trial brief but is also redacted in the Amended Trial Brief: "Sun's 2003 SCOsource license explicitly acknowledges that it is intended to 'amend and restate' the 1994 buy-out agreement. (Order at 94.) By definition, Sun's SCOsource license therefore 'concerns' a buy-out, and SCO was required to follow the additional restrictions imposed by Amendment No. 2 on transactions that concern buy-outs." That's on page 16 of the Amended Trial Brief; 15 in the original.

Because both redactions concern already public information, never redacted in the original even after the fact, so far as I am aware, I see no reason in this case to pretend we didn't read it in September, although I've made the text here correspond to the PDF, showing the materials as redacted. It is, of course, possible that the Amended Trial Brief's redacted sections include further materials.

What's still on deck for the trial then? Novell lists the following:

The principal questions that remain for trial are:
  • What portion of the revenue from the Sun and Microsoft SCOsource licenses has SCO wrongly retained?

  • Are SCO's other SCOsource licenses SVRX Licenses and, if so, what portion of the revenue from those SCOsource licenses has SCO wrongly retained?

  • Did SCO have the authority to enter into the SCOsource licenses, including those with Sun and Microsoft?

And here is Novell's Amended Trial Brief as text:

******************************

MORRISON & FOERSTER LLP
Michael A. Jacobs, pro hac vice
Eric M. Acker, pro hac vice
Kenneth W. Brakebill, pro hac vice
Marc J. Pernick, pro hac vice
David E. Melaugh, pro hac vice
[address]
[phone]
[fax]

ANDERSON & KARRENBERG
Thomas R. Karrenberg, #3726
Heather M. Sneddon, #9520
[address]
[phone]
[fax]

Attorneys for Defendant and Counterclaim-Plaintiff Novell, Inc.

_______________________________

IN THE UNITED STATES DISTRICT COURT
DISTRICT OF UTAH, CENTRAL DIVISION

THE SCO GROUP, INC., a Delaware
corporation,

Plaintiff and Counterclaim-
Defendant,

v.

NOVELL, INC., a Delaware corporation,

Defendant and Counterclaim-
Plaintiff.
NOVELL'S AMENDED TRIAL BRIEF

(REDACTED pursuant to the August 2,
2006 Stipulated Protective Order)

Case No. 2:04CV00139

Judge Dale A. Kimball

TABLE OF CONTENTS

Page

TABLE OF AUTHORITIES....................................................................................................iii

INTRODUCTION...................................................................................................................1

CLAIMS AT ISSUE................................................................................................................2

A. Fourth Claim: Declaratory Relief.............................................................................2

B. Sixth, Seventh, and Eighth Claims: Unjust Enrichment,
Breach of Fiduciary Duty, Conversion.....................................................................3

C. Claims Not Set for Trial.............................................................................................3

ARGUMENT.................................................................................................4

I. SCOSOURCE IS A CAMPAIGN TO LICENSE SVRX. .................................................4

II. NOVELL IS ENTITLED TO THE SCOSOURCE LICENSING
REVENUE. .....................................................................................................4

A. Any Doubt or Ambiguity as to Entitlement to SCOsource
Revenue Must Be Resolved in Novell's Favor. .......................................................5

B. Novell Is Entitled to the Microsoft SCOsource Revenue. ......................................8

1. Novell Is Entitled to the Entirety of the [redacted]
Section 2 Revenue.....................8

2. Novell Does Not Seek the Section 3 Revenue.................9

3. Novell Is Entitled to the [redacted] Section 4 Revenue...........10

C. Novell Is Entitled to the Sun SCOsource Revenue......................................................10

D. Novell Is Entitled to the Other SCOsource Revenue.................................................11

E. SCO Cannot Carry Its Burden to Show Entitlement to
SCOSource Revenue....................13

F. SCO Is Not Entitled to Keep 5% of the SVRX License
Revenue........................................................................................14

III. SCO WAS WITHOUT AUTHORITY TO ENTER INTO THE
SCOSOURCE LICENSES. ...........................................................................14

IV. SCO'S AFFIRMATIVE DEFENSES HAVE NO MERIT. ...................................................16

i

A. Novell Is Not Estopped from Pursuing Its Fiduciary Duty
Claims Against SCO. ...........................................................................16

B. Novell Has Acted with "Clean Hands." ..................................................................18

CONCLUSION..............................................................19

ii


Roth v. Sawyer-Cleator Lumber Co.,
61 F.3d 599 (8th Cir. 1995)

TABLE OF AUTHORITIES

CASES

Belling v. Croter,
57 Cal. App. 2d 296 (1943)

19

Confederated Tribes of the Warm Springs Reservation of Or. v. United States,
248 F. 3d 1365 (Fed, Cur, 2001)

7

Donovan v. Bierwirth,
754 F. 2d 1049 (2d Cir. 1985)

7

Evolution, Inc. v. Prime Rate Premium Fin. Corp.,
No. 03-2315-KHV, 2004 U.S. Dist. LEXIS 25017 (D. Kan. Aug. 13, 2004)

9

Feduniak v. California Coastal Comm'n,
148 Cal. App. 4th 1346 (2007)

18

Hobbs v. Bateman Eichler, Hill Richards, Inc.,
164 Cal. App. 3d 174 (1985)

18

Kennard v. Glick,
183 Cal. App. 2d 246 (1960)

7

Kim v. Fujikawa,
871 F.2d 1427 (9th Cir. 1989)

7

Leigh v. Engle,
727 F.2d 113 (7th Cir. 1984)

7

Lentz v. McMahon,
49 Cal. 3d 393 (1989)

17

New England Mut. Life Ins. Co. v. Anderson,
888 F2d 646 (10th Cir. 1989)

13

Reynolds v. Roll,
122 Cal. App. 2d 826 (1954)

19

Rosenfeld, Meyer & Susman v. Cohen,
191 Cal. App. 3d 1035 (1987)

5-6

Rosenfeld v. Zimmer,
116 Cal. App. 2d 719 (1953)

19

7

Sheldon v. Metro-Goldwyn Pictures, Corp.,
106 F.2d 45 (2d Cir. 1939)

5

iii

In re Unisys Corp. Retiree Med. Benefits Litig.,
MDL NO. 969,2000 U.S. Dist. LEXIS 22347 (E.D. Pa. Apr. 25, 2000)

7

United States of America v. Zelonky,
209 F. Supp. 305 (D.C. Wis. 1962)

13

Watson v. Poore,
18 Cal. 2d 302 (1941)

19

Wootton Land & Fuel Co. v. Ownbey,
265 F. 91 (8th Cir. 1920)

7, 14

STATUTES

Cal. Civ. Code

§3517

3

§3288

13

Cal. Evid. Code

§623

17

Fed. R. Evid.

801, 802

13

iv

INTRODUCTION

This Court has held that any contract "relating to" the SVRX releases listed in the APA is an SVRX License, that the Sun and Microsoft SCOsource licenses are SVRX Licenses, and that SCO breached its fiduciary duties by failing to disclose those licenses and by failing to remit appropriate revenue from those licenses. The principal questions that remain for trial are:

  • What portion of the revenue from the Sun and Microsoft SCOsource licenses has SCO wrongly retained?

  • Are SCO's other SCOsource licenses SVRX Licenses and, if so, what portion of the revenue from those SCOsource licenses has SCO wrongly retained?

  • Did SCO have the authority to enter into the SCOsource licenses, including those with Sun and Microsoft?1

As the Court may have surmised from the motion in limine briefing, neither Novell nor SCO intends to come into court and argue, e.g., "The evidence definitively establishes Novell is entitled to precisely 98% of this license's revenue, 88% from this license, etc." Instead, SCO intends to argue that it is entitled to most, if not all, of the SCOsource licensing revenue, and Novell intends to argue the opposite. Novell believes the evidence presented at trial will paint Novell's position as considerably more credible.

The evidence will show that:

  • SCO approached Novell before beginning the SCOsource licensing campaign and asked Novell to join in that effort;

  • Novell refused to join the SCOsource campaign but SCO went ahead anyway;

  • The SCOsource campaign was based entirely on claims that Linux infringed SVRX copyrights;

1

  • SCO has never claimed that any party infringed SCO's UnixWare rights;

  • The focus of the specific SCOsource licenses that SCO executed is SVRX rights, not UnixWare rights; and

  • SCO never remitted to Novell any portion of the SCOsource revenue -- on the contrary, in violation of its fiduciary duties, SCO consistently refused to disclose the SCOsource contracts.

The law is clear that as Novell's fiduciary and as the party at fault for introducing any apportionment uncertainty into the SCOsource licenses, SCO must bear the burden of apportionment, and any doubts as to entitlement to particular licensing revenue must be decided against SCO.

In the face of such evidence, SCO persists in arguing that SVRX played only an incidental role in SCOsource and that it was therefore authorized to enter into the SCOsource licenses, notwithstanding the APA's general prohibition against SCO entering into new SVRX Licenses. Because the evidence will demonstrate that SVRX was at the heart of SCOsource, it cannot be that SVRX played only an "incidental" role in SCOsource licenses. Novell is therefore entitled to a declaration that SCO was without authority to enter into the SCOsource licenses.

CLAIMS AT ISSUE

A. Fourth Claim: Declaratory Relief

Novell has a motion for summary judgment pending on this claim. As described in the accompanying briefing, Novell believes this claim can be decided as a matter of law. (See Memo. in Support of Novell's Motion for Summary Judgment on Its Fourth Claim for Relief, filed December 21, 2007, PACER No. 482.) Pursuant to the Court's January 15, 2008 Order (PACER No. 485), Novell's motion is set of hearing on April 30. Novell is therefore also prepared to try this claim before the Court.

2

At trial, Novell will seek a declaration that SCO had no authority to enter into the Sun, Microsoft, and other SCOsource licenses. The Court has already held that the Sun and Microsoft SCOsource licenses are SVRX Licenses. At trial, Novell will prove that the other SCOsource licenses are also SVRX Licenses. Novell will then prove that none of the exceptions to the APA's prohibition against SCO entering into or modifying SVRX Licenses apply -- i.e., that Novell did not consent, that these licenses were not merely "incidental" to SCO's right to enter into UnixWare licenses, and that the licenses are not "additional CPU" licenses.

In addition, Novell will demonstrate it is entitled to a declaration that SCO had no authority to enter into the Sun SCOsource license because that agreement "concerned" a buy-out and SCO did not seek Novell's approval before entering into the Sun SCOsource license.

B. Sixth, Seventh, and Eighth Claims: Unjust Enrichment, Breach of Fiduciary Duty, Conversion

The Court has resolved any question as to SCO's liability for unjust enrichment, breach of fiduciary duty, and conversion as to the Sun and Microsoft SCOsource licenses. (Memorandum Decision and Order, Docket No. 377 ("Order"), at 97 ("SCO's conduct also amounts to a breach of fiduciary duty, conversion, unjust enrichment, and breach of express contract").) As to the Sixth, Seventh, and Eighth Claims, the only issue left for trial on the Sun and Microsoft SCOsource licenses is therefore the proper apportionment of the license revenue. The trial will also address whether SCO's remaining SCOsource agreements licensed SVRX and, if so, the amount of revenue that should be apportioned to Novell from those agreements. As discussed below, Novell need only prove up the total amount of revenue SCO received from the SCOsource licenses, and the burden then shifts to SCO to prove what amount is not Novell's. The evidence will show that the majority of the SCOsource revenue is in fact SVRX Royalties.

C. Claims Not Set for Trial

Pursuant to agreement or Court order, Novell's First, Second, Third, Fifth, and Ninth Claims are not set for trial. Novell will also not seek punitive damages.

3

ARGUMENT

I. SCOSOURCE IS A CAMPAIGN TO LICENSE SVRX.

SCOsource is a campaign to extract licensing revenue based on SCO's claim that UNIX System V code was in Linux. (Order at 29 ("SCOsource ... was an effort to obtain license fees from Linux users based on claims to Unix System V intellectual property.").) SCO has recently suggested that, in describing the focus of SCOsource, SCO's use of the term "UNIX System V" is broad enough to encompass UnixWare, because, technically UnixWare is derived from the UNIX System V code base. The origins of UnixWare are not important. Given that SCOsource is a licensing campaign based on claims of copyright infringement, to get at the heart of what is licensed one need only examine what code SCO alleged infringed. After years of litigation, thousands of hours of investigation, and millions of dollars in expert fees, SCO has only identified UNIX System V release 4 code as infringing -- SCO has never identified a single line of post-APA code in Linux.2

II. NOVELL IS ENTITLED TO THE SCOSOURCE LICENSING REVENUE.

The evidence presented at trial will show that the bulk of the money SCO collected in its SCOsource campaign was in fact SVRX Royalties and that Novell is entitled to restitution of this money.

4

A. Any Doubt or Ambiguity as to Entitlement to SCOsource Revenue Must Be Resolved in Novell's Favor.

As the plaintiff, Novell bears the burden to make out its prima facie case -- to show that SCO entered into SVRX Licenses, that SCO received SVRX Royalties, and that SCO did not remit those SVRX Royalties. The evidence presented at trial will establish such a case. The law is clear, however, that where a fiduciary commingles its own funds with those of its agent, it is the fiduciary's obligation to untangle the funds. Novell need only prove up the total amount of revenue SCO received, and the burden then shifts to SCO to show what amount is not Novell's.

Any other result would be manifestly unfair. Novell is not the author of the SCOsource licenses -- instead, SCO did its best to keep the terms of those licenses secret from Novell. If it is difficult to separate out what is SCO's from what is Novell's in those licenses, that is SCO's fault alone. To place the burden of doubts on Novell would reward SCO for its breach of fiduciary duty and encourage fiduciaries to convert agents' funds in ways that make apportionment difficult. One of the primary benefits of the APA's requirement for Novell's prior approval of SVRX Licenses is that it allows the parties to work out a fair apportionment of licensing revenue ahead of time and structure licenses to make clear each party's rights.

Faced with similar questions in the context of a copyright infringement accounting, Judge Learned Hand held:

[T]he defendants must be content to accept much of the embarrassment resulting from mingling the plaintiff's property with their own. We will not accept the expert's testimony at its face value; we must make an award which by no possibility shall be too small. It is not our best guess that must prevail, but a figure which will favor the plaintiffs in every reasonable chance of error.
Sheldon v. Metro-Goldwyn Pictures, Corp., 106 F.2d45, 51 (2d Cir. 1939). Similarly, Rosenfeld, Meyer & Susman v. Cohen, 191 Cal. App. 3d 1035 (1987), involved the dissolution of a law firm. The court held that, in breach of their fiduciary duties, one set of partners (the "RMS" partners) withheld partnership revenue from a second set (the "C&R" partners). Separation of the monies involved was complicated by the fact that some revenue stemmed from post-

5

dissolution work (to which, like SCO, only the RMS partners were entitled) and predissolution work (to which, like Novell, the C&R partners were entitled). Given the fiduciary relationships involved, the trial court placed the burden of apportionment on the RMS partners, with doubts decided against them. The appellate court affirmed:
The position of RMS was not unlike that of other trustees who fail to keep proper records of the dates and amounts of receipts and expenses; such fiduciaries have the burden of establishing that data and, upon their failure to do so, a computation may be made on the basis of gross receipts, even though that approach is unfavorable to them.

. . .

Surely, where a fiduciary has a legal duty to allocate receipts between those in which its beneficiary has some interest and those in which the beneficiary has none, and is fully and singularly capable of making that allocation but fails to do so, a court is justified in calling upon the fiduciary to bear the burden of differentiation at trial ....

Except for a few accounts, for which RMS did prove that percentage fee receipts were the product of post dissolution work, RMS failed to bear its burden at trial. As a result, the trial court correctly used the balance of the percentage fee income as the base for allocating the partners' shares.

Id. at 1051-52. This shift of the ordinary burden of proof allocation reflects a bedrock principle of the law of fiduciary relationships:
The rules of law that were applicable in the taking of the accounting may be briefly stated:

Where the defendant is an accounting party, and stands as one occupying a fiduciary relation toward the plaintiff, because of money or property intrusted to him, the burden is upon him to show that he has performed his trust and the manner of its performance. He owes this duty because of the confidential relation he bears to his principal, and because he is presumed to know how he has performed his duty. He must therefore prove any allowances or credits that he may claim to have made on behalf of his principal....

It follows as a corollary to these principles that the duty to account is not fulfilled by a mere general statement that the money was expended for the principal's benefit or business, or by a general

6

denial that any of the principal's money was taken for the personal use of the trustee. SUch statements are but the conclusions of the witness, and afford no reasonable opportunity to the principal to test the fact or the propriety of the expenditures, and give the court no basis for determining from the facts of each transaction whether the trustee has faithfully performed his duty.

Wootton Land & Fuel Co. v. Ownbey, 265 F. 91, 99-100 (8th Cir. 1920)(internal citations to various treatises omitted).3

SCO has attempted to distinguish these cases by inventing a distinction between uncertainty caused by the mingling of revenue from multiple sources (e.g., the new and old business in RMS) and uncertainty caused by the mingling of revenue within one source (e.g., the Microsoft SCOsource license). (SCO's Reply Memo. in Further Support of SCO's Motion In Limine Regarding Apportionment of 2003 Microsoft and Sun Agreements, filed September 4, 2007, PACER No. 449, at 3.) Nothing in these cases supports such a distinction, however, and

7

SCO has cited no cases of its own in support. It would be surprising if a fiduciary could force its principal to pay the price for the uncertainty caused by its own wrongdoing by simply commingling multiple revenue streams in one agreement.

B. Novell Is Entitled to the Microsoft SCOsource Revenue.

SCO has consistently described the license with Microsoft as part of its SCOsource campaign, and has never classified any portion of the revenue it collected from Microsoft as "UnixWare revenue" in its SEC filings. (NOV-EX-304.) Microsoft paid SCO [REDACTED ] for its SCOsource license, as follows:

REDACTED

(NOV-EX-189.) Novell is entitled to the revenue from Sections 2 and 4. Though Novell believes a case can be made that it is also entitled to a portion of the Section 3 revenue, for purposes of this trial Novell will not seek such revenue.

1. Novell is Entitled to the Entirety of the [redacted] Section 2 Revenue.

REDACTED

8

REDACTED

2. Novell Does Not Seek the Section 3 Revenue.

REDACTED

9

REDACTED

3. Novell is Entitled to the [redacted] Section 4 Revenue.

REDACTED

C. Novell Is Entitled to the Sun SCOsource Revenue.

REDACTED

10

(NOV-EX-327.) Darl McBride, SCO's CEO, was asked about this aspect of Sun's SCOsource license, and confirmed that SCO believes the license conveyed the right to Sun to open source Solaris. (NOV-EX-327, -341.) Sun's CEO, Scott McNealy, describes the license in the same way:
There were hundreds of encumbrances to open sourcing Solaris. Some of them we had to buy out, others we had to eliminate. We had to pay SCO more money so we could open the code -- I couldn't say anything about that at the time, but now I can tell you that we paid them that license fee to expand our rights to the code," McNealy said, referring to the February 2003 expanded Unix SVR4 license rights purchase from the SCO Group.

REDACTED

D. Novell Is Entitled to the Other SCOsource Revenue.

As noted above, SCO sent letters to thousands of Linux users threatening suit over the SVRX code supposedly in Linux. [REDACTED] such users took a SCOsource license, each under similar terms. These licenses grant, with certain limitations, the "right and license to use ... SCO IP." (NOV-EX-346.) The definition of "SCO IP" makes clear that these licenses convey SVRX rights:

"SCO IP" means the SCO UNIX®-based Code alleged by SCO to be included, embodied, or otherwise utilized in the Operating System.

. . .

11

"UNIX-based Code" means any Code or Method that: (i) in its literal or non-literal expression, structure, format, use, functionality or adaptation (ii) is based on, developed in, derived from or is similar to (iii) any Code contained in or Method devised or developed in (iv) UNIX System V or UnixWare®, or (v) any modification or derivative work based on or licensed under UNIX System V or UnixWare.
(NOV-EX-346 (emphasis added).)

In total, SCO entered into the following additional SCOsource licenses:

REDACTED

(NOV-EX-365, -391, -411.)

12

As SCO itself admits "[t]he central feature of the other SCOsource agreements is the covenant not to sue and the waiver of claims by SCO for the companies' internal Linux usage." (SCO's Memo. in Opp. to Novell's Motion In Limine to Preclude SCO from Contesting Licenses Conveying SVRX Rights Are "SVRX Licenses," Docket No. 421, at 3.) Because SCO has never contended UnixWare is in Linux, that "covenant not to sue" and "waiver of claims" must concern only SVRX. Novell is therefore entitled to the entirety of this SCOsource revenue.

E. SCO Cannot Carry Its Burden to Show Entitlement to SCOsource Revenue.

Critically, SCO will not offer any testimony from an actual SCOsource licensee and will not offer any expert analysis of the value of UnixWare rights supposedly contained in SCOsource licenses. Instead, based on the briefing to date, it appears that SCO will, in large part, attempt to support its case through testimony purporting to show its licensees' "intent" in entering into a SCOsource license. This is classic hearsay, and inadmissable. Fed. R. Evid. 801, 802; New England Mut. Life Ins. Co. v. Anderson, 888 F.2d 646, 650 (10th Cir. 1989)(reporter's out-of-court statements properly excluded as hearsay where declarant "was unavailable for cross-examination, and the statements were offered to prove the truth of the matters asserted."). Moreover, the testimony that Sun was seeking rights to UnixWare proves nothing about the license that eventually issued. See United States of America v. Zelonky, 209 F. Supp. 305, 307 (D.C. Wis. 1962) (defendant's testimony about how parties orally characterized contract at time of signing "cannot be given any credence in this action because it is not only hearsay but also is an attempt to vary by parol evidence the terms of a clear, unambiguous, and complete contract").

Such a bar is especially appropriate here, where the issue is the apportionment of funds wrongfully retained by a fiduciary. It is fundamentally unfair to allow a fiduciary in such circumstances to apportion revenue based on the supposed statements or intent of third parties

13

not present in court. As discussed above in Section II.A, a fiduciary must meet a high standard of accountability and transparency as to how those funds were managed:
[The duty to account] is not fulfilled... by a general denial that any of the principal's money was taken for the personal use of the trustee. Such statements are but the conclusion of the witness, and afford no reasonable opportunity to the principal to test the fact or the propriety of the expenditures, and give the court no basis for determining from the facts of each transaction whether the trustee has faithfully performed his duty.

Wooltton Land, 265 F. at 99-100. SCO seeks to buttress a "general denial" that the SCOsource licenses primarily conveyed rights to SVRX with third parties' out-of-court settlements, the reliability of which cannot be ascertained. This tactic cannot help SCO meet its burden of proof on accounting. If anything, it demonstrates how little proof SCO has.

F. SCO Is Not Entitled to Keep 5% of the SVRX License Revenue.

As the Court is aware, under the APA, SCO undertook a fiduciary duty to collect and remit 100% of the SVRX Royalties. "In consideration of SCO's exercise of its fiduciary duties, SCO is ordinarily entitled to "an administrative fee equal to 5% of such SVRX Royalties." (NOV-EX-l (APA) at §4.16(a).) Here, the Court has found that, as a matter of law, SCO breached its fiduciary duties and converted revenue meant for Novell. (Order at 97.) Given that breach, SCO is not entitled to any percentage of the SVRX Royalties, and the Court should therefore make no 5% deduction from any restitution granted Novell.4

III. SCO WAS WITHOUT AUTHORITY TO ENTER INTO THE SCOSOURCE
LICENSES.

In addition to the return of SCOsource revenue wrongfully withheld, Novell seeks a declaration that SCO was without authority to enter into the SCOsource licenses. Novell's entitlement to such a remedy is straightforward. This Court has already held that the Microsoft

14

and Sun SCOsource licenses are SVRX Licenses, and has barred SCO from contesting that ruling at trial. (Order at 95; September 9, 2007 Order ("MIL Order"), PACER No. 453, at 16-17.) The evidence will show that SCO's other SCOsource licenses also conveyed SVRX rights and that they are therefore SVRX Licenses.

SCO is generally barred from modifying existing SVRX Licenses and from entering into new SVRX Licenses. (Order at 92.) As amended, the APA permits only three exceptions:

SCO may enter into SVRX Licenses with Novell's written permission. Novell never consented to the SCOsource licenses, and SCO has not suggested otherwise. (Order at 41.)

SCO may enter into SVRX Licenses "incidentally involved through [SCO's] rights to sell and license" UnixWare. The evidence cited and discussed above amply demonstrates that SVRX played more than an "incidental" role in the SCOsource licenses -- it was the very heart of SCOsource.

And SCO may enter into SVRX Licenses "to allow a licensee under a particular SVRX License to use the source code of the relevant SVRX product(s) on additional CPU's or to receive an additional distribution, from [SCO], of such source code." The SCOsource licenses are not such "additional CPU" licenses. In the case of Sun and Microsoft, the SCOsource [redacted] The other SCOsource licenses permit the licensee to use SVRX in Linux and, again, contain no CPU limitations. With no applicable exception, the APA's general bar applies and SCO was therefore without authority to enter into the SCOsource licenses.

SCO was without authority to enter into the Sun SCOsource license for an additional, independent reason. Before entering into "any potential transaction with an SVRX licensee which concerns a buy-out of any such licensee's royalty obligations," SCO must notify Novell in writing and obtain Novell's consent. (NOV-EX-40). There is no dispute that Sun's 1994

15

agreement with Novell was a "buy-out," as that term is used in Amendment No. 2. [redacted] The evidence will establish that SCO did not inform Novell in writing of its intention to enter into the Sun SCOsource agreement and did not obtain Novell's consent to that agreement. For this additional reason, SCO was without authority to enter into the Sun SCOsource agreement.

IV. SCO'S AFFIRMATIVE DEFENSES HAVE NO MERIT.

During meet and confer on the pretrial order, SCO articulated two affirmative defenses it intends to raise at trial: estoppel and unclean hands. Neither has any application here.

As a preliminary matter, both defenses would appear to concern Novell's entitlement to equitable relief, not the precise amount of that relief. As that entitlement has already been determined as a matter of law, it is unclear what application these defenses could have now. Put otherwise, if SCO wanted to raise these defenses, it should have done so in the motion for summary judgment briefing.

A. Novell Is Not Estopped from Pursuing Its Fiduciary Duty Claims Against SCO.

SCO's draft pretrial order suggested that SCO will assert that Novell is estopped from seeking the SVRX Royalties withheld by SCO. SCO has, in the past, asserted that Novell's purported failure to ask for SVRX Royalties from licenses that also license UnixWare is evidence that Novell is not entitled to such revenue. SCO made that argument in an effort to graft "existing at the time of the APA" into the definition of "SVRX License," which the Court rejected as a matter of law. (Order at 90-93.) SCO bears an even greater burden to show that the same supposed facts make out a case for estoppel -- a burden that SCO cannot hope to carry.

16

Estoppel arises out of the rule that "[w]henever a party has, by his own statement or conduct, intentionally and deliberately led another to believe a particular thing true and to act upon such belief, he is not, in any litigation arising out of such statement or conduct, permitted to contradict it." Cal. Evid. Code § 623. To make out estoppel, "four elements must be present ... (1) the party to be estopped must be apprised of the facts; (2) he must intend that his conduct shall be acted upon, or must so act that the party asserting the estoppel had a right to believe it was so intended; (3) the other party must be ignorant of the true state of facts; and (4) he must rely upon the conduct to his injury." Lentz v. McMahon, 49 Cal. 3d 393,399 (1989). SCO would therefore have to show that Novell knew whether and to what extent SCO collected but did not remit SVRX Royalties, that Novell failed to seek such Royalties and intended for that failure to be taken by SCO as indication it could keep the money, and that SCO relied on Novell to its injury.

It is obviously impossible for SCO to make out those elements as to the SCOsource revenue -- as soon as Novell found out about that, it sent repeated letters to SCO demanding Novell's proper share. (NOV-EX-220, -267, -280, -293, -297, -303, -317.) What SCO must intend to argue, instead, is that Novell's purported conduct concerning earlier licenses, not at issue in this trial, waived Novell's right to insist on apportionment of the SCOsource revenue. If that is not the very argument this Court has already rejected as a matter of law, it certainly bears a striking resemblance.

Assuming the law of the case does not bar estoppel here, though, SCO still cannot succeed. It cannot point to any affirmative conduct by Novell waiving its right to SVRX Royalties. SCO is therefore confined to arguing that Novell's silence when supposedly presented with evidence that SCO withheld SVRX Royalties estops Novell now. "Estoppel by silence" is especially difficult to show. Courts typically require a duty to speak before imparting preclusive effect to silence. See, e.g., Feduniak v. California Coastal Comm'n, 148 Cal. App. 4th

17

1346, 1362 (2007) ("It is settled that when the party to be estopped does not say or do anything, its silence and inaction may support estoppel only if it had a duty to speak or act under the particular circumstances."). That is especially true in fiduciary relationships, where the presumption is that the principal need not investigate the activities of its agent and can instead rely on the agent to fulfill its duties faithfully. Hobbs v. Bateman Eichler, Hill Richards, Inc., 164 Cal. App. 3d 174, 201-202 (1985) ("Where there is a fiduciary relationship, the usual duty of diligence to discover facts does not exist."). As Novell has no "duty to speak" here, it cannot be estopped by its supposed silence.

Even if SCO surmounted all these obstacles, the facts simply do not show Novell silence in the face of knowledge that SCO retained SVRX Royalties from mixed licenses. SCO has presented no evidence that Novell was aware of even one such circumstance. The record instead shows that Novell's auditors reviewed royalty reports prepared by SCO, royalty reports from third-party licensees, and other payment and financial records, and not the terms of the actual SCO UnixWare licenses. (NOV-EX-84 ("[t]he audit included a review of royalty reports, third party royalty reports, summary reports, Novell cash deposit reports, cash reconciliations, accounts receivable reports, customer lists, other financial records and SCO's customer audits").) Novell is not aware of any evidence that Novell saw any of SCO's UnixWare licenses that conveyed SVRX rights. SCO's briefing is to the same effect.5

B. Novell Has Acted with "Clean Hands."

SCO's draft pretrial order also suggested that SCO intends to assert that the equitable remedies Novell seeks are barred under the doctrine of unclean hands. As partially codified in California Civil Code section 3517, this doctrine provides that "[n]o one can take advantage of

18

his own wrong." Aside from listing "unclean hands" in its Answer, SCO has never mentioned this defense and has therefore never articulated what conduct by Novell SCO claims bars the recovery of equitable remedies. If SCO had a meritorious unclean hands defense, it is surprising that SCO did not raise it in the motion for summary judgment briefing.

In any event, Novell has always acted with good faith toward SCO (see, e.g., Order at 65), and the cases actually granting such a defense make clear that no conduct by Novell rises to the level of unclean hands. See, e.g., Rosenfeld v. Zimmer, 116 Cal, App. 2d 719, 722 (1953) ("A court of equity will not assist a party to a fraudulent scheme to secure the objective of such plan."); Reynolds v. Roll, 122 Cal. App. 2d 826,836 (1954) ("courts will not lend assistance to persons whose claim for relief rests on an illegal transaction" (internal quotation marks and citation omitted)). Even where such conduct is shown, it must be part of the same transaction at issue, and the nature of the plaintiff's conduct must be worse than that of the defendant. See, e.g., Watson v. Poore, 18 Cal. 2d 302, 313 (1941) ("[I]mproper conduct not necessarily connected with the transaction particularly involved ... is not a reason for denying equitable relief on the ground of unclean hands."); Belling v. Croter, 57 Cal, App. 2d 296, 304 (1943) (Unclean hands does not apply "if it be shown that [the plaintiff] is the one 'least at fault,' and that the party against whom relief is sought was guilty of wrongdoing in respect to the same matters and is 'most in fault. '”).

It is therefore clear that no affirmative defenses protect SCO's conduct here.

CONCLUSION

For the reasons stated above, Novell is entitled to:

  • Apportionment of the SCOsource revenue in an amount to be determined by the Court, without any 5% administrative fee deduction;

  • Prejudgment interest at 7%; and

19

  • A declaration that SCO exceeded its authority in entering into the SCOsource licenses.

Based on that recovery, Novell anticipates seeking additional relief in its post-trial briefing, such as a constructive trust. Consideration of such relief is not necessary at trial, which per the Court's direction will focus on the proper apportionment of the SCOsource revenue and on Novell's entitlement to declaratory relief.

DATED: April 23, 2008

ANDERSON & KARRENBERG

By: /s/ Heather M. Sneddon
Thomas R. Karrenberg
Heather M. Sneddon

- and -

MORRISON & FOERSTER LLP
Michael A. Jacobs, pro hac vice
Eric M. Acker, pro hac vice
Kenneth W. Brakebill, pro hac vice
Marc J. Pernick, pro hac vice
David E. Melaugh, pro hac vice

Attorneys for Defendant and
Counterclaim-Plaintiff Novell, Inc.


1 This Trial Brief replaces the brief Novell filed before SCO's bankruptcy, at Docket No. 470.

2 See, e.g., NOV-EX-427 (SCO opposition to IBM's motion for summary judgment on IBM's claim seeking declaration that it does not infringe any UNIX copyright, identifying only "SVr4" material as infringing, see esp. Appendix A at 92-93, ¶181, admitting that infringing material comes from SVr4 and previous releases), NOV-EX-429 (IBM submission noting "the only allegedly infringed copyrights are, under the Novell Decision, owned by Novell, not SCO"), NOV-EX-430 (SCO letter informing arbitration panel that proceeding with arbitration is "pointless" because all copyrights relevant to SUSE's purported infringement have been held owned by Novell); see also NOV-EX-192 (letter identifying "UNIX System V" infringing material as "distributed by AT&T" -- i.e., well before UnixWare), NOV-EX-193 (same), NOV-EX-194 (same), NOV-EX-195 (same), NOV-EX-346 (letter identifying only pre-APA code as infringing, see esp. Ex. 1), Id. (same, see esp. Ex. 2).

3 See also Confederated Tribes of the Warm Springs Reservation of Or. v. United States, 248 F.3d 1365, 1371 (Fed. Cir. 2001) ("The court was also wrong to refuse to award damages on the ground that any award would be speculative. It is a principle of long standing in trust law that once the beneficiary has shown a breach of the trustee's duty and a resulting loss, the risk of uncertainty as to the amount of the loss falls on the trustee."); Kim v. Fujikawa, 871 F.2d 1427, 1430-31 (9th Cir. 1989) ("In determining the amount that a breaching fiduciary must restore to the Funds as a result of a prohibited transaction, the court should resolve doubts in favor of the plaintiffs." (internal quotation and citation omitted)); Donovan v. Bierwirth, 754 F.2d 1049, 1056 (2d Cir. 1985) ("The burden of proving that the funds would have earned less than that amount is on the fiduciaries found to be in breach of their duty. Any doubt or ambiguity should be resolved against them. This is nothing more than the application of the principle that, once a breach of trust is established, uncertainties in fixing damages will be resolved against the wrongdoer."); Leigh v. Engle, 727 F.2d 113, 138-39 (7th Cir. 1984) ("[T]he burden is on the defendants who are found to have breached their fiduciary duties to show which profits are attributable to their own investments apart from their control of the Reliable Trust assets.... [W]hile the district court may be able to make only a rough approximation, it should resolve doubts in favor of the plaintiffs."); In re Unisys Corp. Retiree Med. Benefits Litig., MDL No. 969, 2000 U.S. Disst. LEXIS 22347, at *15 (E. D. Pa. Apr. 25, 2000) ("[O]nce a plaintiff has established a breach and resulting harm, the breaching fiduciary has the burden of resolving any uncertainty pertaining to the extent of that harm.") (Ex. A hereto); Kennard v. Glick, 183 Cal. App. 2d 246, 250-51 (1960) ("An agent who fails to keep an account raises thereby a suspicion of infidelity or neglect, creates a presumption against himself, and brings upon himself the burden of accounting to the utmost for all that has come into his hands; and in such case every doubt will be resolved against the agent, and in favor of the principal...."); Roth v. Sawyer-Cleator Lumber Co., 61 F.3d 599, 602 (8th Cir. 1995) ("To the extent that there are ambiguities in determining loss, we resolve them against the trustee in breach.").

4 Novell will address additional recovery, such as prejudgment interest and attorneys' fees, in post-judgment briefing.

5 SCO's Memorandum in Opposition to Novell's Motion for Partial Summary Judgment or Preliminary Injunction and in Support of SCO's Cross Motion for Summary Judgment or Partial Summary Judgment, Docket No. 183, at ¶ 60 (noting that Novell representatives received only reports of binary royalties from SVRX licenses).

20

CERTIFICATE OF SERVICE

I HEREBY CERTIFY that on this 23rd day of April, 2008, I caused a true and correct copy of NOVELL'S AMENDED TRIAL BRIEF [ REDACTED pursuant to the August 2, 2006 Stipulated Protective Order] to be served to the following:

Via CM/ECF:

Brent O. Hatch
Mark F. James
HATCH JAMES & DODGE, P.C.
[address]

Stuart H. Singer
William T. Dzurilla
Sashi Bach Boruchow
BOIES, SCHILLER & FLEXNER LLP
[address]

David Boies
Edward J. Normand
BOIES, SCHILLER & FLEXNER LLP
[address]

Devan V. Padmanabhan
John J. Brogan
DORSEY & WHITNEY, LLP
[address]

Via U.S. Mail, postage prepaid:

Stephen Neal Zack
BOIES, SCHILLER & FLEXNER LLP
[address]

/s/ Heather M. Sneddon


  


Parties File Sealed Trial Briefs; Novell's Redacted Amended Trial Brief, as text | 208 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Corrections Here
Authored by: entre on Thursday, April 24 2008 @ 03:37 AM EDT
As needed.

[ Reply to This | # ]

News Picks here
Authored by: grouch on Thursday, April 24 2008 @ 03:56 AM EDT
Commentary about articles in the News Picks here, please. It's helpful to include a link or at least the title of the article you're referencing.

Thanks!

---
-- grouch

"People aren't as dumb as Microsoft needs them to be."
--PJ, May 2007

[ Reply to This | # ]

Off Topic here
Authored by: grouch on Thursday, April 24 2008 @ 04:05 AM EDT
Please post off-topic commentary here. (Not to be confused with off-color). See instructions below the "Post a Comment" editing box.

Thank you!

---
-- grouch

"People aren't as dumb as Microsoft needs them to be."
--PJ, May 2007

[ Reply to This | # ]

Parties File Sealed Trial Briefs; Novell's Redacted Amended Trial Brief, as text
Authored by: Ian Al on Thursday, April 24 2008 @ 04:20 AM EDT
SCO seeks to buttress a "general denial" that the SCOsource licenses primarily conveyed rights to SVRX with third parties' out-of-court settlements, the reliability of which cannot be ascertained.
That is interesting because it seems to address a settlement by CA with the Canopy Group: Computer Associates' VP Says CA Did Not Exactly Buy a SCO License. That is interesting because the settlement was not with SCO and also because SCO insisted that it included SCOSource Linux Tax licences and CA refuted that. Both sides agree that it involved the purchase of several Unixware licences to enable support of CA's customers. If the customers were running Unixware 2, then that is Novell's money. There is no way that CA's customers could have got the merged product and still be in breach of contract.

Since SCO insisted it included Linux Tax licences (many times and in public) then that could only have been for SVRX. So, come on SCO. Tell us how much of the $40M settlement was for Unix SVRX and how much of it was for Linux SVRX?

The flapping noise you can hear is SCO's chickens coming home to peck them in the briefs.

---
Regards
Ian Al

When nothing else makes sense, use Linux.

[ Reply to This | # ]

Order of questions is interesting
Authored by: Anonymous on Thursday, April 24 2008 @ 05:12 AM EDT
The principal questions that remain for trial are:
  • What portion of the revenue from the Sun and Microsoft SCOsource licenses has SCO wrongly retained?
  • Are SCO's other SCOsource licenses SVRX Licenses and, if so, what portion of the revenue from those SCOsource licenses has SCO wrongly retained?
  • Did SCO have the authority to enter into the SCOsource licenses, including those with Sun and Microsoft?

I find the order in which Novell present the questions significant. It indirectly addresses SCO's recent arguments (and reflects some discussions which went on here) that, in asking for a statement that SCO had no authority to enter into them, Novell is not entitled to receive the money from the agreements.

Note that the question of SCO's authority is listed after the question of how much money it "wrongly retained". By this ordering, I believe Novell's lawyers are underlining to the Judge that the question of authority is not a predicate to any decision regarding apportionment.

It's another example of the difference between lawyers and programmers, I suppose. A programmer, IMHO, would have listed them in the natural order in which the questions arose i.e. were they even permitted to enter into the agreements, then how much was due. A "good" opposing lawyer could seize on that as indicating that the second part is dependent on the first. By this ordering, Novell forestalls that argument.

The devil is in the details.

----------------------
Nigel Whitley

[ Reply to This | # ]

Newly-redacted text may be redacted new text
Authored by: Doghouse on Thursday, April 24 2008 @ 06:26 AM EDT
On your "redactions in this document of material visible in the
original", PJ. It's an untested assumption that the redacted text is the
same as in the original.

[ Reply to This | # ]

Open sourcing of Solaris
Authored by: Anonymous on Thursday, April 24 2008 @ 06:36 AM EDT
The trial brief contains this statement:

"Darl McBride, SCO's CEO, was asked about this aspect of Sun's SCOsource
license, and confirmed that SCO believes the license conveyed the right to Sun
to open source Solaris. (NOV-EX-327, -341.)"

While not particularly relevant to Novell's claims, if this is correct it is
difficult to see that, even in the unlikely event that SCO were to prevail in
trial against IBM, they could have suffered any compensatable damages. Once the
code is in the open, it is in the open, and someone else improperly publishing
it in the open will not have caused any further loss.

[ Reply to This | # ]

Constructive trust?
Authored by: Anonymous on Thursday, April 24 2008 @ 08:13 AM EDT
In their conclusion, Novell states:
Based on that recovery, Novell anticipates seeking additional relief in its post-trial briefing, such as a constructive trust.
Judge Gross only allowed the Utah trial to be unstayed for the matters of SCOSource revenue apportionment and the declaration as to whether SCO had the right to enter into the SCOSource licenses, and he reserved the decsision on a constructive trust to be handled by the bankruptcy court. Why is Novell saying that they intent to ask for a constructive trust in its post-trial briefing in the Utah case? Could that come back to bite them?

[ Reply to This | # ]

Are we going to see a Chapter 7 filing on Monday?
Authored by: Anonymous on Thursday, April 24 2008 @ 08:43 AM EDT
This might have been in previous comments.
I've forgotten, do the SCOundrels need permission to file chapter 7 from the
bankruptcy judge?

[ Reply to This | # ]

SCO cannot expose MS and Sun to cross-examination
Authored by: Anonymous on Thursday, April 24 2008 @ 09:05 AM EDT
As should have been expected, SCO and BSF are viewing this trial as the hill
that they are about to die on, and by not offering any admissible testimony
about from MS and Sun about the intent, I can't see how they have any hope of
winning. But it's just about winning, now, it's about how they lose.

So one needs to ask -- why are they going to try to rely on inadmissible
hearsay, i.e., to try to get into evidence indirectly what SCO 'represents' that
SUN and MS intended?

Because if they actually put SUN and/or MS representatives on the stand, i.e.,
people with direct and admissible evidence about the understanding of SUN and MS
regarding the licenses, what will happen is -- no matter how those witnesses
tried to slant their testimony on direct -- those witnesses will be subjected to
a lengthy, excruciating, well-prepared and detailed cross-examination by
Novell's lawyers. And the real truth will HAVE to come out. And the witnesses
will cave. And the tunnel that SCO is already in will collapse.

So -- we're seeing a predictable, albeit pathetic attempt by BSF and SCO to try
a dodge to avoid the train wreck that they see coming right at them, a dodge
that tries to sidestep the most basic rule of trial evidence, namely, that
hearsay -- testimony from a witness about the intent of a non-witness -- is not
admissible as to the truth of the matter asserted.

Remember, they declared bankruptcy rather than confront this, the last time
around. And we're back...

LEXLAW

[ Reply to This | # ]

Obligatory hearsay Comment
Authored by: red floyd on Thursday, April 24 2008 @ 10:34 AM EDT
Novell calls that hearsay, and so, once again, Novell must raise Ye Olde Rules of Evidence, specifically the hearsay and parol rules of evidence. Some things about SCO never change.
We've plenty of hearsay and conjecture. Those are kinds of evidence.

--Lionel Hutz, "The Simpsons"

---
I am not merely a "consumer" or a "taxpayer". I am a *CITIZEN* of the United States of America.

[ Reply to This | # ]

Either or?
Authored by: Hop on Thursday, April 24 2008 @ 11:01 AM EDT
Shouldn't this really be an "either or" argument? Either Novell is
owed royalties from the agreement or the agreement is invalid and the money paid
for the licenses is returned. If the money has to be returned, would Microsoft
and Sun then just be added to the list people SCO owes money to? It's not like
SCO could actually return the money at this point. It also looks like SCO would
be better off admitting that it made a mistake in selling licenses to Sun and
Microsoft. It doesn't hurt them much at this point... or does it?

I guess Novell could always ask to see everything related to the transactions to
determine what Sun and Microsoft had actually done with the licenses. The
by-product of that would be learning whether or not Sun and Microsoft had any
real plans to use those licenses, which I seriously doubt. And if they did
already do something with those licenses, they'd have to negotiate a new
contract with Novell or back out everything related to it.


“Oh what a tangled web we weave, When first we practice to deceive” - Sir Walter
Scott

[ Reply to This | # ]

What happens if SCo tries to sneak in a Sun or MS witness?
Authored by: Anonymous on Thursday, April 24 2008 @ 12:18 PM EDT
Could they suprise novell and call a witness from Sun or MS? If its possible, I
bet they would give it a try.

[ Reply to This | # ]

Filing under seal without court permission
Authored by: Anonymous on Thursday, April 24 2008 @ 02:44 PM EDT

Does SCO have permission to file their brief under seal?

From the Utah local rules:

No document may be designated by any party as Filed under Seal or Confidential unless:

  1. it is accompanied by a court order sealing the document;
  2. it is being filed in a case that the court has ordered sealed; or
  3. it contains material that is the subject of a protective order entered by the court.

Their filing should have been accompanied by a copy of or reference to a previous order from the court allowing sealing. But it wasn't.

There's a court order back at [102] which allows Novell to file certain documents under seal. And there was a stipulation in discovery [138] that certain materials could be marked "Confidential". But neither of those exceptions seems to apply here.

Novell properly cites the August 2, 2006 protective order in their filing, explicitly claimed confidentiality on limited items, and filed a "redacted" version simultaneously. SCO seems to have simply filed their brief and checked the "Sealed" box without citing court authority for that action, or even claiming that the brief contains confidential information.

[ Reply to This | # ]

UnixWare is a derivative work
Authored by: GLJason on Thursday, April 24 2008 @ 06:50 PM EDT

The court has ruled that SVRX copyrights belong to Novell. UnixWare is a derivative work of SVRX. The APA and Santa Cruz's original contract for OpenServer give SCO rights to distribute binary copies of UnixWare, but not to give rights to SVRX code.

The best analogy I can think of is this... Say Bart is an author who writes a book called "Epiphany". Stan licenses the rights to create a comic book based on the book and Darl licenses the rights to create a movie based on the book. In the mean time Bart produces his own short film based on his book. Bart gets tired of peddling his book to stores, and Darl is interested in some things that Bart did with his short film. Bart sells the rights to his short film to Darl and the business of marketing his book, but he keeps the copyrights and 100% of the royalties from his book (although he gives back 5% to Darl for collecting the money for him). Darl then goes on to combine his own film with Bart's short film and sell the result.

Now Darl has the rights to the short film and the film he produced himself, but the purchase agreement forbids Darl from any other licensing of the book except as it relates to those two films (unless approved by Bart). What we have here is Darl selling the book on Amazon.com and keeping all of the profits based on the fact that he has the right to license the movies. Darl is also suing Stan for his comic book royalties even though Stan licensed the comic book rights from Bart and the comic books are not based on the movies, but the original book. Obviously Bart has the rights to the proceeds from selling the book on Amazon.com, and he also has the right to prevent Amazon.com from selling his book any more because Darl had no right to do that in the first place. If Amazon gave Darl a huge up-front payment and they haven't sold enough books to cover the agreement, then it's Bart's choice whether to return some of that money to Amazon and prevent them from selling the book any more or to keep all the money and allow them to continue selling the book. Darl never had any legal interest in the money he unlawfully kept from Bart.

[ Reply to This | # ]

A bit OT regarding style
Authored by: Anonymous on Thursday, April 24 2008 @ 07:34 PM EDT
I notice that in a number of these briefs the lawyers make what I would regard
as flat conclusiary statements, such as "it is impossible for" where I
would have that that this would be a decision that the court would have to make.
In my IANAL opinion it would be better to use "in our opinion it is
impossible".

I wonder if this difference of style would keep the Judge from getting a little
narked at the apparent presumption of the lawyers of the courts functions? Is
this flat style common with lawyers making these sort of briefs?

I would have thought that lawyers would always attempt to keep the judge as
neutral as possible, if only to prevent any possibility of prejudicing the judge
against you. My very limited experience of judges is that they like to make the
decisions and not be told what the ruling is, when they have in fact not yet
made it.

I repeat, IANAL and am just curious.

[ Reply to This | # ]

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 )