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
AutoZone's 1st Request for Documents - as text
Sunday, October 17 2004 @ 03:24 PM EDT

Here is Autozone, Inc.'s First Requests For Production of Documents and Things To Plaintiff The SCO Group, Inc. ( beginning on page 73), as text. The document makes reference to their First Set of Interrogatories. Again, our thanks to Henrik Grouleff.

Some of you will remember that some time ago, I mentioned that really good lawyers are careful to craft good definitions in a legal document. This is a fine example of doing that. But why do you need a definition of "relate to" or "person" or "each"? You know what the words mean, right?

The answer is, yes, you know, but if the lawyer doesn't phrase the question just right, you could say to yourself, "Oh, he said 'each' and in my mind I thought that didn't include 'every', so I don't have to tell him about that key piece I know he needs to prove his case against me." As Supreme Court Justice Anthony Scalia once said, and I'm paraphrasing from memory here, if you could get the truth by just asking someone a question and getting an answer, we wouldn't need lawyers.

So in the adversarial system, and that's what the US has, each side's lawyers try, depending on what side they represent, to frame questions as broadly and as specifically as possible so you have to tell them the piece you'd rather not tell or, on the other side, to interpret all questions as narrowly as possible so as not to have to provide the opposition with all you actually know. It's the other side's job to formulate the question properly so you can't wriggle away. This isn't gaming the system. It is the system.

That alone should tell you that you need a lawyer when any legal conflict arises. Common sense isn't enough. Honesty isn't either. There is a complicated system, and you need help to make it work for you. When you read the definitions in this document, they almost sound silly to a nonlawyer, but then match them up with the list of items AutoZone is asking SCO to provide (for example, their use of "relate" in numbers 6-8 in the list of items to be provided), and I think you'll see what they are doing -- making sure the other side has no excuse to avoid providing all that they want to know.

Items 8 and 9 provide a clear example, too. Notice they request in 9, "All documents that reflect or regard correspondence or communications to or from AutoZone relating to Linux, and all notes and memoranda regarding or relating to the same." Obviously, AutoZone is aware of some correspondence between the parties. It has received some correspondence from SCO regarding Linux use, for example maybe the Dear Linux User letter or perhaps there have been many others, as well as some from AutoZone back to SCO. They know. But what they want isn't the letters. They have those. What they want is everything all the SCOfolk said to one another or to third parties about it, before, during and after.

Why bother to say all notes *and* memoranda when they've already covered everything by asking for all documents? Let's imagine a scenario. Suppose a SCO executive jotted down some notes at a meeting about who to sue, and AutoZone's name came up. Someone mentioned that they read on Groklaw that a Jim Greer had posted that he was in charge of the switch to Linux, and he didn't use the shared libraries. Everyone talks about whether to go forward with the scheme to sue AutoZone anyway. Someone mentions that no one will ever know that they read that, so let's go for it. Our hypothetical executive writes that down in his notes. SCO then sues AutoZone.

