@TF Whelan Associates, Inc. v. Jaslow Dental Lab. 230 USPQ 481 (3rd Cir. 1986) @@@UP@

Court of Appeals, Third Circuit

Whelan Associates, Inc. v. Jaslow Dental Laboratory, Inc., et al.

No. 85-1358
Decided August 4,1986

Appeal from District Court for the Eastern District of Pennsylvania, VanArtsdalen, District Judge; 225 USPQ 156.

@Action by Whelan Associates, Inc., against J aslow Dental Laboratory, Inc., Dentcom, Inc., Edward Jaslow, Rand Jaslow, and Joseph M. Cerra, for copyright and trademark infringement and unfair competition. From judgment for plaintiff, defendants appeal. Affirmed.

Michael J. Mangan, Robert S. Bramson, Ronald E. Karam, and Schnader, Harrison, Segal & Lewis, all of Philadelphia, Penn., for appellants.

Joel S. Goldhammer and Seidel, Gonda, Gold-hammer & Abbott, both of Philadelphia, Penn., and Irwin S. Rubin and Rubin, Glickman & Steinberg, both of Souderton, Penn., for appellee.

Ronald J. Palenski, Morton David Goldberg, Richard Dannay, and Jo Recht, for amicus curiae, ADAPSO.

Before Gibbons, Becker, and Rosenn, Circuit Judges.
Becker, Circuit Judge.

@This appeal involves a computer program for the operation of a dental laboratory, and calls upon us to apply the principles underlying our venerable copyright laws to the relatively new field of computer technology to determine the scope of copyright protection of a computer program. More particularly, in this case of first impression in the courts of appeals, we must determine whether the structure (or sequence and organization)[1] of a computer program is protectible by copyright, or whether the protection of the copyright law extends only as far as the literal computer code. The district court found that the copyright law covered these non-literal elements of the program, and we agree. This conclusion in turn requires us to consider whether there was sufficient evidence of substantial similarity between the structures of the two programs at issue in this case to uphold the district court's finding of copyright infringement. Because we find that there was enough evidence, we affirm.


@Appellant Jaslow Dental Laboratory, Inc. (gJaslow Labh) is a Pennsylvania corporation in the business of manufacturing dental prosthetics and devices. Appellant Dentcom, Inc. (gDentcomh) is a Pennsylvania corporation in the business of developing and marketing computer programs for use by dental laboratories. Dentcom was formed out of the events that gave rise to this suit, and its history will be recounted below. Individual appellants Edward Jaslow and his son Rand Jaslow are officers and shareholders in both Jaslow Lab and Dentcom. Appellants were defendants in the district court. Plaintiff-appellee Whelan Associates, Inc. (gWhelan Associatesh) is also a Pennsylvania corporation, engaged in the business of developing and marketing custom computer programs.

@Jaslow Lab, like any other small- or medium-sized business of moderate complexity, has significant bookkeeping and administrative tasks. Each other for equipment must be registered and processed; inventory must be maintained; customer lists must be continually updated; invoicing, billing, and accounts receivable, must be dealt with. While many of these functions are common to all businesses, the nature of the dental prosthetics business apparently requires some variations on the basic theme.

@Although Rand Jaslow had not had extensive experience with computers, he believed that the business operations of Jaslow Lab could be made more efficient if they were computerized. In early 1978, he therefore bought a small personal computer and tried to teach himself how to program it so that it would be of use to Jaslow Lab. Although he wrote a program for the computer, he was ultimately not successful, limited by both his lack of expertise and the relatively small capacity of his particular computer.

@A few months later, stymied by his own lack of success but still confident that Jaslow Lab would profit from computerization, Rand Jaslow hired the Strohl Systems Group, Inc. (gStrohlh), a small corporation that developed custom-made software to develop a program that would on Jaslow Lab's new IBM Series One computer and take care of the lab's business needs. Jaslow Lab and Strohl entered into an agreement providing that Strohl would design a system for Jaslow Lab's needs and that after Strohl had installed the system Strohl could market it to other dental laboratories. Jaslow Lab would receive a 10% royalty on all such sales.[2] The person at Strohl responsible for the Jaslow Lab's account was Elaine Whelan, an experienced programmer who was an officer and half-owner of Strohl.

@Ms. Whelan's first step was to visit Jaslow Lab and interview Rand Jaslow and others to learn how the laboratory worked and what its needs were. She also visited other dental laboratories and interviewed people there, so that she would better understand the layout, work-flow, and administration of dental laboratories generally. After this education into the ways of dental laboratories - and Jaslow Lab, in particular - Ms. Whelan wrote a program called Dentalab for Jaslow Lab. Dentalab was written in a computer language known as EDL (Even Driven Language), so that it would work with IBM Series One machines. The program was completed and was operative at Jaslow Lab around March 1979.

@Presumably with an eye towards exploiting the economic potential of the Dentalab program, Ms. Whelan left Strohl in November, 1979, to form her own business, Whelan Associates, Inc., which acquired Strohl's interest in the Dentalab program. Shortly thereafter, Whelan Associates entered into negotiations with Jaslow Lab for Jaslow Lab to be Whelan Associates' sales representative for the Dentalab program. Whelan Associates and Jaslow Lab entered into an agreement on July 30, 1980, according to which Jaslow Lab agreed to use its gbest efforts and to act diligently in the marketing of the Dentalab package,h and Whelan Associates agreed to guse its best efforts and to act diligently to improve and augment the previously successfully designed Dentalab package.h App. at 1779. The agreement stated that Jaslow Lab would receive 35% of the gross price of any programs sold and 5% of the price of any modifications to the programs. The agreement was for one year and was then terminable by either party on thirty days' notice.

@The parties' business relationship worked successfully for two years.[3] During this time, as Rand Jaslow became more familiar with computer programming, he realized that because Dentalab was written in EDL it could not be used on computers that many of the smaller dental prosthetics firms were using, for which EDL had not been implemented. Sensing that there might be a market for a program that served essentially the same function as Dentalab but that could be used more widely, Rand Jaslow began in May or June of 1982 to develop in his spare time a program in the BASIC language for such computers. That program, when completed, became the alleged copyright infringer in this suit; it was called the Dentcom PC program (gDentcom programh).4

@It appears that Rand Jaslow was sanguine about the prospects of his program for smaller computers. After approximately a year of work, on May 31, 1983, his attorney sent a letter to Whelan Associates giving one month notice of termination of the agreement between Whelan Associates and Jaslow Lab.[5] The letter stated that Jaslow Lab considered itself to be the exclusive marketer of the Dentalab program which, the letter dated, gcontains valuable trade secrets of Jaslow Dental Laboratory.h The letter concluded with a thinly veiled threat to Whelan Associates: gI... look for your immediate response confirming that you will respect the rights of Jaslow and not use or disclose to others the trade secrets of Jaslow.h App. at 1221.

@Approximately two months later, on about August 1, Edward and Rand Jaslow, Paul Mohr, and Joseph Cerra formed defendant-appellant Dentcom to sell the Dentcom program.[6] At about the same time, Rand Jaslow and Jaslow Lab employed a professional computer programmer, Jonathan Novak, to complete the Dentcom program. The program was soon finished, and Dentcom proceeded to sell it to dental prosthetics companies that had personal computers. Dentcom sold both the Dentalab and Dentcom programs, and advertised the Dentcom program as ga new version of the Dentlab computer system.h App. at 178: 1766 - 69; 1567 - 73.

@Despite Jaslow Lab's May 31 letter warning Whelan Associates not to sell the Dentalab program, Whelan Associates continued to market Dentalab. This precipitated the present litigation.


@On June 30, 1983, Jaslow Lab filed suit in the Court of Common Pleas of Montgomery County (Pennsylvania), alleging that Whelan Associates had misappropriated its trade secrets. Whelan Associates responded by filing the instant suit in the United States District Court for the Eastern District of Pennsylvania on September 21, 1983. As set forth in its amended complaint, Whelan Associates alleged that Dentcom's licensing of the Dentalab and Dentcom programs infringed Whelan Associates' copyright in Dentalab, App. at 452-53; that Dentcom' s use of the terms gDentlabh or gDentalab,h violated Pennsylvania common law and 15 U.S.C. 1125(a) (Lanham Trademark Act of 1946) (false designation of origin), App. at 454-57; and that Dentcom's activities violated various other federal and state laws pertaining to unfair competition and tortious interference with contractual relations, App. at 457-63. Whelan Associates sought injunctive relief, as well as compensatory and punitive damages. App. at 464-69.

@Jaslow Lab and its co-defendants answered, denying all liability. They claimed that Whelan Associates' copyright was invalid for two reasons. First, they said that although he had not been listed in the copyright registration, Rand Jaslow had been a co-author (with Elaine Whelan) of the Dentalab program. The omission of Rand Jaslow from the registration form, defendants averred, rendered the copyright defective. App. at 506-09. Second, the defendants maintained that even if Rand Jaslow had not co-authored the program, he owned the copyright because the program had been written by someone employed by him. App. at 507. Defendants also averred that Rand Jaslow had developed the Dentcom system independently, and therefore could not have violated Whelan Associate's copyright, even if the copyright were valid.[7] Finally, defendants claimed that their use of gDentalabh or gDentlabh violated neither federal nor state law, for, inter alia those terms are merely general descriptions of goods and services, not names of particular products. App. at 504. Defendants counterclaimed that Whelan Associates had usurped defendants' copyright and that by continuing to sell Dentalab, Whelan Associates was engaging in unfair competition. App. at 505-11. By agreement of the parties, the trade secret action was removed from the Court of Common Pleas to the district court and became a counterclaim. App. at 509-12.

@The first procedural blow was struck by the defendants, who moved almost immediately for a preliminary injunction to enjoin Whelan Associates from using Jaslow Labs' trade secrets. After a three-day hearing, the district court denied the motion in a bench opinion delivered on November 2, 1983. The court held that the defendants had not shown a likelihood of success on the merits because they had failed to prove that any of Jaslow Lab's trade secrets were in the Dentalab program. Moreover, the court held that the defendants had not proven irreparable harm and that they had approached the court with gunclean hands~~ on account of their use of the term gDentlab,h which could be and was confused for Dentalab. App. 443-44; 446-47.

@A quick victory proving beyond the defendants' reach, the parties prepared for a protracted battle. Discovery proceeded on each side, and a three-day bench trial began on July 9,1984. At trial, Whelan Associates continued to press all of its claims - copyright violations, unfair competition, and tortious interference with contractual relations. The defendants abandoned the trade secret claim that had failed them in the preliminary injunction battle, but maintained their position that Rand Jaslow owned the copyright to Dentalab. Defendants continued to deny Whelan Associates' allegations.

