Академический Документы
Профессиональный Документы
Культура Документы
NOTES
Jason H. Eaddy*
Abstract: This Note argues that the legal tests for determining copyright
infringement in software should be used to analyze copyright claims over
computer databases. The Note provides readers with historical background
regarding copyright protection and compilations, focusing on the distinction
between a database and a mere collection of facts. It then discusses the
originality requirement for copyright protection and provides an in-depth
review of the database design process and the resultant sources of originality
present in databases. Thereafter, the Note provides an overview of the
software development process and the two main legal tests used in analyzing
software for copyright infringement purposes. Then, the Note discusses the
application of those tests to a database analysis, and finally the Note provides
an example of how a small software developer could use provisions of the
Digital Millennium Copyright Act to further protect databases used in its
products.
* Candidate for Juris Doctor, New England School of Law (2008). A.B., Computer
Science, cum laude, Princeton University (1998). For the past eight years, Mr. Eaddy has
provided testifying and non-testifying services in computer-related litigation matters as a
computer scientist at Elysium Digital in Cambridge, Massachusetts.
299
EADDY. FINAL 4/1/2008 10:44:00 PM
INTRODUCTION
As technology usage in companies around the world continues to
expand, and as intellectual property becomes increasingly sought after, so
too does the need for lawyers to protect that property.1 Internet companies
spring up seemingly overnight, have an initial public offering,2 or are sold
for massive amounts of money.3 Regardless of what these companies
mission or product might have been, the major value of many of these
companies is their database of consumer information.4 Another source of
value related to databases is found where software companies distribute
software which uses databases to store both proprietary company
information and information created by the companys clients.5 Protecting
the intellectual property and data underlying those corporations becomes a
primary interest.6 Without protection, there is little to stop an employee
from misappropriating the intellectual property and launching a competing
1. See, e.g., D.M. Osborne, Yahoo 2.0, IP L. & BUS., Oct. 2006, at 48, available at
10/2006 IPLBUS 48 (Westlaw).
2. See, e.g., Why Optimism Could Last This Time, REVOLUTION, June 1, 2005, at 23,
available at 2005 WLNR 9984449 (describing venture capital funding of technology start-
ups reviving after the dot-com crash of the early 2000s).
3. See, e.g., Web Valuations Again, BUSINESS STANDARD, Nov. 21, 2006, at 15,
available at 2006 WLNR 20133169. The rapid manner in which many technology
companies grow adds to the necessity of understanding the ways in which the law can
protect the underlying value. For instance, YouTube was purchased by Google for $1.6
billion a mere eighteen months after its founding. Id. By comparison, the eighty-year-old
Readers Digest was sold for approximately the same amount. Id.
4. See Edward Robinson & Jonathan Thaw, YouTube, Facebook Spark Copycats,
Bubble Fear in Silicon Valley, BLOOMBERG.COM, Feb. 23, 2007, http://www.bloomberg.
com/apps/news?pid=20601109&sid=a8GnNzotH8IQ&refer=home (explaining the values
being paid for internet companies with large user bases and large amounts of data).
5. See, e.g., Lifeware TEK Launches I-Cook Recipe Management System, WORLDWIDE
DATABASES, Jan. 1, 2007, available at 2007 WLNR 1293 (desktop software which stores
recipes in a database locally and on a web server); Hy-Tek Sports Software for Swimming
and Track and Field, http://www.hy-tekltd.com (Hy-Tek is a software manufacturer
specializing in support of individual-focused sports, such as track and swimming, including
competition management, team organization, and workout planning. Each of Hy-Teks
products communicates with a database, the design of which is distributed to all purchasers
as a part of the software package). Furthermore, open source database software is a booming
industry providing free versions of database software that companies can use in their
software. See Barbara Grady, Startups Mainstream Open-Source Software, OAKLAND TRIB.,
Mar. 6, 2006, available at 2006 WLNR 3765381 (discussing various open source projects
including the widely used MySQL database and database juggernaut Oracles entry into this
arena).
6. See generally U.S. Patent and Trademark Office and AeA Join Together to Fight IP
Theft, Stop Fakes, http://www.aeanet.org/GovernmentAffairs/gajl_stopfakes0805.asp (last
visited Mar. 26, 2008).
EADDY. FINAL 4/1/2008 10:44:00 PM
7. See id.
8. 499 U.S. 340 (1991).
9. Id. at 344-45 (quoting Harper & Row, Publishers, Inc. v. Natl Enters., 471 U.S.
539, 556 (1985)).
10. See Martin Goetz, Patents: Wheres the Invention?, COMPUTERWORLD, Mar. 6,
2006, at 24, available at 2006 WLNR 8808455 (describing the proliferation of software
patents and the fact that software is already protected by copyright).
11. See generally Microsoft Corp., Access Home Page, http://office.microsoft.com/en-
us/access/default.aspx (last visited Mar. 26, 2008).
12. See Walker v. Time Life Films, Inc., 784 F.2d 44, 48 (2d Cir. 1986) (stating that
proving copyright infringement requires showing access to the copyrighted work).
13. See infra Part IV (discussing copyright infringement analysis in software).
14. See infra Part II for a discussion of the requirements for copyright protection of a
database.
15. See Computer Assocs. Intl., Inc. v. Altai, Inc., 982 F.2d 693, 701 (2d Cir. 1992)
EADDY. FINAL 4/1/2008 10:44:00 PM
United States copyright law only grants protection for databases containing
a requisite amount of originality; this law does not provide protection to
databases which would only qualify under the sweat-of-the-brow theory.26
Under the sweat-of-the-brow theory, a person who expends
sufficient effort to obtain the data underlying a database is entitled to
protection of the data.27 This doctrine, also termed industrious collection,
state[s] that copyright protection could be provided to those who exert hard
work in compiling information.28 This philosophy means that if a second
person wishes to create a similar database, he must start from scratch and
obtain all of the data himself.29 The sweat-of-the-brow theory rewards the
effort rather than the creativity.30 This philosophy has been validated in
various European states under a European Council directive on database
protection.31
The second theory, loosely termed, the originality theory, holds that
databases must be sufficiently original to qualify for protection under
federal copyright law.32 Article I, section 8, clause 8 of the United States
Constitution gives Congress the authority to encourage scientific and
artistic progress by protecting an authors writings.33 This so-called
writings requirement is satisfied under federal copyright law by requiring
protected works to be fixed in any tangible medium of expression, now
known or later developed, from which they can be perceived, reproduced,
or otherwise communicated.34 Just as important to the copyright protection
26. See generally Feist Publns, Inc. v. Rural Tel. Serv. Co., 499 U.S. 340 (1991). Feist
addressed the fact that lower courts adopted the sweat of the brow or industrious
collection test and extended a compilation's copyright protection beyond selection and
arrangement to the facts. Id. at 352-53. For a more detailed discussion, see infra Part II.A.
27. See Robert Howell, Editorial, Using the Ideas but Not the Expressions from Abroad,
MANAGING INTELL. PROP., Feb. 2006 (discussing the originality requirement in the U.S. and
Canada), available at 2006 WLNR 4066365.
28. Patrick W. Ogilvy, Note, Frozen in Time? New Technologies, Fixation, and the
Derivative Work Right, 8 VAND. J. ENT. & TECH. L. 687, 716 (2006).
29. See id.
30. Id.; see also Feist, 499 U.S. at 344 ([F]acts are not copyrightable; . . . compilations
of facts generally are.).
31. See Council Directive 96/9, art. 7, 1996 O.J. (L 77) 20 (EC), available at
http://www.wipo.int/clea/docs-new/pdf/en/eu/eu005en.pdf.
32. See Feist, 499 U.S. at 345.
33. U.S. CONST. art. I, 8, cl. 8 (Congress shall have Power . . . To promote the
Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors
the exclusive Right to their respective Writings and Discoveries.) (emphasis added).
34. 17 U.S.C. 102(a) (2000). [A]lthough the word writings might be limited to
script or printed material, it may be interpreted to include any physical rendering of the
fruits of creative intellectual or aesthetic labor. Goldstein v. California, 412 U.S. 546, 561
(1973).
EADDY. FINAL 4/1/2008 10:44:00 PM
1. Factual Background
In Feist, Rural Telephone Service Co. (Rural) brought suit against
Feist Publications, Inc. (Feist), alleging that Feist unlawfully copied a
telephone directory.43 Rural was a local telephone provider that published a
35. Feist, 499 U.S. at 345 (The sine qua non of copyright is originality.).
36. 17 U.S.C. 102(a), 103(a).
37. Id. 101.
38. Id. 103(b).
39. Id.
40. See supra notes 27-31 and accompanying text.
41. See supra notes 32-39 and accompanying text.
42. 499 U.S. 340 (1991).
43. Id. at 344.
EADDY. FINAL 4/1/2008 10:44:00 PM
local telephone directory, including both white and yellow pages.44 This
lawsuit focused solely on the listings from the white pages portion of the
directory.45 Like any other white pages listing, Rural provided the names of
its subscribers, in alphabetical order, along with the subscribers towns and
telephone numbers.46 This listing was distributed to all of Rurals
subscribers free of charge.47
In contrast to Rurals local listing, Feist published listings of white
and yellow pages covering a much larger area consisting of multiple
smaller telephone service areas, including the area covered by Rurals
listings.48 Out of eleven local telephone companies providing service in the
areas covered by Feists listings, only Rural refused to license its listings to
Feist for the larger publication.49 Because Feist itself was not a telephone
service provider, the company did not have a direct resource to obtain the
data from Rurals customers for Feists book.50 Instead of leaving the Rural
listings out or continuing to negotiate with Rural for its data, Feist hired
personnel to process Rurals records, exclude any listings outside Feists
intended publication area, and gather additional information, such as street
addresses, for each listing.51 Feist then published its book, including the
listings obtained without a license from Rural.52 Rural subsequently
brought a copyright action as a result of Feists use of Rurals
information.53
2. Holding
In deciding Feist, the Court reiterated that facts themselves are not
protectable, but that compilations of facts are protectable.54 Here, the two
telephone books constituted compilations, the entirety of each being
copyrightable.55 Federal copyright law protects compilations under section
103(a),56 and limits that protection, under section 103(b), to the work added
66. Id.
67. Feist, 499 U.S. at 345.
68. Id. at 348. The Court actually mentions three such items: selection, order, and
arrangement. Id.
69. See id.
70. Id.
71. Id.
72. Id.
73. Feist, 499 U.S. at 349.
74. 878 F. Supp 804 (D. Md. 1995).
75. Id. at 808.
76. Id.
EADDY. FINAL 4/1/2008 10:44:00 PM
77. Id.
78. Id. at 808-09.
79. Id. at 809.
80. Montgomery County, 878 F. Supp at 810.
81. Id.
82. Id.
83. Id.
84. 26 F.3d 1335 (5th Cir. 1994).
85. See id. at 1340.
86. Id. at 1339. The formats in question are specifications regarding how the data
operated on by the program and the data that is given back to the user are organized. See id.
at 1338. The . . . input formats instruct the user to place specific kinds of information in a
specific place on the card. Id.
EADDY. FINAL 4/1/2008 10:44:00 PM
opinion, the court ruled that WIREdata should be given the raw assessment
data from the Market Drive database; it reversed the judgment and ordered
the district court to dismiss the copyright claim in its entirety.98
Instead of finding a lack of originality in the storage of the data, the
court fell back to the lack of originality in the data itself.99 Additionally,
Assessment Technologies could not assert ownership of this data as it was
in the public domain and gathered by public workers.100 In fact, Wisconsin
had an open records law requiring that public records be provided to
anyone who would pay the copying fee.101 However, there was a specific
carve-out in the law to prevent government agencies from being required to
produce copyrighted data.102 Here, the court found that the basic facts about
the houses, provided in a manner different from how they were stored by
the Market Drive software, were merely uncopyrightable facts and
therefore should have been produced.103
Even so, the opinion makes it clear that the database itself was
protected under copyright even though Assessment Technologies failed to
protect the underlying data.104 Indeed, the court stated that WIREdatas
appeal g[ot] off on the wrong foot, with the contention that Market Drive
lack[ed] sufficient originality to be copyrightable.105 The court realized
that no other assessment software stored its information in a database
containing 456 fields grouped into . . . 34 categories106 and that this
structure was not obvious or inevitable.107 Therefore, Assessment
Technologies held a valid copyright in the Market Drive program and
underlying database based upon the originality in the design of the database
itself, as opposed to the data contained inside.108
109. See, e.g., id. (appellant argued that there was no valid copyright in a database
because of the public facts contained therein); Matthew Bender & Co. v. West Publg Co.,
158 F.3d 693, 698-99 (2d Cir. 1998) (describing aspects of Wests legal database as a
collection of uncopyrightable facts, and finding that there was not enough originality in the
presentation for copying to constitute infringement) .
110. ABRAHAM SILBERSCHATZ ET AL, DATABASE SYSTEM CONCEPTS 1 (3d ed. 1996).
111. See id.
112. Id.
113. Id.
114. Id. at 4.
115. See id.
116. See SILBERSCHATZ ET AL., supra note 110, at 4.
117. See id. Usually, the underlying data will be stored on one or more hard disk drives,
but these files could be stored in non-volatile RAM. See, e.g., McObject LLC, Embedded
Databases for Real-Time Military and Aerospace, http://www.mcobject.com/milaero.shtml
(last visited Mar. 26, 2008).
118. See SILBERSCHATZ ET AL., supra note 110, at 4; PostgreSQL, PostgreSQL 8.1:
Database Physical Storage, http://www.postgresql.org/docs/8.1/interactive/storage.html (last
visited Mar. 26, 2008) (describing how the PostgreSQL system stores the files for each
database stored in the system and does not describe how a user could change those files).
EADDY. FINAL 4/1/2008 10:44:00 PM
119. See Feist Publns, Inc. v. Rural Tel. Serv. Co., 499 U.S. 340, 345, 348 (1991).
120. See SILBERSCHATZ ET AL., supra note 110, at 63.
121. E.F. Codd, A Relational Model of Data for Large Shared Data Banks, 13 COMM. OF
THE ACM 377 (1970), available at http://www.seas.upenn.edu/~zives/03f/cis550/codd.pdf.
122. See SILBERSCHATZ ET AL., supra note 110, at 63.
123. As examples of commercial, closed-source database products, see the following
websites: Microsoft, Microsoft SQL Server, http://www.microsoft.com/sql/default.mspx
(last visited Mar. 26, 2008); Microsoft, Microsoft Access Homepage, http://
office.microsoft.com/en-us/access/FX100487571033.aspx (last visited Mar. 26, 2008);
Oracle, Oracle Database 11g, http://www.oracle.com/features/hp/11g-generalavailability
.html (last visited Mar. 26, 2008). Additionally, open-source, freely-available database
products can be found here: Firebird Foundation, Inc., Firebird - Innovative RDBMS Thats
Going Where Youre Going, http://www.firebirdsql.org/index.php (last visited Mar. 26,
2008); MySQL Ab, MySQL Products, http://www.mysql.com/products/ (last visited Mar.
26, 2008); PostgreSQL, PostgreSQL: About, http://www.postgresql.org/about/ (last visited
Mar. 26, 2008).
124. See infra Part IV.
125. See supra text accompanying note 109.
126. See infra Part III.A.
EADDY. FINAL 4/1/2008 10:44:00 PM
copyright protection.138
The type of information contained in a tables fields is defined when
the table is created.139 A field can contain a wide variety of data types
including numbers, dates, times, a single character, a string field
consisting of multiple characters, and numerous other data types.140 These
data types can be further refined by the size of data they can hold, i.e. a
small integer (1-byte, can hold values up to the number 255), a large
integer (4-bytes, can hold values up to 4,294,967,295), or a 20-character
string.141 Again, the naming of columns and the selection of the particular
data types when defining columns in a table present potential choices for a
database designer, and therefore additional examples of originality
involved in the design of a database schema.
After the database designer determines the data to be stored in a
particular table, a further step in the table definition involves specifying the
keys, or indices and constraints placed on the table.142 Each table may, and
usually should, have a single primary key, consisting of one or more
columns where the value of the column is unique for any given row of data
contained in the table.143 For example, primary keys could be unique part
numbers, vehicle identification numbers of cars, or social security
numbers.144 Alternatively, most relational DBMS solutions provide an
auto-generated primary key, which will populate the primary key field for a
given table with a unique number.145 The unique property of a primary key
means that the database system can store a link to the data for fast retrieval
of a particular row from storage.146
Similarly, a database designer creates indices on tables to facilitate
fast retrieval of data upon requests for data matching particular
properties.147 A library card catalog system for looking up books by authors
138. See Assessment Techs. of Wis., L.L.C. v. WIREdata, Inc., 350 F.3d 640, 643 (7th
Cir. 2003) (defining the grouping of fields as satisfying the originality requirement of Feist).
139. See Microsoft, Add a Field to a Table, http://office.microsoft.com/en-
us/access/HA100728831033.aspx?pid=CH100645681033 (last visited Mar. 26, 2008).
140. See, e.g., POSTGRESQL GLOBAL DEV. GROUP, POSTGRESQL 8.2.0 DOCUMENTATION
91 (2006).
141. See, e.g., id.
142. Database Design Basics, supra note 133; see DATAMIRROR MOBILE SOLUTIONS,
INC., POINTBASE DEVELOPERS GUIDE VERSION 4.8 at 76 (2004), http://dlc.sun.com/pdf/817-
7464/817-7464.pdf.
143. See Database Design Basics, supra note 133.
144. See id.
145. See, e.g., POSTGRESQL GLOBAL DEV. GROUP, supra note 140, at 95-96.
146. See SILBERSCHATZ ET AL., supra note 110, at 339.
147. See id. An index allows the database server to find and retrieve specific rows much
faster than it could do without an index. PostgreSQL, Documentation: Manuals:
EADDY. FINAL 4/1/2008 10:44:00 PM
the data from a row in another table in the database.159 In the related table,
the field being referenced is called a foreign key.160 There are three types
of relationships that can be defined between tables: one-to-one, one-to-
many, or many-to-many.161 As their names suggest, these relationships
define data that matches from one object to only one other object, from one
object to multiple other objects, or from multiple objects to multiple objects
respectively.162
Because primary keys, indexes, constraints, and relationships allow
for the efficient storage of the data and correlation with the other tables in
the database, their usage and definitions supply the originality in the design
which qualifies the database for copyright protection.
Computer science theory has determined how to most efficiently
organize the data, but real-world designs usually differ from the theoretic
perfection.163 The primary reason for this difference is improved
performance.164 The process of moving the database from a structure that
stores the intended information to one that stores it efficiently is called
normalization.165 While more exist, the most common forms of
normalization are first, second, and third normal form.166 The theoretical
details behind these forms are not particularly relevant to this Note; the
point is that there are theoretical reasons for a number of the choices made
by a designer when creating a database schema167 and that these choices
can result in commonalities between otherwise independently developed
databases.
Classes
Name Data Type Key?
Id Auto Number Primary
Title Character(60)
name_instructor Character(30)
Semester Character(6)
Year Integer
168. See, e.g., PostgreSQL, Documentation: Manuals: PostgreSQL 8.2: Numeric Types,
8.1.4, http://www.postgresql.org/docs/8.2/static/datatype-numeric.html#DATATYPE-SERI
AL (last visited Mar. 26, 2008).
169. See Drew Georgopulos, Develop a Consistent Naming Convention for Your
Database Objects, DEVX.COM, Feb. 10, 2003, http://www.devx.com/dbzone/Article/
10866/1954 for an article addressing naming conventions in databases. The larger a
database grows and the more databases a corporation uses in its business, the more
important it becomes to have a consistent naming scheme. See id.
170. Microsoft, Database Design Basics, http://office.microsoft.com/en-us/access/
HA012242471033.aspx (last visited Mar. 26, 2008).
EADDY. FINAL 4/1/2008 10:44:00 PM
Students
Name Data Type Key?
Id Auto Number Primary
name_first Character(20)
name_last Character(30)
Middle_initial Character(1)
date_birth Date
Grades
Name Data Type Key?
Id Auto Number Primary
student_id Integer Foreign
class_id Integer Foreign
Grade Integer
source code down into multiple files,202 each of which may contain one or
more routines,203 commonly called functions in many programming
languages.204 Generally, a function is a grouping of instructions which the
programmer gives a name and which can be executed or called multiple
times within a program.205
With regard to copyright, the expression of a computer program can
take two shapes: source code and object code.206 Source code for a piece of
software consists of multiple files containing instructions written in a
programming language.207 By grouping instructions into functions and
grouping functions into files which are stored on a computers hard drive, a
developer fixes the softwares source code in a tangible medium of
expression, thereby qualifying the source code for copyright protection.208
In a typical case, the source code files are compiled into object code.209 The
object code is what the computers operating system loads and eventually
runs.210 Unsurprisingly, courts have acknowledged that direct copying of
source code or object code constitutes copyright infringement.211
1. Factual Background
In this matter, one of the defendants, Rand Jaslow, ran a dental
laboratory which manufactured dental prosthetics and devices.215 Jaslow
felt that a computer program could help the operation of his business, and
he attempted to write such a program.216 Without any background in
computer programming, Jaslow ultimately came to the conclusion that he
could not create the software himself.217
After the failure, Jaslow hired Elaine Whelans company to create the
dental laboratory management software, called Dentalab.218 Whelan
followed the standard software development cycle, spending a considerable
amount of time gathering the requirements for the software by examining
the operations at the Jaslow laboratory and other dental laboratories to gain
an understanding of how the software should operate.219 Once the software
was written, the two parties reached an agreement regarding marketing,
sales, and profit sharing that served them well for two years.220
During the period in which the two parties worked together, Rand
Jaslow became more familiar with computer programming and realized that
there was the potential for greater sales if the Dentalab software was
written for a different type of computer.221 After a year of work on his own
software, which he called Dentcom, Jaslow notified Whelan that their
contract was being terminated.222 Jaslow hired another programmer to
complete the work and proceeded to sell the finished product.223
212. 797 F.2d 1222 (3d Cir. 1986), affg 609 F. Supp. 1307 (E.D. Penn. 1985).
213. Id. at 1224.
214. See id. at 1224-25.
215. Id. at 1225.
216. Id.
217. Id.
218. Whelan, 797 F.2d at 1225-26.
219. Id.
220. Id. at 1226.
221. Id.
222. Id.
223. Id. at 1226-27.
EADDY. FINAL 4/1/2008 10:44:00 PM
For copyright purposes, the key distinction between the Dentalab and
Dentcom computer programs is that the two were written in different
languagesDentalab was written in EDL and Dentcom was written in
BASIC.224 This fact is important because, like normal spoken languages,
computer programming languages appear remarkably different even when
the languages communicate the same thing.225
224. Whelan, 797 F.2d at 1226. EDL was a programming language used on an IBM
Series/1 mainframe. Id. BASIC is a programming language, developed in the 1960s, and
became popular with the rise of home computers in the 1970s and 1980s. Mary Bellis, The
History of BASIC Beginners All Purpose Symbolic Instruction Code, http://
inventors.about.com/library/inventors/blbasic.htm (last visited Mar. 26, 2008).
225. See Whelan, 797 F.2d at 1233. In this case, however, the district court did not find
any copying of the source or object codes, nor did the plaintiff allege such copying. Id.
226. Id.
227. Id. at 1234. The court goes on to state that it looked for comprehensive nonliteral
similarity when performing the substantial similarity analysis. Id. at 1234 n.26.
228. Id. at 1234.
229. Id. at 1236.
230. Id. (emphasis omitted).
231. See Whelan, 797 F.2d at 1236.
232. Id. at 1229-30.
EADDY. FINAL 4/1/2008 10:44:00 PM
242. Computer Assocs. Intl, Inc. v. Altai, Inc., 775 F. Supp. 544, 553 (E.D.N.Y. 1991),
affd 982 F.2d 693 (2d Cir. 1992).
243. Id. at 553-54. Altais program actually took some thirty percent of its code from
Computer Associates product. Id. at 554.
244. Id. at 554. These programmers were prevented from seeing the previous source code
or speaking with the employee who brought the code to the company. Id.
245. Computer Assocs., 982 F.2d at 706.
246. Id. at 705.
247. Id.
248. Id.
249. See id. at 706.
250. Id.
251. Computer Assocs., 982 F.2d at 706-10. See also generally Donald R. Robertson, III,
Note, An Open Definition: Derivative Works of Software and the Free/Open Source
Movement, 42 NEW. ENG. L. REV. 339, 346-61 (2008) (arguing that the abstraction, filtration
and comparison test should be used universally in cases of unauthorized derivative works of
software).
EADDY. FINAL 4/1/2008 10:44:00 PM
In the abstraction step, the court dissects the software into a series of
abstractions from the lowest level steps of the program to the functional
and file organization to the general purpose of the program.252 Along the
way, it is necessary essentially to retrace and map each of the designers
stepsin the opposite order in which they were taken during the programs
creation.253 The higher the level of abstraction, the simpler the view of the
program becomes.254 Hence, the court would break out the program at each
level, from the individual instructions, to the functions, to the program as a
whole.255
The filtration step separates the portions of the program which are
covered by copyright and those items which are not protectable.256 As
stated previously, ideas are not protectable, but a particular expression of
an idea is protectable by copyright.257 Items which are necessarily incident
to the expression of an idea are not protectable.258 Under this step, the court
looks at each of the pieces of the abstraction from the first step, and
determines whether or not the particular aspect was an idea or dictated
by considerations of efficiency . . . ; required by factors external to the
program itself; or taken from the public domain.259 If any of these are true,
that particular element is not protectable by copyright and must be removed
from further consideration in determining whether or not the two programs
were substantially similar.260
This doctrine of merger is based upon the fact that [w]hen there is
essentially only one way to express an idea, the idea and its expression are
inseparable and copyright is no bar to copying that expression.261 In
software, for example, efficiency is often the reason given for the
commonality of expression and this step protects an innocent second party
from copyright liability when there was only a single good way for a
portion of a program to be written.262
The final step, comparison, involves actually comparing the
remaining elements after the court completes the first two steps.263 After
the abstraction and filtration steps, the court may be left with a core of
protectable expression.264 Here, the court checks to see whether the
defendant copied any of the plaintiffs protected expression and what level
of importance these elements have in relation to the overall work of the
plaintiff.265 It is left to the trier of fact to determine whether or not the
defendants copying took such a quantity of material from the plaintiff such
that [the] defendant wrongfully appropriated something which belongs to
the plaintiff.266 Given the nature of the works at hand, however, expert
testimony is acceptable with regard to explaining the various abstractions
and filtrations necessary for the analysis to succeed.267
273. See supra Part IV.B.2, C. Like the court in Whelan, this Note treats the terms
structure, sequence, and organization interchangeably. See Whelan Assocs., Inc. v.
Jaslow Dental Lab., Inc., 797 F.2d 1222, 1224 n.1 (3d Cir. 1986).
274. Computer Assocs., 982 F.2d at 705-06.
275. Id.
276. Whelan, 797 F.2d at 1236.
277. See id.
278. See Computer Assocs., 982 F.2d at 706.
279. See supra Part III.A (describing the various static parts of database design); supra
Part III.C (describing the few potentially dynamic aspects of databases). Because there are
not generally the equivalent of functions called interactively in a database, the structure
of a database does not dynamically change like software.
EADDY. FINAL 4/1/2008 10:44:00 PM
Next, looking at the Grades table in the example database brings out
the abstraction of the relationships between the tables.287 The information
contained in the Grades table includes pointers to the other two tables
because the information contained in that table is not particularly useful
when considered separately from the other two tables.288 Additionally, the
table level of abstraction provides the opportunity to abstract out the
indices and constraints imposed on the various fields of a table.289 The final
abstraction is that of the entire database itself, a representation of all the
class, student, and grade information for a school.290
After the abstractions, the court should look at the validity of
copyright protection on the work as a whole. Under Feist, if a work is to be
protected by copyright law, it must possess[] at least some minimal degree
of creativity of the originality required for protection.291 Feist teaches that
if the database schema merely arranges information in an obvious or
completely trivial manner, then the schema does not have enough
originality in its expression to qualify under this standard.292 This
originality requirement implies that a simplistic database which simply
stores standard information in a single table, or perhaps even just a few
tables, could be too unoriginal to qualify for protection.293
impose restrictions upon the information that can be kept in a table.305 For
instance, an index could be created on the last names table to allow faster
retrieval of a particular record when searching by last name.306 A constraint
could be imposed on the table requiring the combination of the three name
fields and the date of birth field to be unique in the table.307 These indices
and constraints are optional items which are often imposed as part of the
optimization of a database in order to speed access or ensure data
integrity.308 As such, they are separate from the ideas represented therein
and constitute protectable expression.
Finally, the idea of the overall database is designed to store a specific
set of information, such as the idea of tracking grades in a school.309 As
this is inherently just an idea, it is not protectable by copyright.
easily avoided and does not constitute much of an actual barrier to the
viewing of a database schema.322 This is where the DMCA reifies the
password protection mechanism.
As previously stated, the DMCA provides that no one is allowed to
circumvent a technological measure which effectively controls access
to a copyrighted work.323 Potentially foreseeing an inevitable debate
surrounding the definition of these terms, Congress helpfully acted as its
own lexicographer and clearly set forth what its intent was in the
legislation.324
A person circumvents of a technological measure if he or she
avoid[s] . . . [or] bypass[es] . . . a technological measure, without the
authority of the copyright owner.325 Clearly, someone using a piece of
software designed to provide access to a password-protected database
without knowing the password avoids the technological measure that is
inherent in the password protection.
However, there is no DMCA violation unless the circumvention is of
a device which effectively controls access to the copyrighted work,326
meaning that the measure must require[] the application of information
during its ordinary course of . . . operation in order to access the
protected work.327 In this hypothetical, the supplied information used to
gain access to the database file is the previous specified password.328
Hence, the password protection mechanism qualifies as an effective
protection mechanism and bypassing that protection constitutes a violation
of the anti-circumvention provision of the DMCA.329
VII. CONCLUSION
Protecting the intellectual property investment of companies is of
growing importance to the legal industry.335 As such, lawyers need to
understand the various sources of intellectual property in their clients
possession and the protection options available for each of them. This Note
presented a hypothetical situation where a client developed a piece of
software and a related database which was thereafter illicitly copied.336
Because of the complicated nature of a database, the ordinary
observer is not likely to be able to determine whether or not a copyright in
a database has been violated without the assistance of expert testimony.337
This expert testimony should follow the practices developed in the Whelan
and Computer Associates cases in order to properly extract all of the
expression potentially protected by copyright and arrange it for the
ordinary observer to review.338 The adapted test proposed in this Note
presents an opportunity to provide a standard method of review for
database copyright analysis which should help lawyers protect their
intellectual property.
Finally, given the protection afforded to copyright holders under the
DMCA, a software company that distributes a copyrightable database in
conjunction with its software should strongly consider protecting its