Copyright Protection for Software and Databases

Copyright protects original works of authorship fixed in a tangible medium, including literary works. For software and databases, this means protection can extend to:

Source code and object code

Structure, sequence, and organization (SSO)

Documentation, user manuals, and GUI elements

Databases (compilations, if there is originality in selection or arrangement)

However, copyright does not protect:

Ideas, methods, processes, or functional aspects of software (those may be patentable)

Facts or raw data in databases (only the selection/arrangement may be protected)

PART I: Key Principles of Software and Database Copyright

1. Software Protection

Source code and object code are considered “literary works.”

Protection covers literal elements (code) and non-literal elements (structure, sequence, and organization).

Reverse engineering or decompiling may be restricted under copyright law, depending on licensing.

2. Database Protection

Original selection and arrangement of data is protected.

Raw data itself (facts) cannot be copyrighted.

Databases may be protected under:

Compilation copyright (originality in selection/coordination)

Sui generis database rights (EU-style, not U.S.)

3. Licensing and Monetization

Software and databases can be licensed via:

Proprietary licenses (perpetual or subscription)

Open source (GPL, MIT, Apache)

Field-of-use restrictions for enterprise databases

Licensing revenue depends on enforceability, originality, and market adoption.

PART II: Key Case Laws and Detailed Analysis

Here are seven landmark cases that shaped software and database copyright law:

1. Apple Computer, Inc. v. Franklin Computer Corp. (1983)

Issue:

Are computer operating systems (OS) copyrightable?

Holding:

OS software, including source and object code, is protected under copyright.

Impact:

Affirmed software as a “literary work”

Companies can enforce licensing and prevent copying of system software

Set precedent for corporate software monetization

2. Computer Associates International, Inc. v. Altai, Inc. (1992)

Issue:

How to determine copyright infringement for non-literal elements of software?

Holding (Abstraction-Filtration-Comparison Test):

Abstraction: Break software into layers (functions, modules, code)

Filtration: Remove unprotectable elements (ideas, efficiency constraints, public domain code)

Comparison: Compare remaining protectable elements for copying

Impact:

Non-literal code (structure, sequence, organization) is protected, but only original elements

Critical for licensing negotiations and litigation

Influences valuation of software IP portfolios

3. Oracle America, Inc. v. Google, Inc. (2016)

Issue:

Can APIs (application programming interfaces) be copyrighted?

Holding:

Oracle claimed APIs were copyrightable; Supreme Court remanded for fair use evaluation

Ultimately, limited copying may be permissible under fair use

Impact:

APIs may receive copyright protection, enhancing software monetization

Raises licensing importance for frameworks and developer tools

4. Feist Publications, Inc. v. Rural Telephone Service Co. (1991)

Issue:

Are telephone directories protected by copyright?

Holding:

Facts themselves are not copyrightable

Original selection, coordination, or arrangement is protected

Impact:

Critical for database protection

Monetization depends on creative arrangement, not raw data

Applies to bioscience, financial, and commercial databases

5. Lotus Development Corp. v. Borland International, Inc. (1995)

Issue:

Can menu command structures of software be copyrighted?

Holding:

The First Circuit held that menu command hierarchy was a “method of operation” and not copyrightable

Supreme Court deadlocked, leaving the lower court decision in place

Impact:

Functional elements of software may not be protected

Emphasizes need to focus copyright claims on expressive, not functional, elements

6. MAI Systems Corp. v. Peak Computer, Inc. (1993)

Issue:

Does loading software into RAM constitute a copy?

Holding:

Yes, loading software into RAM creates a “copy” under copyright law

Impact:

Expands enforcement potential for licensing agreements

Supports monitoring and compliance for SaaS and cloud-based software

7. ProCD, Inc. v. Zeidenberg (1996)

Issue:

Are shrink-wrap licenses enforceable?

Holding:

Yes, shrink-wrap license terms can bind users if agreed upon

Impact:

Critical for software monetization

License restrictions on copying, reverse engineering, or redistribution are enforceable

8. Assessment of Database Rights – International Case Context

While not strictly U.S., EU law provides additional insight:

Sui generis database right (Directive 96/9/EC) protects investment in data collection

Example: EU databases can be licensed even if raw facts are unprotectable

Startups can monetize curated datasets via licensing agreements

PART III: Practical Insights for Software and Database Copyright Monetization

Protect Both Literal and Non-Literal Elements

Source code, object code, SSO, and GUI layouts

Document Originality

Software and databases should have a clear record of selection, arrangement, and creation

Use Licensing Strategically

Proprietary, subscription, field-of-use, or API-based licensing

Enforce Contracts

Shrink-wrap, click-wrap, SaaS agreements are enforceable (ProCD v. Zeidenberg)

Monitor Functional vs. Expressive Elements

Functional features may not be protected (Lotus v. Borland)

Consider International Protections

Databases may have additional rights in jurisdictions like the EU

Leverage Copyright for Monetization

Licensing revenue, acquisition premium, defensive IP, and litigation leverage