About the Collection

Historical Note

The American Committee for Interoperable Systems (ACIS) was an organization of technology companies that advocated for the interoperability of computer systems and software.

ACIS took part in public debate over how copyright law should treat software interfaces and reverse engineering, filing amicus briefs in appellate litigation and submitting comments to government bodies. Its founding and advocacy are described in The Legacy of ACIS below.

The Legacy of ACIS

In the early 1990s, software developers faced a consequential question: who could make a product work with a computer system controlled by another company? Compatibility often depended on understanding an existing program’s interfaces: the rules through which programs exchange information or respond to commands. A developer might need to study a program closely, sometimes through reverse engineering, before building an independent product that could communicate with it. The American Committee for Interoperable Systems (ACIS) formed to defend room for that work in intellectual property law.

ACIS took shape at a December 1991 meeting at Sun Microsystems, chaired by Sun’s deputy general counsel, Peter M. C. Choy. It was an informal association rather than a standards body. Its participants included companies developing hardware and software intended to operate with systems made by others. The breadth of its membership mattered: interoperability was a practical concern for chip makers, computer manufacturers, software firms, and smaller developers alike. Their products could succeed or fail according to whether they were permitted to connect with systems already in widespread use.

The principles ACIS advanced

Protection for original software: ACIS supported intellectual property protection that rewarded developers for creating new programs.
Access to functional interfaces: It argued that copyright should not give a program’s owner exclusive control over the rules and specifications another developer needed to achieve compatibility.
Reverse engineering for interoperability: ACIS defended the study of lawfully obtained software to discover how systems communicate, including the incidental copying that such study could require.
Independent, compatible products: Developers, it argued, should be able to use what they learned to create their own implementations, whether those products complemented or competed with an established system.
Competition in connected markets: ACIS warned that control over a widely used interface could become control over which other products were able to enter a market.

These positions drew a distinction between protecting a company’s original implementation and allowing others to understand the functional means of connecting with it. For ACIS, compatibility was part of the process by which software improved: developers could make new tools, serve users of existing systems, and offer alternatives without having to reproduce the original product.

In the courts

ACIS pressed its case in the courts. It submitted or joined briefs in disputes over software interfaces, compatibility, and reverse engineering, including Sega Enterprises v. Accolade, Lotus Development v. Borland, Apple Computer v. Microsoft, and Sony Computer Entertainment v. Connectix. The cases raised different legal questions, but each touched on the boundary between a company’s rights in its software and another developer’s ability to make something that worked with it. ACIS’s briefs brought the practical concerns of developers and users into proceedings between individual litigants. The decisions belong to the courts and cannot be credited to ACIS alone; the committee’s documented contribution was to argue consistently for compatibility when those legal boundaries were being tested.

Browse the Amicus Briefs series →

Policy and legislation

Its work extended beyond litigation. In a 1992 communication to the incoming Clinton administration, ACIS urged policymakers to consider interoperability, fair competition, and open systems alongside strong intellectual property protection. As plans for a national and global information infrastructure developed, ACIS entered debates over who would control the interfaces connecting networks, devices, and services. The issue was particularly important where an interface had become a practical gateway to a market. A company that controlled that gateway could influence which competing products were able to participate.

The same concern arose during the debate over the Digital Millennium Copyright Act. ACIS and the Computer & Communications Industry Association warned that restrictions on bypassing technological locks could obstruct legitimate efforts to discover how programs communicate. Congress ultimately included a provision addressing reverse engineering for interoperability in section 1201(f) of the Act. ACIS and its allies also challenged other proposals they believed could restrict compatible development, including approaches to software licensing and database protection. Their advocacy reached international discussions as well, with ACIS supporting interoperability provisions in countries including Japan, Korea, and the Philippines.

A lasting connection to software innovation

The principles ACIS advanced remained relevant as software development changed. A compatible program can allow users to retain access to existing files or systems while choosing a new tool. It can let a smaller developer build on an established platform, or let a competitor offer a different implementation of a familiar function. Those possibilities help explain why disputes over interfaces concern more than the companies immediately involved: they affect how easily new software can enter an established computing environment.

The connection to open source is indirect. Open-source software developed through its own communities, projects, and licensing practices; ACIS was not its founder or representative. But open-source developers, like the companies ACIS represented, have needed to implement interfaces, exchange data with proprietary systems, and build compatible alternatives. The Open Source Initiative later made the importance of shared interfaces central to its arguments in Google v. Oracle. ACIS’s earlier filings belong to the history of the legal questions that those developers continued to face. Later briefs in the same dispute cited ACIS’s 1991 principles, although the Supreme Court decided the case on fair use grounds rather than resolving every question about the copyright status of interfaces.

ACIS’s legacy is therefore found in both its particular interventions and the durable question linking them. Its statements, correspondence, policy comments, and court briefs show how developers argued for the freedom to connect independent products to existing systems while preserving protection for original software. Its views were contested, and the law has not answered every interoperability question in the same way. Yet the problem ACIS identified remains familiar: innovation depends in part on whether the next developer can understand enough of an existing system to make something new that works with it.

Scope & Content

The collection documents ACIS's advocacy and organizational work. It includes amicus curiae briefs, minutes and notes of committee meetings, correspondence with members, allied organizations, and government offices, formal comments submitted in regulatory and standards proceedings, and reports, newsletters, and other organizational records.

Arrangement

The records are arranged in five series by material type.

Series	Title	Items

Access & Use

The collection is open for research. Digitized materials are made available for personal, educational, and research use. Permission from the Robert Crown Law Library is required to publish or reproduce materials for other purposes. For permission requests, please contact the library.

Citing Materials

Each item page provides a recommended citation in Chicago and Bluebook formats, along with a permanent URL (PURL) in the Stanford Digital Repository. Please cite the PURL rather than the address shown in your browser.

About This Site

The ACIS Digital Archive is developed by the Robert Crown Law Library at Stanford Law School. Digitized objects are preserved in the Stanford Digital Repository (SDR), and Ask the Archive is powered by an AI discovery tool that searches the collection and cites the items it draws on.