AutoZone would like to have those notes (remember, we're just imagining here). If they just ask for all memoranda, the imaginary note-taking executive could withhold his smoking gun notes, because technically, it isn't a memo, at least not in his mind, because there was no MEMO header and the fact that he Xeroxed ten copies of his notes for everyone doesn't, in his mind, morph it into a memo. This is a hypothetical example, just for illustrative purposes. I am not suggesting that happened, just showing why you need to spell out everything and your list of documents needs to include all memoranda, notes, post-its, doodles, etc., the details depending on the situation and what you are after. Contrast the simplicity of item 10, where there is no wriggle room to worry about. Of course, my favorite is number 6.

AutoZone does a masterful job of closing off potential excuses and loopholes. If you notice the Instructions section, they also put it in writing that these are only their requested items within the context of the current limited discovery framework. If it were to broaden later, they don't want their options cut off.

It may sound funny to you when I tell you that I enjoyed reading this document, definitions, instructions, and all, but I did, and it's one I'll save as a template for future use.

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

James J. Pisanelli
Nevada Bar No. 4027
Nicki L. Wilmer
Nevada Bar No. 6562
SCHRECK BRIGNONE
[address, phone]

Michael P. Kenny. Esq.
James A. Harvey, Esq.
David J. Stewart, Esq.
Christopher A. Riley, Esq.
Douglas L. Bridges, Esq.
ALSTON & BIRD LLP
[address, phone]

Attorneys for Defendant AutoZone, Inc.

UNITED STATES DISTRICT COURT
THE DISTRICT OF NEVADA


THE SCO GROUP, INC.,
a Delaware Corporation
Plaintiff,
v.

AUTOZONE, INC.,
a Nevada Corporation
Defendant.




Civil Action File No.


CV-S-04-0237-RCJ-LRL



DEFENDANT AUTOZONE, INC.'S FIRST REQUESTS FOR PRODUCTION
OF DOCUMENTS AND THINGS TO PLAINTIFF THE SCO GROUP, INC.

Pursuant to Rules 26 and 34 of the Federal Rules of Civil Procedure (hereinafter "FRCP"), Defendant AutoZone, Inc. ("AutoZone") hereby serves these requests for the production of documents and things upon Plaintiff The SCO Group, Inc. ("SCO") ("Plaintiff" or "SCO"). In accordance with FRCP 34, AutoZone requests that SCO respond to these Requests for Production within thirty (30) days after service hereof and that SCO produce the documents identified below for inspection and copying by AutoZone's attorneys at the offices of Alston & Bird, LLP, [address], or at such other place as may be agreed upon by counsel for the parties.

Each Request for Production set forth below is addressed to the knowledge of SCO, as well as to knowledge, information and documents in the possession, custody or control of SCO and SCO's attorneys, accountants, agents, employees, or officers.

DEFINITIONS

The following definitions apply with respect to each of the following requests for production and each of the terms defined below, when used in any request for production, shall have the meaning given herein:

(1)        "You", "your", "SCO", or "Plaintiff" means and includes The SCO Group, Inc., any parent, subsidiary, affiliate, successor or predecessor-in-interest thereof, and each of their present and former officers, directors, agents, employees, attorneys, accountants, investigators, consultants or other persons acting or purporting to act for them or on their behalf.

(2)        "AutoZone" or "Defendant" means and includes AutoZone, Inc., any parent, subsidiary, affiliate or related company thereof, and any predecessor-in-interest thereof.

(3)        "Document" means and includes all documents and things covered by Rule 34 of the FRCP and shall have the broadest meaning proscribed therein.

(4)        "Person" means and includes natural persons, individuals, firms, corporations, partnerships, proprietorships, joint ventures, unincorporated associations, government agencies, and all other organizations and entities of any type.

(5)        "Entity" means and includes corporations, companies, businesses, partnerships, proprietorships, or trade names.

(6)        The term "identify" has the following meanings in the following contexts:

(a)        When used with respect to a person or persons, "identify" means to provide each such person's name, last known residence address, last known business address, home telephone number, work telephone number, employer, and place of employment.

(b)        When used with respect to a place, "identify" means to provide the address, city or town, county, and state where that place is located.

(c)        When used with respect to a document, "identify" means to provide that document's current location, author and date, the identity of each recipient, and the subject of the document.
(7)        The term "relate to" shall be construed as to include indicating, referring to, mentioning, reflecting, pertaining to, evidencing, involving, describing, discussing, supporting, or contradicting.

(8)        The term "each" includes the word "every" and "every" includes the word "each." The term "any" includes the word "all" and "all" includes the word "any." The terms "and" as well as "or" shall be construed either disjunctively or conjunctively so as to bring within the scope of the request responses that might otherwise be construed to be outside the scope.

(9)        The singular and masculine form of any word shall embrace, and shall be read and applied as embracing, the plural, the feminine and the neuter.

(10)        The use of a verb in any tense shall be construed as the use of the verb in all other tenses, wherever necessary to bring within the scope of the interrogatory or request for production all responses that might otherwise be construed to be outside the scope.

(11)        "AutoZone's First Interrogatories" means Defendant AutoZone, Inc.'s First Interrogatories to Plaintiff The SCO Group, Inc., served simultaneously herewith.

(12)        "SCO's Injunctive Relief Statement" means SCO's Statement of Basis for Claim for Preliminary Injunctive Relief and Nature of Relief served on AutoZone on August 30, 2004.

INSTRUCTIONS

Discovery on the merits is limited at this time to SCO's claims that AutoZone infringed SCO copyrights when AutoZone migrated from OpenServer to Linux. Accordingly, the scope of documents and information requested in all of AutoZone's discovery requests is limited at this time to SCO's claims of copyright infringement related to AutoZone's migration to Linux.

REQUESTS FOR PRODUCTION OF DOCUMENTS AND THINGS

1.        One copy of each work identified in response to Interrogatory No. 1 of AutoZone's First Interrogatories. For computer code, provide copies of the relevant source and object code.

2.        Documents that reflect or relate to SCO's claims that it owns the copyrights in each of the works, or the relevant sections of the works, identified in response to Interrogatory No. 1 of AutoZone's First Interrogatories.

3.        All correspondence between SCO and any third party, including but not limited to Novell, Inc., relating to SCO's claims that it owns the copyrights in the works identified in response to Interrogatory No. 1 of AutoZone's First Interrogatories.

4.        Copies of the certificates of registration for each registration identified in response to Interrogatory No. 5 of AutoZone's First Interrogatories.

5.        Copies of the applications for registration of each work identified in response to Interrogatory No. 1 of AutoZone's First Interrogatories, including supporting deposit materials.

6.        All documents, including analyses, that evidence or relate to your claims that the works, or relevant portions thereof, that you identified in response to Interrogatory No. 1 of AutoZone's First Interrogatories are subject to protection under the Copyright Act.

7.        All documents that evidence, reflect, or relate to each act or instance of alleged copying or infringement of your works by AutoZone.

8.        All documents that refer, reflect, or relate to AutoZone's use of Linux or its migration from OpenServer to Linux.

9.        All documents that reflect or regard correspondence or communications to or from AutoZone relating to Linux, and all notes and memoranda regarding or relating to the same.

10.        Copies of any license agreements between SCO and AutoZone.

11.        Documents reflecting or relating to when SCO first learned of AutoZone's alleged acts of infringement of SCO's copyrights.

12.        Documents evidencing or relating to any harm that SCO alleges it will suffer if AutoZone is not preliminarily enjoined from its purported acts of copyright infringement.

13.        Statements of any witness who is identified in response to any of AutoZone's First Interrogatories.

14.        All documents, including correspondence, sent to or received from any witness you intend to call as an expert in connection with your motion for preliminary injunction.

15.        All documents referenced or relied upon by any witness you intend to call as an expert in connection with your motion for preliminary injunction.

This 1st day of September, 2004.


James J. Pisanelli, Esq.
Nicki L. Wilmer, Esq.
SCHRECK BRIGNONE
[address, phone]

Attorneys for Defendant
AutoZone, Inc.


CERTIFICATE OF SERVICE

I hereby certify that I have this day served a copy of the within and foregoing DEFENDANT AUTOZONE, INC.'S FIRST REQUESTS FOR PRODUCTION OF DOCUMENTS AND THINGS TO PLAINTIFF THE SCO GROUP, INC. upon all counsel of record addressed as follows:

Stanley W. Parry, Esq.
Glenn M. Machado, Esq.
CURRAN & PARRY
[address]
(Via Hand Delivery)

David S. Stone, Esq.
Robert A. Magnanini, Esq.
BOIES, SCHILLER & FLEXNER LLP
[address]
(Via Hand Delivery)

Stephen N. Zack, Esq.
Mark J. Heise, Esq.
BOIES, SCHILLER & FLEXNER LLP
[address]
(Via First Class Mail)


This 1st day of September, 2004.

__________[signature]__________
An employee of Schreck Brignone


  


AutoZone's 1st Request for Documents - as text | 195 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
9 and 10
Authored by: Anonymous on Sunday, October 17 2004 @ 03:40 PM EDT
These should just be put into the law. It's silly to
have that sort of stuff (singular including plural,
masculine including feminine and neuter) being repeated
in legal documents all across the country all the time.

I suppose congress wants lawyers to have more billable
time. Grrr...

[ Reply to This | # ]

Trolls and ogres here
Authored by: Anonymous on Sunday, October 17 2004 @ 03:41 PM EDT
Hehe, did you notice?
Instead of Nazguls Autozone works with ogres. (Schreck)

[ Reply to This | # ]

Corrections here please
Authored by: MadScientist on Sunday, October 17 2004 @ 03:45 PM EDT

[ Reply to This | # ]

Official "The SCO Group" Positions
Authored by: MadScientist on Sunday, October 17 2004 @ 03:46 PM EDT
Main posts in this thread may only be made by senior managers or attorneys for
"The SCO Group". Main posts must use the name and position of the
poster at "The SCO Group". Main posters must post in their official
capacity at "The SCO Group".

Sub-posts will also be allowed from non-"The SCO Group" employees or
attorneys. Sub-posts from persons not connected with "The SCO Group"
must be very polite, address other posters and the main poster with the
honorific "Mr." or "Mrs." or "Ms.", as
appropriate, use correct surnames, not call names or suggest or imply unethical
or illegal conduct by "The SCO Group" or its employees or attorneys.
This thread requires an extremely high standard of conduct and even slightly
marginal posts will be deleted.

P.J. says you must be on your very best behavior.

[ Reply to This | # ]

Documents and Things
Authored by: snorpus on Sunday, October 17 2004 @ 03:46 PM EDT
I noticed this in the Interrogatories too...

Somehow, Things just doesn't have the right, formal, lawyerly ring to it.

Objects, articles, components, devices, apparatus maybe... but Things?

---
73/88 de KQ3T ---
Montani Semper Liberi

[ Reply to This | # ]

Off topic materials here
Authored by: MadScientist on Sunday, October 17 2004 @ 03:47 PM EDT

[ Reply to This | # ]

Can SCO invalidate this request on a technicality?
Authored by: Kevin on Sunday, October 17 2004 @ 04:13 PM EDT
Definition 3 says,
"Document" means and includes all documents and things covered by Rule 34 of the FRCP and shall have the broadest meaning proscribed therein.

As I mentioned in my post in the "Corrections" thread, the word, proscribed, means, "forbidden." So, as drafted, this entire request demands all and only those "documents" whose production is forbidden by FRCP 34.

Can SCO turn around and say, "we're not producing anything, because you're asking for only that material that's forbidden?" Will that enable it to escape discovery? Oh, what a difference a single keystroke can make!

---
73 de ke9tv/2, Kevin (P.S. My surname is not McBride!)

[ Reply to This | # ]

SCO must get creative again
Authored by: Anonymous on Sunday, October 17 2004 @ 06:02 PM EDT
I guess an answer like "Um, yeah, you know, we needed to sue some
Linux-User and to us it looked like that Unixware-Linux port went just a little
too fast to be true. Oh, and we really think we own the copyrights, er, some
copyrights anyway, which maybe are even relevant to this case." would shut
down their case *really* quick :-)

TToni

[ Reply to This | # ]

Limited Discovery
Authored by: Anonymous on Sunday, October 17 2004 @ 06:31 PM EDT
I thought the Judge limited discovery to irreparable harm. Do the questions
posed by autozone relate to the discovery the judge ordered?

[ Reply to This | # ]

The FIRST thing...
Authored by: Tomas on Sunday, October 17 2004 @ 06:43 PM EDT
The FIRST thing that struck me when I began reading this document was
"...In accordance with FRCP 34, AutoZone requests that SCO respond to these Requests for Production within thirty (30) days after service hereof..."
which caused me to jump to the end of the document to read
"I hereby certify that I have this day served a copy...upon all counsel of record...[t]his 1st day of September, 2004."
which THEN caused me to glance at the top right of my screen to verify that today, Sunday, October 17, 2004, was indeed well past the deadline for at least some sort of response from the folks at The SCO Group (TSCOG).

---
Tom
Engineer (ret.)
Comment ©2004 Tomas@TiJiL.org

[ Reply to This | # ]

"All" but not "any"
Authored by: Khym Chanur on Sunday, October 17 2004 @ 06:50 PM EDT
Among the definitions,
and "all" includes the word "any"
So then, if one side said "Gives us all foo", the other side could reply "Aha! You didn't say any foo, so we don't have to give you this!"? I would think that 'all' just naturally includes 'any', becuase, you know, it's all.

---
Give a man a match, and he'll be warm for a minute, but set him on fire, and he'll be warm for the rest of his life. (Paraphrased from Terry Pratchett)

[ Reply to This | # ]

AutoZone's 1st Request for Documents - as text
Authored by: Anonymous on Sunday, October 17 2004 @ 07:59 PM EDT
This, of course, depends on what your definition of "is" is... ;)

[ Reply to This | # ]

AutoZone's 1st Request for Documents - as text
Authored by: brian on Sunday, October 17 2004 @ 08:29 PM EDT
"Some of you will remember that some time ago, I mentioned
that really good lawyers are careful to craft good
definitions in a legal document. This is a fine example of
doing that. But why do you need a definition of "relate
to" or "person" or "each"? You know what the words
mean,
right?"

If AZ didn't include all these definitions, SCOX would
wiggle out of production to keep the FUD ball in the air.
Just look at how long IBM has been hammering them trying
to get a basic question answered. Don't forget that SCO
says one thing in writing and another in this court and
yet another thing in the other courts. This whole
discovery phase is (in part) because of that. IBM is
exactly correct in the SCO "anywhere but here" strategy.

B.

---
#ifndef IANAL
#define IANAL
#endif

[ Reply to This | # ]

AutoZone's 1st Request for Documents - as text
Authored by: blacklight on Sunday, October 17 2004 @ 08:39 PM EDT
SCOG is probably finding out that the predation business is hell on incompetent
predators.

[ Reply to This | # ]

SCO will probably not respond
Authored by: Anonymous on Sunday, October 17 2004 @ 09:46 PM EDT
I know this is completely wrong and the judge will probably yell at them, but I
doubt SCO will provide the requested items. This is too good of a request and
would kill their business plan. They will probably say that discovery was only
for them so that they could make their claims of harm. So they will say
autozone can't possibly make requests for discovery yet. They have afterall
tried more than once to have the law work only for them. They also don't seem to
care what the judges think about them either.

[ Reply to This | # ]

Well, let's see here....
Authored by: Anonymous on Monday, October 18 2004 @ 12:08 AM EDT
Item 10: "Copies of any license agreements between SCO and AutoZone".

We see that the meaning of SCO "includes The SCO Group, Inc. ... and ...
other persons acting or purporting to act for them or on their behalf."
And, further, the meaning of persons includes "corporations".

Didn't Novell, when they were handing out "get out of jail free" cards
to defendants involved in the suits, give one to Autozone? The text of those
letters stated they were exercising their right to act on SCO's behalf to waive
the rights, since SCO hadn't followed Novell's direction to waive them. And
they do seem to constitute license agreements.

Thus, if there was such a letter, it would appear to me that SCO would be
required to produce it -- whether or not they thought it was valid. Amusing,
that.

[ Reply to This | # ]

Can IBM use any of this?
Authored by: moosie on Monday, October 18 2004 @ 01:01 AM EDT
Is SCO replies with sealed responses (specifically to #6) Can IBM subpena these
fom the AZ case in order to get at least some answers?

- Moosie.

[ Reply to This | # ]

OT - Can You Use Legal Documents as a Template?
Authored by: Whiplash on Monday, October 18 2004 @ 02:07 AM EDT
PJ said: "I'm going to save this to use as a template".

So the question is: Legally: what is the legal status of legal documents?
Can you copy them?
Are they public domain? (Different to being in the public view!)

Are they copywritable? Etc.

Just Curious,

Whiplash

[ Reply to This | # ]

The source code be handed over in an unsuitable form couldn't it?
Authored by: Anonymous on Monday, October 18 2004 @ 03:21 AM EDT
One minor problem I think AutoZone may have is that they (to my eyes) forgot to
close a loophole SCO tried to exploit with IBM. The "Request for
Production..." starts with this item:

1. One copy of each work identified in response to Interrogatory No. 1 of
AutoZone's First Interrogatories. For computer code, provide copies of the
relevant source and object code.

Note that they fail to specify format for any these coputer files. That should
probably read:

1. One copy of each work identified in response to Interrogatory No. 1 of
AutoZone's First Interrogatories. For computer code, provide copies of the
relevant source in the digitial form most appropropriate for editing and
searching the code, and for object code provide copies in an digital format most
appropriate to object code distribution.

Or something like that. As I read it its acceptable for SCO to print a handful
of files in hex and then hand the paper over.

IIRC SCO already pulled this type of thing in the IBM dispute so I think if this
is to be a template that area of the document needs to be enhanced.

[ Reply to This | # ]

Code on paper again?
Authored by: Anonymous on Monday, October 18 2004 @ 03:30 AM EDT
1. One copy of each work identified in response to Interrogatory No. 1 of AutoZone's First Interrogatories. For computer code, provide copies of the relevant source and object code.

For all their careful definitions, Autozone forgot to specify what format they want the code in. Now they will get paper tape or punched cards...

[ Reply to This | # ]

Computer Programmers and Lawyers
Authored by: Anonymous on Monday, October 18 2004 @ 06:45 AM EDT
It has struck me before that Computer Programmers and Lawyers have a lot in
common when it comes to defining precisely what they mean. Maybe that is part of
what makes Groklaw work, along with the hardwork of PJ et al.

[ Reply to This | # ]

SCO's move for reconsideration of the APA ruling
Authored by: codswallop on Monday, October 18 2004 @ 07:00 AM EDT
Now that Silver is on board, they seem to be waking up. When they allowed the
staement that the base agreement didn't transfer the copyrights to go
unchallenged, they screwed up. Silver would like to wriggle out of this. He'll
probably say that had SCO known of the bill of sale, they would have challenged
this, so they deserve another chance. Since this is a new complaint, they may be
entitled to do this. Rule 12(g) applies to defendants, I don't know what the
rules are for plaintiffs.

Since Judge Kimball relied on the issue of the APA not being an instrument of
transfer as being undisputed, he would have to amend/reconsider his decision at
least as far as ruling on this facet as well.

Part of the ruling was based on the future tense of "will convey at
closing". He wants to fix this. The idea is that the bill of sale is a
confirming writing similar to the accepted written confirmation of an oral
conveyance.

With this repaired he can then argue that the copyright exclusion is
contradicted explicitly and by implication by other parts of the agreement. If
this is an ambiguity, then parol evidence is in order and he has a chance of
getting to trial. Certainly it would be enough to avoid dismissal on these
grounds.

He spends a lot of time on the "all right, title and interest" issue.
He's almost certainly right that without the copyright exclusion, the
combination of APA and bill of sale would convey all the copyrights.

A really cute bit is how he gets around the problem of the copyright exclusion.
He can't really argue that the contract as a whole is ambiguous, so the
exclusion should be stricken, because this would probably be very difficult and
parol evidence for this would be disallowed.

Instead he argues that it was just meant to cover the Novell copyrights, not
Unix. Since this is an interpretation of language rather than a change to it,
parol evidence is allowable.

Also Chatlos wasn't around for amendment 2, so his evidence is only good if the
APA itself (with the bill of sale) conveyed copyrights.

This is partly an answer to an earlier post by Quatermass in a dead thread
wondering what SCO was up to in trying to reargue a decided issue.



---
IANAL This is not a legal opinion.
SCO is not a party to the APA.
Discovery relevance is to claims, not to sanity.

[ Reply to This | # ]

We have met the enemy, and he is us
Authored by: Anonymous on Monday, October 18 2004 @ 09:18 AM EDT

SCO originally said they have "millions of lines of code", now they
say they need all of the AIX/Dynix code to compare. Maybe they found out the
original "millions of lines of code" were actually contributed by
Caldera/SCO. That would explain why they are stalling, why they want AIX/Dynix
(to try to find SOMETHING to sue about).

[ Reply to This | # ]

ESL question
Authored by: Anonymous on Monday, October 18 2004 @ 01:10 PM EDT
"The answer is, yes, you know, but if the lawyer doesn't phrase the
question just right, you could say to yourself, "Oh, he said 'each' and in
my mind I thought that didn't include 'every' .."
OK I'll bite. Would someone care to explain a set of circumstances under which
'each' would not mean 'every' ?

[ Reply to This | # ]

  • ESL question - Authored by: Anonymous on Monday, October 18 2004 @ 06:57 PM EDT
    • ESL question - Authored by: Anonymous on Tuesday, October 19 2004 @ 08:33 AM EDT
AutoZone's 1st Request for Documents - as text
Authored by: Anonymous on Monday, October 18 2004 @ 02:08 PM EDT
Predecessor-in-interest. This means it is being served on Tarentella, Novell,
AT&T, USL, Berkley, and who knows all who else also?

[ Reply to This | # ]

"Anthony" Scalia
Authored by: Anonymous on Monday, October 18 2004 @ 04:27 PM EDT
"Anthony" Scalia is what our current President calls him, but Justice
Scalia might prefer that you call him Antonin -- it is his name after all.

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