@The principal witnesses were Elaine Whelan, Rand Jaslow, and two expert witnesses, Dr. Thomas Moore for Whelan Associates and Stephen Ness on behalf of the defendants. Whelan and Jaslow testified about the dealings and negotiations between the parties. Dr. Moore and Mr. Ness examined the programs and testified about the programs' similarities and differences. Dr. Moore testified that although the Dentcom program was not a translation of the Dentalab system, the programs were similar in three significant respects. He testified that most of the file structures, and the screen outputs, of the programs were virtually identical. App. at 682-704 (file structures); id. at 681-82 (screen outputs). He also testified that five particularly important gsubroutinesh within both programs - order entry, invoicing, accounts receivable, end of day procedure, and end of month procedure - performed almost identically in both programs. App. at 7O4~18.[8]@Mr. Ness compared the source and object codes[9] of the Dentalab, Dentcom, and Datamaster programs, see supra n.4, and testified at length about the many ways that the programs differed from one another. He concluded that gsubstantive differences in programming style, in programming structure, in algorithms and data structures, all indicate that the Dentcom system is not directly derived from either of the other systems.h App. at 823-24. In his written report, however, which was entered into evidence, Mr. Ness conceded that the Dentalab and Dentcom programs had goverall structural similarities.h App. at 1798.

@The district court ruled for Whelan Associates on all grounds. Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. 1307, 225 USPQ 156 (E.D. Pa. 1985). It found that Elaine Whelan was the sole author of the Dentalab system (and, hence, that Rand Jaslow was not a co-author) and that the contract between Strohl and Rand Jaslow, see supra n.2, made clear that Strohl would retain full ownership over the software. Whelan Assoczates v. Jaslow Dental Laboratory, 609 F.Supp. at 1318-19, 225 USPQ at 164-65. The court thus concluded that Whelan Associates' copyright in the Dentalab System was valid, and that Dentcom's sales of the Dentalab program were violations of that copyright.[10] Id. at 1320, 225 USPQ at 165-66.

@The court also found that Rand Jaslow had not created the Dentcom system independently, and that the Dentcom system, although written in a different computer language from the Dentalab, and although not a direct transliteration of Dentalab, was substantially similar to Dentalab because its structure and overall organization were substantially similar. Id. at 1321-22. (The district court's opinion on this point is described infra). This substantial similarity, in conjunction with Rand Jaslow's acknowledged access to the Dentalab system, led the district court to conclude that each sale of the Dentcom program by Dentcom[11] violated Whelan Associates' copyright on the Dentalab system. The court therefore awarded Whelan Associates damages for these copyright infringements, and enjoined Dentcom from selling any more copies of the Dentalab or Dentcom programs. Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. at 1322-23, 225 USPQ at 167-68. The court also held that plaintiffs had exclusive use of the term gDentalab,h and enjoined defendants from using either gDentalabh or gDentlabh in their business. Id. at 1324-25, 225 USPQ at 169.

@The parties filed a series of post-trial motions, primarily concerned with damage calculations and attorneys fees. Upon the district court's disposition of these motions, Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. 1325, 225 USPQ 169 (E.D. Pa. 1985), the defendants filed their notices of appeal.[12] On appeal, they raise a single issue: whether the district court erred in its finding that the Dentcom program infringes the copyright of plaintiffs' Dentalab system.


@We begin with a brief description of computer programs and an explanation of how they are written. This introduction is necessary to our analysis of the issues in this case.

@A computer program is a set of instructions to the computer.[13]@Most programs accept and process user-supplied data. The fundamental processes utilized by a program are called algorithms (mechanical computational procedures) and are at the heart of the program. See Keplinger, Computer Software - Its Nature and its Protection, 30 Emory L. J. 483, 484-85 (1984). These algorithms must be developed by the human creativity of the programmer, and the program therefore cannot contain any algorithms not already considered by humans. Although a computer cannot think or develop algorithms, it can execute them faster and more accurately than any human possibly could. See R. Saltman, Copyright in Computer-Readable Works 59 (1977).

@The creation of a program often takes place in several steps, moving from the general to the specific.[14] Because programs are intended to accomplish particular tasks, the first step in creating the program is identifying the problem that the computer programmer is trying to solve. In this case, Rand Jaslow went to Strohl and stated that his problem was recordkeeping for his business. Although this was an accurate statement of the problem, it was not specific enough to guide Elaine Whelan. Before she could write the Dentalab program, she needed to know more about Jaslow Lab's business -how orders were processed, what special billing problems might arise, how inventory might be correlated to orders, and other characteristics of the dental prosthetics trade.

@As the programmer learns more about the problem, she or he may begin to outline a solution. The outline can take the form of a flowchart, which will break down the solution into a series of smaller units called gsubroutinesh or gmodules,h[15] each of which deals with elements of the larger problem. See Note, Defining the Scope of Copyright Protection for Computer Software, 38 Stan.L.Rev. 497, 500-01 (1986). A program's efficiency depends in large part on the arrangements of its modules and subroutines; although two programs could produce the same result, one might be more efficient because of different internal arrangements of modules and subroutines. Because efficiency is a prime concern in computer programs (an efficient program being obviously more valuable than a comparatively inefficient one), the arrangement of modules and subroutines is a critical factor for any programmer. In the present case, the Dentalab program had numerous modules pertaining to inventory, accounts receivable, various dentist-patient matters, and payroll, among others. See App. at 1588-1698 (showing flowcharts of subroutines). Some of the modules were simple; others were quite complex and involved fairly elaborate logical development.

@As the program structure is refined, the programmer must make decisions about what data is needed, where along the program's operations the data should be introduced, how the data should be inputted, and how it should be combined with other data. The arrangement of the data is accomplished by means of data files, discussed infra, and is affected by the details of the program's subroutines and modules, for different arrangements of subroutines and modules may require data in different forms. Once again, there are numerous ways the programmer can solve the data-organization problems she or he faces. Each solution may have particular characteristics - efficiencies or inefficiencies, conveniences or quirks -that differentiate it from other solutions and make the overall program more or less desirable. Because the Dentalab program was intended to handle all of the business-related aspects of a dental laboratory, it had to accommodate and interrelate many different pieces and types of data including patients' names, dentists' names, inventory, accounts receivable, accounts payable, and payroll.[16]

@Once the detailed design of the program is completed, the coding begins.[17]@Each of the steps identified in the design must be turned into a language that the computer can understand. This translation process in itself requires two steps. The programmer first writes in a gsource code,h which may be in one of several languages, such as COBOL, BASIC, FORTRAN, or EDL.[18] The choice of language depends upon which computers the programmer intends the program to be used by, for some computers can read only certain languages.[19] Once the program is written in source code, it is translated into "object code," which is a binary code, simply a concatenation of "O" 's and "1" 's. In every program, it is the object code, not the source code, that directs the computer to perform functions.

@The object code is therefore the final instruction to the computer.[20][21]

@As this brief summary demonstrates, the coding process is a comparatively small part of programming. By far the larger portion of the expense and difficulty in creating computer programs is attributable to the development of the structure and logic of the program, and to debugging, documentation and maintenance, rather than to the coding. See Frank, Critical Issues in Software 22 (1983) (only 20% of the cost of program development goes into coding); Zelkowitz, Perspective on Software Engineering, 10 Computing Surveys 197-216 (June, 1978). See also Info World, Nov. II, 1985 at 13 (gthe 'look and feel' of a computer software product often involves much more creativity and often is of greater commercial value than the program code which implements the product. . . .g). The evidence in this case is that Ms. Whelan spent a tremendous amount of time studying Jaslow Labs, organizing the modules and subroutines for the Dentalab program, and working out the data arrangements, and a comparatively small amount of time actually coding the Dentalab program.


@A. The elements of a copyright infringement action - To prove that its copyright has been infringed, Whelan Associates must show two things: that it owned the copyright on Dentalab, and that Rand Jaslow copied Dentalab in making the Dentacom program. Sid & Marty Krofft Television Prods., Inc. v. McDonald's Corp., 562 F.2d 1157, 1162, 196 USPQ 97, 100 (9th Cir. 1977); Reyher v. Children's Television Workshop, 533 F.2d 87, 90, 190 USPQ 387, 389 (2d Cir.), cert. denied, 429 U.S. 980, 192 USPQ 64 (1976); 3 Nimmer On Copyright 13.01 (1985) [referred to hereinafter as gNimmerh]. Although it was disputed below, see supra, the district court determined, and it is not challenged here, that Whelan Associates owned the copyright to the Dentalab program. We are thus concerned only with whether it has been shown that Rand Jaslow copied the Dentalab program.

@As it is rarely possible to prove copying through direct evidence, Roth Greeting Cards v. United Card Co., 429 F.2d 1106, 1110, 166 USPQ 291, 294 (9th Cir. 1970), copying may be proved inferentially by showing that the defendant had access to the allegedly infringed copyrighted work and that the allegedly infringing work is substantially similar to the copyrighted work. Ferguson v. iVational Broadcasting Co., 584 F.2d 111, 113, 200 USPQ 65 (5th Cir. 1978); Sid & A'Iarty Krofft Television Prods. Inc., supra; Universal Athletic Sales Co. v. Salkeld, 511 F.2d 904, 907, 185 USPQ 76, 77 (3d Cir.), cert. denied, 423 U.S. 863 (1975); Midway Mfg, Co. v. Strohon, 564 F.Supp. 741, 753, 219 USPQ 42, 52 (N.D. Ill. 1983). The district court found, and there it is uncontested that Rand Jaslow had access to the Dentalab program, both because Dentalab was the program used in Jaslow Labs and because Rand Jaslow acted as sales representative for Whelan Associates. See Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. at 1314, 225 USPQ at 161.[22] Thus, the sole question is whether there was substantial similarity between the Dentcom and Dentalab programs.[23]

@B. The appropriate test for substantial similarity in computer program cases - The leading case of Arnstein v. Porter, 154 F.2d 464, 468-69, 68 USPQ 288, 292-93 (2d Cir. 1946), suggested a bifurcated substantial similarity test whereby a finder of fact makes two findings of substantial similarity to support a copyright violation. First, the fact-finder must decide whether there is sufficient similarity between the two works in question to conclude that the alleged infringer used the copyrighted work in making his own. On this issue expert testimony may be received to aid the trier of fact. (This is called the gextrinsich test of substantial similarity. Sid & Marty Krofft Television Prods., Inc. v. McDonald's Corp., 562 F.2d at 1164-65, 196 USPQ at 102-03.) Second, if the answer to the first question is in the affirmative, the fact-finder must decide without the aid of expert testimony, but with the perspective of the glay observer,h whether the copying was gillicit,h or gan unlawful appropriationh of the copyrighted work. (This is called an gintrinsich test of substantial similarity. Id.) The Arnstein test has been adopted in this circuit. See Universal Athletic Sales Co., 511 F.2d at 907, 185 USPQat 78.

@The district court heard expert testimony. See supra 12-13; infra at 58-62. It did not bifurcate its analysis, however, but made only a single finding of substantial similarity. See Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. at 1321-22, 225 USPQ at 166-67. It would thus appear to have contravened the law of this circuit. Nevertheless, for the reasons that follow, we believe that the district court applied an appropriate standard.

@[1] The ordinary observer test, which was developed in cases involving novels, plays, and paintings, and which does not permit expert testimony, is of doubtful value in cases involving computer programs on account of the programs' complexity and unfamiliarity to most members of the public. See Note, Copyright Infringement of Computer Programs: A Modification of the Substantial Similarity Test, 68 Minn. L. Rev. 1264, 1285-88 (1984). Cf Note, Copyright Infringement Actions: The Proper Role for Audience Reactions in Determining Substantial Similarity, 54 S.Cal. L. Rev. 385 (1981) (criticizing lay observer standard when objects in question are intended for particular, identifiable audiences). Moreover, the distinction between the two parts of the Arnstein test may be of doubtful value when the finder of fact is the same person for each step: that person has been exposed to expert evidence in the first step, yet she or he is supposed to ignore or gforgeth that evidence in analyzing the problem under the second step. Especially in complex cases, we doubt that the gforgettingh can be effective when the expert testimony is essential to even the most fundamental understanding of the objects in question.

@On account of these problems with the standard, we believe that the ordinary observer test is not useful and is potentially misleading when the subjects of the copyright are particularly complex, such as computer programs. We therefore join the growing number of courts which do not apply the ordinary observer test in copyright cases involving exceptionally difficult materials, like computer programs, but instead adopt a single substantial similarity inquiry according to which both lay and expert testimony would be admissible. See E.F. Johnson Co. v. Uniden Corp., 623 F.Supp. 1485, 1493, 228 USPQ 891, 896 (D.Minn. 1985); Hubco Data Products Corp. v. Management Assistance Inc., 2 Copyright L. Rep. (CCH) 25.529 (D. Idaho Feb. 3, 1983) (enunciating bifurcated test, but relying entirely on expert testimony); Midway Mfg. Co. v. Strohon, 564 F.Supp. 741, 752-53, 219 USPQ 42, 51-52 (N.D. Ill. 1983) (relying entirely on expert testimony to find substantial similarity); see also Fed. R. Evid. 702 (gIf [expert testimony] will assist the trier of fact to understand the evidence or to determine a fact in issue, a witness . . . may testify thereto in the form of an opinion or otherwise.h). That was the test applied by the district court in this case.24

@C. The arguments on appeal - On appeal, the defendants attack on two grounds the district court's holding that there was sufficient evidence of substantial similarity. First, the defendants argue that because the district court did not find any similarity between the gliteralh elements (source and object code) of the programs, but only similarity in their overall structures, its finding of substantial similarity was incorrect, for the copyright covers only the literal elements of computer programs, not their overall structures. Defendants' second argument is that even if the protection of copyright law extends to gnon-literalh elements such as the structure of computer programs, there was not sufficient evidence of substantial similarity to sustain the district court's holding in this case. We consider these arguments in turn.25


@It is well, though recently, established that copyright protection extends to a program's source and object codes. Stern Elecs., Inc. v. Kaufman, 669 F.2d 852, 855 n.3, 213 USPQ 443, 444 n.3 (2d Cir. 1982) (source code); Apple Computer, Inc. v. Franklin Computer Corp., 714 F.2d 1240, 1246-47, 219 USPQ 113, 118-19 (3d Cir. 1983) (source and object code), cert. dismissed, 464 U.S. 1033 (1984); Williams Elecs., Inc. v Artic International, Inc., 685 F.2d 870, 215 USPQ 405 (3d Cir. 1982) (object code). 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. Rather, the district court held that the Dentalab copyright was infringed because the overall structure of Dentcom was substantially similar to the overall structure of Dentalab. Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. at 1321-22, 225 USPQ at 166-67. The question therefore arises whether mere similarity in the overall structure of programs can be the basis for a copyright infringement, or, put differently, whether a program's copyright protection covers the structure of the program or only the program's literal elements, i.e., its source and object codes.

@Title 17 U.S.C. 102(a)(1) extends copyright protection to gliterary works,h and computer programs are classified as literary works for the purposes of copyright. See H.R. Rep.No. 1476, 94th Cong., 2d Sess. 54, reprinted in 1976 U.S. Code Cong. & Ad. News 5659, 5667. The copyrights of other literary works can be infringed even when there is no substantial similarity between the works' literal elements. One can violate the copyright of a play or book by copying its plot or plot devices. See, e.g., Twentieth Century-Fox Film Corp. v. MCA, Inc., 715 F.2d 1327, 1329, 217 USPQ 611, 612 (9th Cir. 1983) (13 alleged distinctive plot similarities between Battlestar Galactica and Star Wars may be basis for a finding of copyright violation); Sid & Marty Krofft Television Productions, Inc., 562 F.2d at 1167, 196 USPQ at 104 (similarities between McDonaldland characters and H.R. Pufnstuf characters can be established by " 'total concept and feel' " of the two productions (quoting Roth Greeting Cards v. United Card Co., 429 F.2d 1106, 1110, 166 USPQ 291, 294 (9th Cir. 1970)); Sheldon v. Metro-Goldwyn Pictures Corp., 81 F.2d 49, 54-55, 28 USPQ 330, 335-36 (1936); Nichols v. Universal Pictures Corp., 45 F.2d 119, 121,7 USPQ 84,96 (2d Cir. 1930) (copyright gcannot be limited literally to the text, else a plagiarist would escape by immaterial variationsh). By analogy to other literary works, it would thus appear that the copyrights of computer programs can be infringed even absent copying of the literal elements of the program.26 Defendants contend, however, that what is true of other literary works is not true of computer programs. They assert two principal reasons, which we consider in turn.

@A. Section 102(b) and the dichotomy between idea and expression - It is axiomatic that copyright does not protect ideas, but only expressions of ideas. This rule, first enunciated in Baker v. Selden, 101 U.S. 99 (1879), has been repeated in numerous cases. See, e.g., Mazerv. Stein, 347 U.S. 201, 217, 100 USPQ 325, 332 (1954) (gUnlike a patent, a copyright gives no exclusive right to the art disclosed; protection is given only to the expression of the idea - not the idea itself.h [citation omitted] ); Universal Athletic Sales Co., 511 F.2d at 906, 185 USPQ at 78; Dymow v. Bolton, 11 F.2d 690, 691 (2d Cir. 1926); see generally A. Latman, The Copyright Law 31-35 (5th ed. 1979); 1 Nimmer 2.03[D]. The rule has also been embodied in statute. Title 17 U.S.C. 102(b) (1982) states:

  In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.
  The legislative history of this section, adopted in 1976, makes clear that 102(b) was intended to express the idea-expression dichotomy. See H.R. Rep. No. 1476 at 57 reprinted in 1976 U.S. Code Cong. & Ad. News at 5670 (102(b) is intended to grestate ... that the basic dichotomy between expression and idea remains unchanged.h) See also Apple Coin puter,supra, 714 F.2d at 1252, 219 USPQ at 123.

@Defendants argue that the structure of a computer program is, by definition, the idea and not the expression of the idea, and therefore that the structure cannot be protected by the program copyright. Under the defendants' approach, any other decision would be contrary to 102(b). We divide our consideration of this argument into two parts. First, we examine the caselaw concerning the distinction between idea and expression, and derive from it a rule for distinguishing idea from expression in the context of computer programs. We then apply that rule to the facts of this case.

@1. A rule for distinguishing idea from expression in computer programs - It is frequently difficult to distinguish the idea from the expression thererof. No less an authority than Learned Hand, after a career that included writing some of the leading copyright opinions, concluded that the distinction will ginevitably be ad hoc.h Peter Pan Fabrics, Inc. v. Martin Weiner Corp., 274 F.2d 487, 489, 124 USPQ 154, 155 (2d Cir. 1960). See also Knowles & Palmieri, Dissecting Krofft: An Expression of New Ideas in Copyright?, [8] San. Fern. Val. L. Rev. 109, 126 (1980) (arguing that there can be no meaningful distinction between idea and expression). Although we acknowledge the wisdom of Judge Hand's remark, we feel that a review of relevant copyright precedent will enable us to formulate a rule applicable in this case. In addition, precisely because the line between idea and expression is elusive, we must pay particular attention to the pragmatic considerations that underlie the distinction and copyright law generally. In this regard, we must remember that the purpose of the copyright law is to create the most efficient and productive balance between protection (incentive) and dissemination of information, to promote learning, culture and development. See U.S. Const. Art. 1 8 cl. 8 [Copyright Clause] (giving Congress the power to gpromote the Progress of Science and useful Artsh).27

@We begin our analysis with the case of Baker v. Selden, which, in addition to being a seminal case in the law of copyright generally, is particularly relevant here because, like the instant case, it involved a utilitarian work, rather than an artistic or fictional one. In Baker v. Selden, the plaintiff Selden obtained a copyright on his book, gSelden's Condensed Ledger, or Bookkeeping Simplified,h which described a new, simplified system of accounting. Included in the book were certain gblank forms,h pages with ruled lines and headings, for use in Selden's accounting system. Selden alleged that Baker had infringed Selden's copyright by making and selling accounting books that used substantially the same system as Selden's and that reproduced Selden's blank forms. No one disputed that Baker had the right to use and promulgate Selden's system of accounting, for all parties agreed that the system could not be copyrighted, although the Court opined that it might be patentable. Id. at 102. Nor did the parties dispute that the text of Baker's book on accounting did not infringe Selden's copyright. The dispute centered on whether Selden's blank forms were part of the method (idea) of Selden's book, and hence non-copyrightable, or part of the copyrightable text (expression). Id. at 101.

@In deciding this point, the Court distinguished what was protectible from what was not protectible as follows:

[W]here the art [i.e., the method of accounting] it teaches cannot be used without employing the methods and diagrams used to illustrate the book, or such as are similar to them, such methods and diagrams are to be considered as necessary incidents to the art, and given to the public.
Id. at 103. Applying this test, the Court held that the blank forms were necessary incidents to Selden's method of accounting, and hence were not entitled to any copyright protection. Id. at 104.

@The Court's test in Baker v. Selden suggests a way to distinguish idea from expression. Just as Baker v. Selden focused on the end sought to be achieved by Selden's book, the line between idea and expression may be drawn with reference to the end sought to be achieved by the work in question. In other words, the purpose or function of a utilitarian work would be the work's idea, and everything that is not necessary to that purpose or function would be part of the expression of the idea. Cf Apple Computer, Inc. v. Formula Int'l Inc., 562 F.Supp. 775, 783, 218 USPQ 47, 53 (C.D. Ca. 1983] [gApple seeks here not to protect ideas (i.e. making the machine perform particular functions) but rather to protect their particular expressions . . .g], affd. 725 F.2d 521, 221 USPQ 762 (9th Cir. 1984). Where there are various means of achieving the desired purpose, then the particular means chosen is not necessary to the purpose; hence, there is expression, not idea.28

@Consideration of copyright doctrines related to scenes a faire and fact-intensive works supports our formulation, for they reflect the same underlying principle. Scenes a faire are gincidents, characters or settings which are as a practical matter indispensable . . . in the treatment of a given topic.h Atari, Inc. v. North American Philips Consumer Elecs. Corp., 672 F.2d 607, 616, 214 USPQ 33, 40 (7th Cir.), cert. denied, 459 U.S. 880 (1982). See also See v. Durang, 711 F.2d 141,143,219 USPQ 771, 772 (9th Cir. 1983). It is well-settled doctrine that scenes a faire are afforded no copyright protection.29

@Scenes a faire are afforded no protection because the subject matter represented can be expressed in no other way than through the particular scene a faire. Therefore, granting a copyright gwould give the first author a monopoly on the commonplace ideas behind the scenes a faire.h Landsberg v. Scrabble Crossword Game Playe+s, Inc., 736 F.2d at 489, 221 USPQ at 1143.30 This is merely a restatement of the hypothesis advanced above, that the purpose or function of a work or literary device is part of that device's gideah (unprotectible portion). It follows that anything necessary to effecting that function is also, necessarily, part of the idea, too.

@Fact intensive works are given similarly limited copyright coverage. See, e.g., Lands-berg, 736 F.2d at 488, 221 USPQ at 1142; Miller v. Universal City Studios, Inc., 650 F.2d 1365, 1372, 212 USPQ 345, 350 [5th Cir. 1981]. Once again, the reason appears to be that there are only a limited number of ways to express factual material, and therefore the purpose of the literary work - telling a truthful story - can be accomplished only by employing one of a limited number of devices. Landsberg, 736 F.2d at 488, 221 USPQ at 1142. Those devices therefore belong to the idea, not the expression, of the historical or factual work.

@Although the economic implications of this rule are necessarily somewhat speculative, we nevertheless believe that the rule would advance the basic purpose underlying the idea/expression distinction, gthe preservation of the balance between competition and protection reflected in the patent and copyright laws.h Herbert Rosenthal Jewelry Corp. v. Kalpakian, 446 F.2d 738, 742, 170 USPQ 557, 559 (9th Cir. 1971); see also Apple Computer, 714 F.2d at 1253, 219 USPQ at 123 [quoting Kalpakian); supra n. 27. As we stated above, see supra at 21, among the more significant costs in computer programming are those attributable to developing the structure and logic of the program. The rule proposed here, which allows copyright protection beyond the literal computer code,31 would provide the proper incentive for programmers by protecting their most valuable efforts, while not giving them a stranglehold over the development of new computer devices that accomplish the same end.

@The principal economic argument used against this position - used, that is, in support of the position that programs' literal elements are the only parts of the programs protected by the copyright law - is that computer programs are so intricate, each step so dependent on all of the other steps, that they are almost impossible to copy except literally, and that anyone who attempts to copy the structure of a program without copying its literal elements must expend a tremendous amount of effort and creativity. In the words of one commentator: gOne cannot simply 'approximate' the entire copyrighted computer program and create a similar operative program without the expenditure of almost the same amount of time as the original programmer expended." Note 68 Minn. L. Rev, at 1290 (footnote omitted). According to this argument, such work should not be discouraged or penalized. A further argument against our position is not economic but jurisprudential; another commentator argues that the concept of structure in computer programs is too vague to be useful in copyright cases. Radcliffe, Recent Developments in Copyright Law Related to Computer Software, [4] Computer L. Rep. 189, 194-97 (1985). He too would therefore appear to advocate limiting copyright protection to programs' literal codes.

@Neither of the two arguments just described is persuasive. The first argument fails for two reasons. In the first place, it is simply not true that gapproximationh of a program short of perfect reproduction is valueless. To the contrary, one can approximate a program and thereby gain a significant advantage over competitors even though additional work is needed to complete the program. Second, the fact that it will take a great deal of effort to copy a copyrighted work does not mean that the copier is not a copyright infringer. The issue in a copyrighted case is simply whether the copyright holder's expression has been copied, not how difficult it was to do the copying. Whether an alleged infringer spent significant time and effort to copy an original work is therefore irrelevant to whether he has pirated the expression of an original work.32

@As to the second argument, it is surely true that limiting copyright protection to computers' literal codes would be simpler and would yield more definite answers than does our answer here. Ease of application is not, however, a sufficient counterweight to the considerations we have adduced on behalf of our position.

@Finally, one commentator argues that the process of development and progress in the field of computer programming is significantly different from that in other fields, and therefore requires a particularly restricted application of the copyright law. According to this argument, progress in the area of computer technology is achieved by means of gsteppingstones,h a process that grequires plagiarizing in some manner the underlying copyrighted work.h Note, 68 Minn. L. Rev, at 1292 [footnote omitted]. As a consequence, this commentator argues, giving computer programs too much copyright protection will retard progress in the field.

@We are not convinced that progress in computer technology or technique is qualitatively different from progress in other areas of science or the arts. In balancing protection and dissemination, see supra at 31 & n. 27, the copyright law has always recognized and tried to accommodate the fact that all intellectual pioneers build on the work of their predecessors. 33 Thus, copyright principles derived from other areas are applicable in the field of computer programs.

@2. Application of the general rule to this case- The rule proposed here is certainly not problem-free. The rule has its greatest force in the analysis of utilitarian or gfunctionalh works, for the purpose of such works is easily stated and identified. By contrast, in cases involving works of literature or gnon-functionalh visual representations, defining the purpose of the work may be difficult. Since it may be impossible to discuss the purpose or function of a novel, poem, sculpture or painting, the rule may have little or no application to cases involving such works. The present case presents no such difficulties, for it is clear that the purpose of the utilitarian Dentalab program was to aid in the business operations of a dental laboratory.34 See supra 4-5. It is equally clear that the structure of the program was not essential to that task: there are other programs on the market, competitors of Dentalab and Dentcom, that perform the same functions but have different structures and designs.

@This fact seems to have been dispositive for the district court:

The mere idea or concept of a computerized program for operating a dental laboratory would not in and of itself be subject to copyright. Copyright law protects the manner in which the author expresses an idea or concept, but not the idea itself. Albert E. Price v. Metzner, 574 F.Supp. 281, 219 USPQ 1092 (E.D. Pa. 1983). Copyrights do not protect ideas - only expressions of ideas. Universal Athletic Sales Co. v. Salkeld, 511 F.2d 904, 908, 185 USPQ 76, 78 (3d Cir. 1975). There are many ways that the same data may be organized, assembled, held, retrieved and utilized by a computer. Different computer systems may functionally serve similar purposes without being copies of each other. There is evidence in the record that there are other software programs for the business management of dental laboratories in competition with plaintiff's program. There is no contention that any of them infringe although they may incorporate many of the same ideas and functions. The eexpression of the idea' in a software computer program is the manner in which the program operates, controls and regulates the computer in receiving, assembling, calculating, retaining, correlating, and producing information either on a screen, print-out or by audio communication.
Whelan Associates v. Jaslow Laboratory, 609 F.Supp. at 1320, 225 USPQ at 165 (emphasis added). We agree. The conclusion is thus inescapable that the detailed structure of the Dentalab program is part of the expression, not the idea, of that program.

@Our conclusion is supported by SAS Institute, Inc. v. S&H Computer Systems, Inc., 605 F.Supp. 816, 225 USPQ 916 (M.D. Tenn. 1985), the only other case that has addressed this issue specifically, in which the court found that a program's copyright could extend beyond its literal elements to its structure and organization. In SAS, plaintiffs supported their allegation of copyright infringement of their computer program with evidence of both literal and organizational similarities between its program and the alleged infringer. Id. at 822, 825-26, 225 USPQ at 919, 922-23. The court found a copyright infringement, and although it did not discuss in detail its evaluation of the evidence, it is apparent that the organizational similarities of the programs were relevant to its decision. After a brief discussion of the programs' literal similarities, the court said:

@In addition, the copying proven at trial does not affect only the specific lines of code cited by Dr. Peterson in his testimony. Rather, to the extent that it represents copying of the organization and structural details of SAS, such copying pervades the entire S&H product.
Id. at 830, 225 USPQ at 926. Although the SAS court did not analyze the point in great depth, we are encouraged by its conclusion.

@The Copyright Act of 1976 provides further support, for it indicates that Congress intended that the structure and organization of a literary work could be part of its expression protectible by copyright. Title 17 U.S.C. 103 (1982) specifically extends copyright protection to compilations and derivative works. Title 17 U.S.C. 101, defines gcompilationh as ga work formed by the collection and assembling of preexisting materials or of data that are selected, coordinated, or arranged in such a way that the resulting work as a whole constitutes an original work of authorship,h and it defines gderivative work,h as one gbased upon one or more preexisting works, such as ... abridgement, condensation, or any other form in which a work may be recast, transformed, or adapted.h (emphasis added). Although the Code does not use the terms gsequence,h gorderh or gstructure,h it is clear from the definition of compilations and derivative works, and the protection afforded them, that Congress was aware of the fact that the sequencing and ordering of materials could be copyrighted, i.e., that the sequence and order could be parts of the expression, not the idea, of a work.

@Our solution may put us at odds with Judge Patrick Higginbotham's scholarly opinion in Synercom Technology, Inc. v. University Computing Co., 462 F.Supp. 1003,199 USPQ 537 (N.D. Tex. 1978), which dealt with the question whether the ginput formatsh of a computer program - the configurations and collations of the information entered into the program - were idea or expression. The court held that the input formats were ideas, not expressions, and thus not protectible. Synercom did not deal with precisely the materials at issue here - input formats are structurally simple as compared to full programs - and it may therefore be distinguishable. However, insofar as the input formats are devices for the organization of data into forms useful for computers, they are similar to programs; thus, Synercom is relevant and we must come to grips with it.

@Central to Judge Higginbotham's analysis was his conviction that the organization and structure of the input formats was inseparable from the idea underlying the formats. Although the court acknowledged that in some cases structure and sequence might be part of expression, not idea, see id. at 1014, 199 USPQ at 547, it stated that in the case of input formats, structure and organization were inherently part of the idea. The court put its position in the form of a powerful rhetorical question: gif sequencing and ordering [are] expression, what separable idea is being expressed?h Id. at 1013, 199 USPQ at 546.

@To the extent that Synercom rested on the premise that there was a difference between the copyrightability of sequence and form in the computer context and in any other context, we think that it is incorrect. As just noted, the Copyright Act of 1976 demonstrates that Congress intended sequencing and ordering to be protectible in the appropriate circumstances, see supra, and the computer field is not an exception to this general rule. Although Congress was aware that computer programs posed a novel set of issues and problems for the copyright law, Congress did not then make, and has not since made, any special provision for ordering and sequencing in the context of computer programs. There is thus no statutory basis for treating computer programs differently from other literary works in this regard.35

@Despite the fact that copyright protection extends to sequence and form in the computer context, unless we are able to answer Judge Higginbotham's powerful rhetorical question - "if sequencing and ordering [are] expression, what separable idea is being expressed?"- in our own case, we would have to hold that the structure of the Dentalab program is part of its idea and is thus not protectible by copyright. Our answer has already been given, however: the idea is the efficient organization of a dental laboratory (presumably, this poses different problems from the efficient organization of some other kinds of laboratories or businesses). Because there are a variety of program structures through which that idea can be expressed, the structure is not a necessary incident to that idea. 36 See supra 39.

@B. The CONTU Report - Defendants' second argument against copyright protection for non-literal elements of computer programs relies not on venerable principles of copyright law, but on the report of a special congressional commission. In 1974, concerned that the rapidly developing field of computer technology was outpacing the extant copyright laws, Congress passed Pub. L. 93-573, 201, 88 Stat. 1873 (1974) creating the National Commission on New Technological Uses of Copyright Works (CONTU) to study and report on the problems and issues of new technology and copyright.

@In 1976, before CONTU reported its findings to Congress, Congress passed a new copyright law to replace the one that had prevailed since 1909. Pub.L. No. 94-553, 90 Stat. 2541(1976) (codified at 17 U.S.C. 101 et seq.). The new law's only explicit accommodation to computer technology was 17 U.S.C. 117, which dealt with copyright issues arising upon certain uses of computer programs not in issue here.

@The Commission's Final Report [hereinafter gCONTU Reporth] was delivered to the President on July 31, 1978. The CONTU Report recommended legislation:

@The new copyright law should be amended: (1) to make it explicit that computer programs, to the extent that they embody an author's original creation, are proper subject matter for copyright; (2) to apply to all computer uses of copyrighted programs by the deletion of the present section 117; and (3) to ensure that rightful possessors of copies of computer programs may use or adapt these copies for their use.
CONTU Report at 1. Congress responded to these suggestions in the 1980 Computer Software Copyright Act by adding a provision to 17 U.S.C. 101 defining computer programs, see Pub.L. No. 96-517, 10(a), 94 Stat. 3028 (1980) (codfted at 17 U.S.C. 101) (quoted supra n.13). It also replaced the old 117 with a new 117 outlining users' rights of adaptation.

@As neither the definition of gcomputer programh nor 17 U.S.C. 117 is relevant here, it would appear that the CONTU Report is of marginal relevance, at best. Nevertheless, defendants argue that it is not only relevant, but that it compels a decision in their favor. Specifically, defendants argue that the CONTU Report recommends that copyright protection be limited to protection of the literal elements of computer programs, and that the CONTU Report is to be taken as authoritative legislative history, which this court is bound to follow. Appellants' Br. at 15-21. This argument is unpersuasive, however.

@In the first place, the CONTU Report never suggests that copyright protection should be limited to the literal code. To the contrary, in discussing the limits of copyright protection, the Report referred to the dichotomy between idea and expression discussed above, and said:

[T]he separation of idea from form of expression . . . is better realized through the courts exercising their judgment in particular cases [than by a per se rule]. . . . Flow charts, source codes, and object codes are works of authorship in which copyright subsists. .
CONTU Report at 21 (emphasis added). While the first part of this passage suggests that the Commission may have reserved judgment as to the coyrightabilty of non-literal elements of computer programs, the second part - particularly the reference to the copyrightability of flowcharts - demonstrates that the Commission intended copyright protection to extend beyond the literal code. Thus, the CONTU Report does not support defendants' position in this case.37

@ Even if the CONTU Report had advocated a strict limitation of the copyrightability of computer programs, defendants' argument would still fail, for the CONTU Report is not binding on us in this case. Defendants correctly note that some courts have treated the CONTU Report as a surrogate legislative history. See, e.g., Micro-Sparc, Inc. v. Am type Corp., 592 F.Supp. 33, 35 n.7, 223 USPQ 1210, 1212, n.7 (D. Mass. 1984) (gThe CONTU Report . .. comprises the entire legislative history of 117.h): Midway Mfg, Co. v. Strohon, 564 F.Supp. 741,750 n.6~ 219 USPQ 42, 49 n.6. The courts have said this because Congress adopted the CONTU Report's recommendations without alterations and without any committee reports. Defendants argue that this court, too, is bound by the CONTU Report for the same reason.

@The argument fails, however, for the only statutory provision relevant to this case is 102(b), see supra, in which no changes were made as a result of the CONTU Report. Therefore, it follows that the CONTU Report cannot be a substitute for legislative history in this case. In effect, defendants ask us to apply the precepts of the CONTU Report regardless of what legislative provision we are considering. We cannot do this, however, for the CONTU Report has force only insofar as it can be said to represent the will of Congress. There is no sense in which it represents the will of Congress with respect to provisions not amended in response to the Report.38


@Defendants' second argument is that even if copyright protection is not limited to computer programs' literal elements as a matter of law, there is insufficient evidence of substantial similarity presented in this case to support a finding of copyright infringement. The defendants claim that all three parts of Dr. Moore's expert testimony as to the similarity of the programs, see supra, were flawed, and also that the district court erred in evaluating the relative weight of Dr. Moore's and Mr. Ness' testimony. We consider these arguments in turn.

A. File structures - Defendants claim that Dr. Moore's examination and conclusions with respect to file structures are irrelevant to the question whether there was a copyright violation. Defendants analogize files to blank forms, which contain no information but merely collect and organize information that is entered from another source. They argue, relying on Baker v. Selden, that, as a matter of law, blank forms cannot be copyrighted. Thus, they conclude, neither can file structures be part of the copyright of a program. See Appellants' Br. at 34-38; Reply Br. at 7-8.39

@Defendants' description of the file structures is indeed correct. Dr. Moore himself described a computer's file as ga storage place for data, and it's really no different in a computer than it is in a file drawer, it's like a manila folder that contains all the data on a particular subject category in a computer.h App. at 682. (Another analogy, particularly accessible to lawyers, is to a very complex cataloging structure like the structure of Lexis or Westlaw without any entries yet made.) Defendants' legal conclusion is not correct, however. Although some courts have stated that the meaning of Baker v. Selden is that blank forms cannot be copyrighted,40 this circuit, like the majority of courts that have considered the issue,41 has rejected this position and instead have held that blank forms may be copyrighted if they are sufficiently innovative that their arrangement of information is itself informative. Apple Computer, Inc., 714 F.2d at 1250, 219 USPQ at 121. See also Manpower, Inc. v. Temporary Help of Harrisburg, Inc., 246 F.Supp. 788, 148 USPQ 85 (E.D. Pa. 1965) (upholding copyrightability of form for vacation schedules).42

@This is not to say that all blank forms or computer files are copyrightable. Only those that by their arrangement and organization convey some information can be copyrighted. Cf I Nimmer at 2-201: gThus books intended to record the events of baby's first year, or a record of a European trip, or any one of a number of other subjects, may evince considerable originality in suggestions of specific items of information which are to be recorded, and in the arrangement of such items.h (footnote omitted). Defendants do not contend, however, that the file structures convey no information, and it appears to us that the structures are sufficiently complex and detailed that such an argument would not succeed. As we have noted, supra, there are many ways in which the same goal - the organization of the business aspects of a dental laboratory - might be accomplished, and several of these approaches might use significantly different file structures.43 The file structures in the Dentalab and Dentcom systems require certain information and order that information in a particular fashion. Other programs might require different information or might use the same information differently. When we compare the comprehensiveness and complexity of the file structures at issue here with the gblank formsh at issue in the cases mentioned above, we have no doubt that these file structures are sufficiently informative to deserve copyright protection.

B. Screen outputs - Defendants' second line of argument is slightly confusing. Defendants appear to argue that to the extent that the district court relied upon the similarity of the screen outputs of Dentalab and Dentcom its finding of substantial similarity was erroneous because (1) the screen outputs are covered by a different copyright from the program's, and/or (2) the screen outputs bear no relation to the programs that produce them. Although these arguments are not always clearly distinguished, Appellants' Br. at 38-41; Reply Br. at 8-10, the distinction is important because whereas the first argument is weak, we feel that the second is more persuasive.

@It is true that screen outputs are considered audio-visual works under the copyright code, see Williams Electronics, 685 F.2d at 874, 215 USPQ at 408; Midway Manufacturing Co., 564 F.Supp. at 749, 219 USPQ at 48 (distinguishing audiovisual copyright in display of videogame from copyright in program that creates the audiovisual display), and are thus covered by a different copyright than are programs, which are literary works, see supra at 27. It is also true that Whelan Associates asserts no claim of copyright infringement with respect to the screen outputs. But the conclusion to be drawn from this is not, as defendants would have it, that screen outputs are completely irrelevant to the question whether the copyright in the program has been infringed. Rather, the only conclusion to be drawn from the fact of the different copyrights is that the screen output cannot be direct evidence of copyright infringement. There is no reason, however, why material falling under one copyright category could not be indirect, inferential evidence of the nature of material covered by another copyright.

@Thus, the question is whether the screen outputs have probative value concerning the nature of the programs that render them sufficient to clear the hurdles of Fed.R.Evid. 401 and 403. The defendants argue that the screen outputs have no probative value with respect to the programs because many different programs can create the same screen output. Defendants rely on Stern Electronics Inc. v. Kaufman, 669 F.2d at 855, 213 USPQ at 444 (gmany different computer programs can produce the same eresults,' whether those results are an analysis of financial records or a sequence of images and sounds.h), and Midway Manufacturing Co., 564 F.Supp. at 749, 219 USPQ at 48 (git is quite possible to design a game that would infringe Midway's audiovisual copyright but would use an entirely different computer program.h). Neither court, however, was presented with the question that faces us today, the evidentiary value of screen outputs in a suit for infringement of the underlying program.h

@Insofar as everything that a computer does, including its screen outputs, is related to the program that operates it, there is necessarily a causal relationship between the program and the screen outputs. The screen outputs must bear some relation to the underlying programs, and therefore they have some probative value. The evidence about the screen outputs therefore passes the low admissibility threshold of Fed.R.Evid. 401.45

@It is still possible, of course, that the risk of unfair prejudice would outweigh the probative value of the evidence, thus contravening Fed. R. Evid. 403. In support of this position one might argue that, because the screen outputs are vivid and easily understood (at least as compared with the obscure details of computer programs), they might have disproportionate influence on the trier of fact. However, because the portions of programs that relate to the screen outputs are often so small a part of the full program, they might say very little about the underlying program. This combination of ease of perception and slight probative value, the argument concludes, works a Rule 403 violation because the screen outputs appear significantly more probative than they in fact can be.

@This argument has force, but we feel that it is ultimately unpersuasive. In the first place, the defendants point to no place in the record where they objected to testimony about the screens similarities. Our independent review of the record has revealed no such objections. See, e.g., App. at 68 1-82 (Dr. Moore testifying about screen similarities without objection from defendants). Therefore, because this could not be plain error, the objection was waived. Second, even if the objection had not been waived, we do not believe that admission of the evidence relating to screen similarity suffices for a Rule 403 exclusion. Screen outputs are not so enticing that a trier of fact could not evaluate them rationally and with a cool head. The party against whom the screen outputs are introduced can easily explain their limited probative value. Given the substantial deference with which we review the district court's decision on this matter, see McQueeney v. Wilmington Trust Co., 779 F.2d 916, 922 (3d Cir. 1985), and the parties' ample opportunities to advance their arguments before the district court, we do not believe that the district court committed error in considering the evidence relating to screen outputs.

C. The five subroutines - With respect to the final piece of evidence, Dr. Moore's testimony about the five subroutines found in Dentalab and Dentcom, defendants state that they gfail to understand how a substantial similarity in structure can be established by a comparison of only a small fraction of the two works.h Appellants' Brief at 43, see also Reply Br. at 12. The premise underlying this declaration is that one cannot prove substantial similarity of two works without comparing the entirety, or at least the greater part, of the works. We take this premise to be the defendants' argument.

@The premise does not apply in other areas of copyright infringement. There is no general requirement that most of each of two works be compared before a court can conclude that they are substantially similar. In the cases of literary works - novels, movies, or plays, for example - it is often impossible to speak of gmosth of the work. The substantial similarity inquiry cannot be simply quantified in such instances. Instead, the court must make a qualitative, not quantitative judgment about the character of the work as a whole and the importance of the substantially similar portions of the work. See, e.g., Harper & Row Publishers, Inc. v. Nation Enterprises, U.S. , n .8, 105 S.Ct. 2218, 2233-34 & 2233 n.8, 225 USPQ 1073, 1083 & n.8 (1985); Atari, Inc. v. North American Philips Consumer Electric Corp., 672 F.2d 607, 618, 214 USPQ 33, 42 (7th Cir.), (gWhen analyzing two works to determine whether they are substantially similar, courts should be careful not to lose sight of the forest for the trees.h), cert. denied, 459 U.S. 880 (1982); Hoehling v. Universal City Studios, Inc., 618 F.2d 972, 979-80, 205 USPQ 681, 686-87 (2d Cir.) (warning against same danger), cert. denied, 449 U.S. 841, 207 USPQ 1064 (1980). See also Universal Pictures v. Harold Lloyd Corp., 162 F.2d 354, 73 USPQ 317 (9th Cir. 1947) (finding copyright violation for copying of 20% of plaintiff's film); In re Personal Computers and Components Thereof, 1983-84 Copyright L. Dec. (CCH) 25,65 1 at 18,931 (Int'l Trade Comm'n Mar. 9, 1984) (18% - 25% identity is sufficient for substantial similarity). Compare Elsmere Music, Inc. v. National Broadcasting Co., 482 F.Supp. 741, 744, 206 USPQ 913, 914 (S.D.N.Y.), affd, 623 F.2d 252, 207 USPQ 277 (2d Cir. 1980) (similarity uncontested by defendants where four notes out of 100 measures and two words out of 45 were identical) with Jewel Music Publishing Co. v. Leo Feist, Inc., 62 F.Supp. 596, 597, 66 USPQ 282, 283 (S.D.N.Y 1945) (finding no substantial similarity where three bars of an eight-bar line were identical and the line appeared 24 times in both songs).

@Computer programs are no different. Because all steps of a computer program are not of equal importance, the relevant inquiry cannot therefore be the purely mechanical one of whether most of the programs' steps are similar. Rather, because we are concerned with the overall similarities between the programs, we must ask whether the most significant steps of the programs are similar. See Midway Mfg. Co. v. Strohon, supra 564 F.Supp. at 753, 219 USPQ at 52. This is precisely what Dr. Moore did. He testified as follows:

@What I decided to do was to look at the programs that had the primary, or let's say most important, tasks of the system, and also ones which manipulate files, because there are a lot of programs that simply print lists, or answer a question when you ask him it, but I thought that the programs which actually showed the flow of information, through the system, would be the ones that would illustrate the system back.
App. at 704. Dr. Moore's testimony was thus in accord with general principles of copyright law. As we hold today that these principles apply as well to computer programs, we therefore reject the defendants' argument on this point.

D. Sufficiency of the evidence - Defendants' final argument is that the district court erred in evaluating the testimony of Dr. Moore and Mr. Ness. They contend that, properly evaluated, Mr. Ness' testimony was sufficiently strong and Dr. Moore's sufficiently weak, that there was not sufficient evidence of substantial similarity for plaintiff to prevail.

@We have described the testimony of Dr. Moore and Mr. Ness, see supra; see also infra, and it is recounted in the district court opinion, Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. at 1316, 225 USPQ at 162. The district court explained its evaluation of the evidence as follows:

I conclude . . .@that Dr. Moore, plaintiffs' expert, had greater knowlege as to the particular programs at issue. Dr. Hess [sic], the defendants' expert witness, reviewed only the source and object codes of the IBM-Series 1 [Dentalab program], the IBM Datamaster [see supra n. 4], and the IBM-PC Dentcom system. He never observed the computer in operation nor viewed the various screens or the user's manual. He stated he was not familiar with EDL coding. More basically, however, his comparison as to dissimilarities was between the IBM Datamaster and the IBM-PC Dentcom systems. Plaintiff contends that the IBM-PC Dentcom is a copy of the IBM Series 1 System - not the IBM-Datamaster system. Dr. Hess's conclusions were that although the overall structures of those systems is similar, the code in the IBM-PC Dentcom is not gdirectly derivedh from either plaintiff's IBM Series-1 or its IBM@Datamaster system. To the extent that Dr. Moore's testimony supports plaintiff's contentions of copying, I find his testimony more credible and helpful because of his detailed and thorough analysis of the many similarities.
Id. at 1321-22, 225 USPQ at 166-67. Determinations of credibility and the relative weight to be given expert witnesses are, of course, left primarily to the discretion of the district court. Our review of the record convinces us that the district court's analysis of the two experts' opinions was far from being erroneous. As the district court pointed out, Mr. Ness had studied the programs, but he had never observed them at work in computers. Id. at 1321, 225 USPQ at 166. The district court also pointed out that Mr. Ness was unfamiliar with EDL coding. Id. These factors suffice to support the court's conclusion.

@In addition, we believe, on re-reading the trial transcript, that although Mr. Ness' testimony was quite competent, Dr. Moore's was persuasive on the issues relevant to this appeal. Whereas the greater part of Mr. Ness' testimony was concerned with the dissimilarities between the two programs' source and object codes, see, e.g. App. at 824-32, Dr. Moore discussed the crucial issue in this case, the similarities and differences in the programs' structures. For example, when he discussed the programs' invoicing subroutine, Dr. Moore testified as follows:

* * *

@In the DentaLab system, the same kind of thing again, same information is up there, description, unit price, extension, items and program reads all those things in from te [sic] number of files actually, and displays them and then gives the operator a number of options to change the order as it appears on the screen to skip this one, to cancel it, or to accept it.
@The same choices are given in Dentalab systems change, skip, cancel.
@Assuming that the order is acceptable, both systems then calculate the money, calculate the amount of money that will be billed, and at this point they use the price code to find which of the four prices are to be charged for this particular customer. Both systems do that. They pick that one of the four prices and calculate the total amount, write then the record of this invoice that has been formed to show the invoice's file, sets the flag in the order's file to show that this order has now been invoiced so that it doesn't get reinvoiced.
Q.@ What is a flag?
A.@ Well, a flag would be, in this case, a certain location is marked I for invoices, just an indicator that invoicing has been done on this record.
Q.@ Both used it?
A.@ Both used a flag. I don't remember whether Dentcom uses a letter I or some other symbol, but there is a flag there that it's a field number 12, in which it's indicated that this file has been invoiced or this order has been invoiced.

* *

Q.@Do you have any comment about the invoicing?
A.@Well, I think it should be clear, it was clear to me from going through these programs that there is a very marke[d] similarity between the two, that they, item by item, are doing pretty much the same thing with the same fields in the same files, and accomplishing roughly the same results.
@So there was quite a match, line by line, between these two, flow in these two.
Q.@What do you conclude from that?
A.@Well, back together with the file's structure, sort of set up with the - how the programs have to proceed. I would think that the person who designed or constructed the DentaLab system must have been thoroughly familiar with the Dentcom system.
@The person who constructed the Dentcom system must have been familiar with the series one system, because the same file structure and same program steps are followed, same overall flow takes place in both systems.

App. at 710-12 (emphasis added). Dr. Moore's testimony about Dentcom's and Dentalab's month-end subroutines also demonstrates the structural comparisons in which he engaged:
Q.@What did you find in month-end?
A.@Okay. Month-end, the calling program in Dentcom, this obviously is done at the end of each month.
@In the Dentcom system there is a program called MOEND, which chains all these other programs, that is MOEND calls MOPRDL, and after that program runs, goes back to MEEND, calls the print sale and so on.
@In the Dentalab system there is a supervisory program also called MOEND, and that system calls or runs a series of programs doing various functions.
@Now if we look at the functions done by the programs in order, we find that they are the same except for a flipping of the order in the first two things.
@The Dentcom system, it first prints product group report, and then prints the monthly customer sales analysis.
@In Dentlab, just reverses, prints sales analysis first, product group report second.
@After that, both systems do the same thing in the same order.
@They now do accounts receivable aging, since a month has gone by they have to update all the 30 days, 60 days, et cetera, calculate service charges. Then they print the monthly AR reports that had to do with service charges, only those that involve service charges, they both do that. Then they both print the age file balance, balance report, and following that they print the month and accounts receivable report. That's the total accounts receivable rport [sic!.
@Then they both go through and look for accounts that are not active that month, and print a list of these accounts, accounts not serviced, an account that doesn't have any access.
@The final think that the Dentcom system does is to calculate the new AR total for the entire lab, which I mentioned is contained in the company file.
@DentaLab doesn't keep that total, so that's the last item, that is not as far as I can tell, done by DentaLab. I may have said -did I say Dentcom keeps that total? DentaLab does not. That's the only difference.
App. at 716-18 (emphasis added). Dr. Moore testified in similar detail and to similar effect about the other three subroutines that he felt were particularly important, order entry, account receivable, and day's end.h46@This testimony, in addition to Dr. Moore's exhaustive comparison of the two programs' file structures, see supra 12, and his testimony about the screen outputs, id., demonstrates the marked similarity between the programs. Defendants' argument as to sufficiency of the evidence therefore fails.47


@[2] We hold that (1) copyright protection of computer programs may extend beyond the programs' literal code to their structure, sequence, and organization, and (2) the district court's finding of substantial similarity between the Dentalab and Dentcom programs was not clearly erroneous. The judgment of the district court will therefore be affirmed.


1 We use the terms gstructure,h gsequence,h and gorganizationh interchangeably when referring to computer programs, and we intend them to be synonymous in this opinion.

2 A letter of August 31, 1978, explained what the program would do for Jaslow Lab and how much it would cost. See App. at 1770-75. A letter from Strohl to Jaslow Lab dated September 20, 1978, supplemented the August 31 proposal as follows:
This communication is a supplement to our proposal letter dated 8/31/78.
We [Strohl] propose that all software developed by us for your dental laboratory system remain under our ownership. This basic system can then be marketed to similar laboratories by our organization. A royalty of ten percent of the basic package price would be returned to Jaslow Dental Laboratory for each system sold.
Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. 1307, 1310, 225 USPQ 156, 158 (E.D. Pa. 1985) (the district court inadvertently identified the letter as dated September 30, 1978). Although no representative of Jaslow Lab ever signed either agreement, the district court found that Jaslow Lab had, through its conduct, accepted the terms of the letter. Id. at 1310, 225 USPQ at 158.

3@Rand Jaslow on behalf of Jaslow Lab sent a letter to Whelan Associates on June 22, 1982, stating its intention to terminate business relations in 30 days. However, the parties continued to do business under the agreement of July 30, 1980 until the termination letter of May 31, 1983, discussed below

4@The record indicates that Whelan Associates also developed a BASIC version of the Dentalab, written specially for the IBM-Datamaster 26 computer. That program [the gDatamasterh program], did not succeed commercially. Whelan Associates has also written a second program in BASIC for dental laboratories' business operations. The second program was intended for use on IBM-PC's. Neither the Datamaster program nor Whelan Associates' program for the IBM-PC is directly in issue here. But see infra 12 (use of Datamaster program by defendants' expert witness at trial).

5@The district court inadvertently referred to this as the letter of January 31, 1983. See Whelan Associates v. Jaslow Dental Laboratory, 609 F.Supp. 1307, 1313, 225 USPQ 156, 160 (E.D. Pa. 1985).

6@Joseph Cerra had, from January until June, 1983, been in the employ of Whelan Associates in charge of their marketing. In this position, he had had close contact with Rand Jaslow. When he left Whelan Associates, he made a verbal promise to Elaine Whelan that he would not become associated in any business ventures with Rand Jaslow. There was, however, no written agreement. App. at 1088. Although Mr. Cerra was originally named as a defendant, he settled prior to trial.
@The record contains no information about Paul Mohr's employment history or of his previous associations with Whelan Associates or any of the defendants.
7@17 U.S.C. 106(1982), which prescribes copyright holders' exclusive rights, forbids the copying of copyrighted works. The independent creation of even identical works is therefore not a copyright infringement, and independent creation is a complete defense to a claim of copyright infringement. See also Fred Fischer, Inc. v. Dillingham, 298 F. 145, 147 (S.D.N.Y. 1924) (L. Hand, J.) (gthe law imposes no prohibition upon those who, without copying, independently arrive at the precise combination of words or notes which have been copyrighted.h).

8@ Dr. Moore's testimony is discussed in greater detail infra at 59-63.

9@Source and object code are defined infra at 19-20.

10@There were two such sales by Dentcom.

11@There were 23 such sales.

12@The appeal is from the court's injunction preventing defendants from selling the Dentcom program. The court has not yet entered a final judgment covering pre- and post-trial damages. Our jurisdiction is thus pursuant to 28 U.S.C. 1292(a)(1).

13@Title 17 U.S.C. 101 (1982), gives a more technical rendering, defining a computer program as ga set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.h

14@More detailed descriptions of this process can be found in D. Bender, Computer Law - Software Protection 2.06[3l (1985): Yohe, An Overview of Programming Tactics, 6 Computing Surveys 221(1974).

15@Technically speaking, modules and subroutines are slightly different. Compare R. Andree, J. Andree & D. Andree, Computer Programming 336 (1973) (defining subroutines) with R. Coats, Software Engineering for Small Computers 12 (1983) (modules). For present purposes, however, they may be used synonymously as discrete parts of programs with readily identifiable tasks.

16@Elaine Whelan's material on the various elements, files and subroutines of the Dentalab system are voluminous, taking up over 200 pages of the record. See App. at 1222-1469. The material consisted of detailed outlines on how the program was to be structured.

17@The discussion in this paragraph draws heavily from Note. Copyright Protection of Computer Program Object Code, 96 I-Iarv. L. Rev. 1723, 1724-25 [1983].

18@We ignore the distinction between ghigh level languageh and gassembly language.h see Note, 96 Harv. L. Rev. 1723, 1725 (1983), which is not relevant to the issues in this case. Both of these may be referred to as gsource codes.h See Apple Computer, Inc. v. Franklin Computer Corp. 714 F.2d 1240, 1243, 219 USPQ 113, 115 (3d Cir. 1983), cert. dismissed, 464 U.S. 1033 (1984).

19@The IBM Series One, for example, can read EDL but not BASIC: the IBM-PC can read BASIC, but not ED.

20@The discussion assumes that the program is gcompiledh or gassembled.h If a program is ginterpreted,h then the source and object codes are joined in a single step. Whether a program is compiled or interpreted depends on the program and the machine on which it is run. The difference is not important in this case.

21@There are three other facets of program creation, debugging, documentation, and maintenance. Although none of these functions are at issue in this case, in the interest of completeness we shall describe them here. After the object code has been completed, the program must be gdebuggedh and documented. Debugging, or error removal, is frequently a lengthy process, for any moderately difficult task may require a fairly detailed and complex program. See D. Bender, supra. 2.06[3][e]. The program demands arduous debugging not only because of its complexity, but also because of its delicacy. Even slight and perhaps obvious errors can hinder a program, for a computer has no way of recognizing errors. Like a perfect soldier, it takes instructions without questioning them.
@Documentation is the general term for the material that a programmer must give to a user to explain how the program runs. Programs frequently come with pamphlets that explain the program's powers and limitations. The documentation must anticipate as many potential questions and exigencies as the programmer can imagine the user will face because most people do not understand computers and programs fully, and it would therefore be very difficult for users to solve their problems themselves. Thus, proper documentation should gdocument everything, continually assuming [that the users] are going to have an attack of amnesia next week.h Brown, Programming and Documenting Software Projects. 6 Computing Surveys 213, 219 (Dec. 1974). See also Yohe, supra n.14 at 221.
@Finally, programmers are also usually responsible for the maintenance of their programs. No mattter how thorough the debugging and documentation problems will likely arise as the user develops new needs for the program. The programmer, like a car manufacturer or dealer, must be prepared to fix latent bugs, adapt the program, or incur other so-called glife cycleh costs of maintenance.

22@The district court found, inter alia, that Rand Jaslow ghad surreptitiously and without consent of either Strohl Systems or Whelan Associates obtained a copy of the [Dentalab] source code.h id., and that he had gutilized the source code in his attempt to develop the IBM-PC Dentcom program.h id. at 1321, 225 USPQ at 166.

23@Although not an issue in this case, see infra n.47, it is important to note that even the showing of substantial similarity is not dispositive, for it is still open to the alleged infringer to prove that his work is an original creation, see supra n.7, or that the similarities between the works was not on account of copying but because both parties drew from common sources that were part of the public domain. The cause of the substantial similarity - legitimate or not - is a question of fact.

24@This circuit has once used the single substantial similarity inquiry advocated here in a computer copyright case. See Williams Electronics v. Arctic International, Inc., 685 F.2d 870, 876 n.6, 215 USPQ 405, 409 n.6 (3d Cir. 1982) (finding substantial similarity in computer programs without mentioning the Arnstein test). Williams did not explain why it did not use the bifurcated Arnstein test, nor did it distinguish Universal Athletic Sales. To the extent that Williams did these things sub silentio, our holding today is merely a ratification of Williams on this point.

25@Because the first argument involves solely a question of law, our review is plenary. The second argument involves questions of fact, and we therefore apply the gclearly erroneoush standard of review. See Original Appalachian Artworks, Inc. v. Toy Loft 684 F.2d 821 ,825 n.4, 215 USPQ 745, 748 n.4 (11th Cir. 1982); International Luggage Registry v. Avery Products 541 F.2d 830, 831, 192 USPQ 426 (9th Cir. 1976.

26@Professor Nimmer distinguishes two ways that one work might be substantially similar to another; comprehensive nonliteral similarity, and fragmented literal similarity, 3 Nimmer at 13.03[A]. See also Warner Bros. v. American Broadcasting Cos., 720 F.2d 231, 240, 222 USPQ 101,108 (2nd Cir. 1983) (noting distinction); Smith v. Weinstein, 578 F.Supp. 1297,1303, 222 USPQ 381, 385 (S.D.N.Y) (Same), affid, 738 F.2d 419 (2d Cir. 1984). The titles are suggestive of their meanings; comprehensive nonliteral similarity means ga similarity not just as to a particular line or paragraph or other minor segment, but [that] the fundamental essence or structure of one work is duplicated in another.h 3 Nimmer at 13-20.1, while fragmented literal similarity means occasional, but not complete, word-for-word similarity. Id. In Professor Nimmer's terminology, we are concerned here only with comprehensive nonliteral similarity.

27@Achieving the proper incentive has been a longstanding task of courts. See, e.g., Sayre v. Moore, 102 Eng. Rep. 138, 140 n.6 (1785)(Lord Mansfield):
[W]e must take care to guard against two extremes equally prejudicial; the one, that men of ability, who have employed their time for the service of the community, may not be deprived of their just merits, and the reward for their ingenuity and labor; the other, that the world may not be deprived of improvements, nor the progress of the arts be retarded.
See also Twentieth Century Music Corp. v. Aiken, 422 U.S. 151, 156, 186 USPQ 65, 67 (1975); Apple Computer, 714 F.2d at 1253, 219 USPQ at 123 (Sloviter, J.) (gthe line must be a pragmatic one, which also keeps in consideration ethe preservation of the balance between competition and protection reflected in the patent and copyright laws.'h (quoting Herbert Rosenthal Jewelry Corp. v. Kalpakian, 446 F.2d 738, 742, 170 USPQ 557, 559 (9th Cir. 1971)))

28@This test is necessarily difficult to state, and it may be difficult to understand in the abstract. It will become more clear as we discuss and explain it in the textual discussion that follows this footnote. See also infra (discussion of the copyrightability of file structures that raise many of the issues considered here). As will be seen, see infra, the idea of the Dentalab program was the efficient management of a dental laboratory (which presumably has significantly different requirements from those of other businesses). Because that idea could be accomplished in a number of different ways with a number of different structures, the structure of the Dentalab program is part of the program's expression, not its idea.

29 See Landsberg v. Scrabble Crossword Game Players, Inc. 736 F.2d 485, 489, 221 USPQ 1140, 1143 (9th Cir.) cert. denied, U.S., 105 S.Ct. 513 (1984); See v. Durang, 711 F.2d at 1423, 219 USPQ at 772; Hoehling v. Universal City Studios, Inc., 618 F.2d 972, 979, 205 USPQ at 686 (2d Cir. 1980)

30 Hoehling, 618 F.2d at 979, 205 USPQ at 686 (explaining the scenes a faire doctrine as follows:gBecause it is virtually impossible to write about a particular historical era or fictional theme without employing certain estockf or standard literary devices, we have held that scenes a faire are not copyrightable as a matter of law.h); cf Dymow v. Bolton, 11 F.2d at 691 (g[I]f the same idea can be expressed in a plurality of totally different manners a plurality of copyrights may resul...h).

31@As we discuss below, see infra n. 34, not all non-literal elements are essential to a given computer program.

32 Even if the product of the alleged infringerfs efforts is a mixture of old and new elements, that would not protect it from the charge of infringement. Parodies, for example, mix copied elements with originality, yet they can violate the copyright of the work being parodied. See generally Note, The Parody Defense to Copyright Infringement: Productive Fair Use After Betamax, 97 Harv. L. Rev. 1395 (1984).

33 Long before the first computer, Sir Issac Newton humbly explained that "if [he] had seen farther than other men, it was because [he] had stood on the shoulders of giants."

34 We do not mean to imply that the idea or purpose behind every utilitarian or functional work will be precisely what it accomplishes, and that structure and organization will therefore always be part of the expression of such works. The idea or purpose behind a utilitarian work may be to accomplish a certain function in a certain way, see, e.g., Baker v. Selden, 101 U.S. at 100 (referring to Selden's book as explaining ga peculiar system of book-keepingh), and the structure or function of a program might be essential to that task. There is no suggestion in the record, however, that the purpose of the Dentalab program was anything so refined; it was simply to run a dental laboratory in an efficient way.

35 See also Mooers, Computer Software and Copyright. 7 Computing Surveys -, 50 (March 1975) (gAlso included in the eexpressionf is the sequence, choice, and arrangement of descriptive elements....h). Two commentators have criticized Synercom for its refusal to permit sequencing and ordering in the computer context to constitute expression. See Pierce, Copyright Protection for Computer Programs. 30 Copyright Law Symposium 1, 19 (1983) (Synercom gstands alone. .. [in denying] copyright protection when the sequence and arrangement of data had been expressed by others in different ways.h (footnote omitted) ): Note, Defining the Scope of Copyright Protection for Computer Software, 38 Stan. L. Rev. 497, 525 (1986) (criticizing Synercom on the ground that gsequence and arrangement are expression that is separable from the underlying utilitarian purpose of the [input] formats, which is to enable the user to communicate with the computer program.h (footnote omitted)). The notewriter concluded that gcopyright law should.., recognize that organizing and connecting the modules and subroutines is a protectible act of authorship.h Id. at 526.

36@It is not clear whether the end sought to be accomplished by the input formats involved in Synercom could be accomplished with different sequences and orders. Compare 462 F.Supp. at 1013, 199 USPQ at 546 (gthere are many ... possible choices of computer formats, and the decision among them [is] arbitraryh) with id. at 1014, 199 USPQ at 547 (gThe eidea or principlef behind the forms in question, and the emethod or system' involved in them, [are] no more or less than the formats.h). Moreover, as noted above, the input formats involved in Synercom are not identical to the structures of computer programs that concern us here.

37@The defendants also rely on statements (not included in the CONTU Report) of individual members of the Commission and of testimony before the Commission. See Appellantsf Br. at 16-17, 18-21. This extrinsic evidence is weak, however, and cannot outweigh the explicit statement of the CONTU Report itself.

38@Defendantsf final argument as to the protectability of program structures is that the Copyright Office has taken the position that the defendants advocate here, and that as the Copyright Office is the agency responsible for the administration of the copyright laws, we should grant deference to its interpretation. In support of its position, the defendants refer us to the Copyright Officerfs Circular R61 (May 1983).


@Copyright protection extends to the literary or textual expression contained in the computer program. Copyright protection is not available foridea, program logic, algorithms, systems, methods, concepts, or layouts.
Circular R61 (May, 1983). Copyright Office circulars are not technical documents, but are gintended to present simple explanations of the law,h for lay persons. Declaration of Arthur J. Levine, former Assistant Chief of the Copyright Office Examining Division and member of CONTU Commission. It is therefore questionable whether the circular deserves great deference on a matter so complex as this one. At any rate, without analyzing the circular in depth - and its import is far from clear - we feel that the argument and evidence we have set forth in the text are sufficient support for our position and that to the extent the Copyright Office's circular differs, it should not be followed.

39@As will be seen below, defendants' argument here parallels their argument discussed in V.A. Defendants again rely on the idea-expression dichotomy and argue that computer files embody ideas and not expressions. The thrust of defendants' argument is that mere organization or ordering cannot be expression, but must be idea. Once again, we reject the argument. We separate the discussion here from the one in V.A. for two reasons. First, whereas defendants' first argument was that the structure of the whole program was classifiable as idea, not expression, the argument here is that a certain part of the program - the file structure - is idea, not expression. Thus, although the form of the arguments is the same, the subject is different. Second, in our analysis of the file structures, we are aided by the clear precedents and close analogy of blank forms, discussed infra. The law surrounding blank forms is particularly appropriate to the question of computer file structures.

40@See, e.g. Brown Instrument Co. v. Warner, 161 F.2d 910, 911, 73 USPQ 427 (D.C. Cir.), cert. denied, 332 U.S. 801,75 USPQ 365 (1947); Taylor Instrument Companies v. Fawley-Brost Co., 139 F.2d 98, 100-01, 59 USPQ 384, 386-87 (7th Cir. 1943), cert. denied, 321 U.S. 785, 60 USPQ 579 (1944).

41@See e.g. Edwin K. Williams & Co. v. Edwin K. Williams & Co. -- 542 F.2d 1053, 191 USPQ 563 (9th Cir. 1976) (gas station account books held copyrightable), cert. denied, 433 U.S. 908 (1977); Baldwin Cooke Co. v. Keith Clarke, Inc., 383 F.Supp. 650, 652, 655, 183 USPQ 209, 211 (N.D. Ill.) (ga combined calendar, appointment, diary and information bookh is gmuch more than a mere diary,h and is thus copyrightable), affd per curiam, 505 F.2d 1250, 183 USPQ 769 (7th Cir. 1974); Harcourt Brace & World Inc. v. Graphic Controls Corp., 329 F.Supp. 517, 171 USPQ 219 (S.D.N.Y. 1971) (answer sheets for recording multiple choice achievement and intelligence test answers held copyrightable). See also I Nimmer 2.08[D][1]; id. 2.1 81C111 ](articulating and endorsing the gnarrowh reading used by these courts, as contrasted by the gbroadh reading illustrated in Brown, supra, and Taylor Instrument, supra); A. Latman, The Copyrzght Law 29-31 (5th ed. 1979)(collecting cases).

42@It is unclear whether the Copyright Office's regulation would permit copyright protection for blank forms or would impose a per se rule against such protection. Title 37 C.F.R. 202.1(c) (1985) denies copy protection to

Blank forms such as time cards, graph paper, account books, diaries, bank checks, scorecards, address books, report forms, order forms and the like, which are designed for recording information and do not in themselves convey information.
To the extent that regulations do impose a per se rule against the copyrightability of blank forms, they analysis is perfectly consistent with this position. See supra n. 41 (Collecting cases).

43@ Defendantsf expert, Mr. Ness, testified that, given the problem to be solved, there were in fact few possible, efficient, file structures, and that the similarity in the programsf file structures was therefore neither surprising nor probative. See App. at 834-37. The district court apparently did not find Mr. Ness persuasive on this point, however, and we defer to the courtfs assessment. Had the defendants offered more evidence to support their position, our answer might have been different. It is true that for certain tasks there are only a very limited number of file structures available, and in such cases the structures might be copyrightable and similarity of file structures might not be strongly probative of similarity of the program as a whole. We are simply not convinced that this is such a case.

44@Stern Electronics was simply explaining a party's decision to copyright the underlying program rather than the screen output. Midway Manufacturing's discussion was a part of its holding that a computer program for audiovisual games is copyrightable separately from the video display. Our analysis is perfectly consistent with this position. See supra.

45@Our holding that evidence of screen outputs may be admissible does not necessarily mean that such evidence would be alone sufficient to withstand motions of summary judgment or directed verdict. Judge Rosenn believes that ordinarily and in the circumstances of this case, screen outputs have no probative worth in determining whether one computer program is copied from another. Different program codes in different computer languages are capable of producing identical screen outputs. To the extent that the district court relied on the screen outputs as evidence of copying, he believes it erred. He concludes such error was harmless, however, in light of all the evidence of copying, the access to and use of the plaintifffs source code, the similarity in the structure of the programs and in flow charts. This court will not reverse a district courtfs factual determination in a non-jury trial where there is sufficient evidence in the record to support it, other than the challenged evidence. DeLaval Turbine, Inc. v. West Indies Industries, Inc., 502 F.2d 259, 263-64 (3d Cir. 1974).

46 Dr. Moore's notes comparing the two program's modules were introduced as exhibits. His comparison of the order entry modules in characteristic of his comparisons of the other modules and is reprinted in Appendix A to this opinion. As we have suggested, this evidence is probative, not dispositive, of copyright infringements.

47@Of course structural similarities between two programs can also arise in completely legitimate ways- e.g., where the authors of the two programs have included subroutines from common, unprotected subroutine libraries, or where the authors of both programs have consulted common, public domain, reference books. There can be no bright line rule as to when similarities are evidence of infringement and when they are legitimate-that is a determination to be made by the trier of fact. See supra note 23. There is no suggestion in the present case that the similarities between Dentalab and Dentcom were the result of such common ground, however, and so the courtfs inference of copyright infringement from its finding of substantial similarity was correct.