Tag Archives: software

An API for the Human Mind

Patent, , , , , , , , ,

by Dennis Crouch

The pace of technological advancement never ceases to amaze me, and it seems like even science fiction is struggling to keep up with reality. In recent months, we’ve witnessed some truly remarkable breakthroughs in the field of artificial intelligence (AI), and this latest development is right up there.

Researchers have used GPT-style machine learning architecture to decode human thoughts by analyzing their functional MRI (fMRI) brain scans. That’s right – we’re talking mind reading. The AI was initially trained trained by exposing participants to 16 hours of narrative stories while recording their brain activity.  And, once trained, the AI was able to accurately describe the content of their thoughts.  Of some interest, the AI was better at identifying concepts and meaning rather than the actual words at issue.

While this technology has the potential to revolutionize communication for individuals with disabilities or neurological conditions, it also raises some privacy concerns that could involve both reading thoughts and writing them.

I imagine that all this wouldn’t require a fMRI technology and instead could rely upon much smaller safe-for-home equipment such as Functional near-infrared spectroscopy (fNIRS) devices shown in the image above or made by Artinis.

A key for me here is that this is potentially moving toward an API for the human mind and body.  For those outside the software world, an API (Application Programming Interface) is a set of protocols, tools, and standards that allow different computer applications to communicate with each other. APIs provide a standardized way for software components to interact.  An API for the human mind and body would create an interface that allows software systems to access and interact with the brain or and other body parts. Over the past several years, folks have been making huge advances with brain/body connection, and I’m excited about where we are headed in this expanded mind approach.

Enjoy!

Federal Circuit Narrows Scope for Copyrighting Software Function

Patent, , , ,

by Dennis Crouch

The copyright lawsuit between the data-software company SAS Institute and its scrappy copycat World Programming has been interesting to follow over the past several years, and the Federal Circuit has now issued a controversial opinion in the case.  SAS Inst. v. World Programming Ltd., — F.4th — (Fed. Cir. 2023).  The majority opinion authored by Judge Reyna and joined by Judge Wallach affirmed the lower court ruling that SAS failed to establish copyrightability of its claimed program elements.  Writing in dissent, Judge Newman argued that the majority’s rejection of copyrightability represents a “far-reaching change” not supported by either precedent or good policy.  I called this outcome controversial. The outcome would also be controversial had Judge Newman’s position prevailed.

The case is properly seen as an extension of the Supreme Court’s decision in Google
LLC v. Oracle America, Inc., 141 S. Ct. 1183 (2021).  In that case, the Court found that Google’s use of Java API naming conventions in its Android operating system was fair use under copyright law.  Because its fair use decision decided the case, the court did not rule separately on whether the API was even copyrightable in the first place.  In SAS v. WPL, the Federal Circuit squarely addressed the copyrightability question.

To be clear, computer software can still be copyrightable.  But, parties asserting protection will need to do a much better job of showing how their creative authorial input survives the “abstraction-filtration-comparison test,” which the Federal Circuit  applied in its decision.

Copyright law’s abstraction-filtration-comparison (AFC) test is used to determine whether a particular work is entitled to copyright protection. The AFC test involves breaking down a work into its constituent parts, abstracting the unprotectable elements, filtering out any remaining unoriginal or unprotectable elements, and then comparing the remaining protectable elements to the allegedly infringing work. The AFC test has been previously adopted by the Second, Fifth, and 10th Circuits.

Here, the court did not delve into the comparison step — and instead simply held that there was nothing left to infringe after abstraction & filtration.

The decision is also substantially procedural.  The district court held a copyrightability hearing and followed a burden shifting procedure created by the 11th Circuit in Compulife Software Inc. v. Newman, 959 F.3d 1288 (11th Cir. 2020).  In particular, the court first assumed that the work was copyrightable based upon the registration documents.  It then allowed the defense to present its filtration argument to show a lack of copyrightability.  If that evidence is sufficient (as it was here), the burden then shifts back to the copyright holder to rebut — and “to establish precisely which parts of its asserted work are, in fact, protectable.”   The difficulty for SAS is that it offered no rebuttal and instead “refused to engage in the filtration step and chose instead to simply argue that the SAS System was ‘creative.'” Slip Op. SAS presented an expert witness on copyrightability, but the district court found it extremely unreliable and thus excluded the testimony.  (The expert had not seen anything to filter out — even clearly unprotectable elements).

The majority walked through each of these issues and ultimately affirmed on all grounds.

= = = =

Some background: SAS makes data analysis software. A key feature of the SAS product is that folks can write programs using SAS syntax in order to get certain results. Thus there are a number of data jockeys who are experts in SAS code.  WPL is a UK based software company who obtained several copies of SAS statistical software and made their own clone version by rewriting the code and by relying upon an early version of SAS that is not protected by copyright.  The WPL version allows folks to use SAS language to get the same results — but at a much lower price.   When I sa “same results” — the clone pretty much identically copied output styles so that a chart made with WPL looks basically identical to a chart made in SAS using the same code.

SAS sued in E.D.Tex for copyright infringement.  Judge Gilstrap dismissed the copyright claims — holding that the software was unprotectable.  Copyright infringement appeals are ordinarily not heard by the Federal Circuit, but in a case of what appears to be appellate-forum shopping, SAS had also included patent infringement allegations that they eventually stopped pursuing.  Under the rules of procedure, if patent claims were raised in the case at some point, then the appeal heads to the Federal Circuit.

The copyright case is not about copying code.  It appears rather to be about copying the input syntax format used by individuals to input their programs and the output design styles for outputting data in some particular style. In the filtration analysis, WPL provided a host of evidence to show that these features should be “filtered out” of the SAS copyrights.

  • WPL established that an earlier version of the SAS System, “SAS 76,” was in the public domain.
  • WPL showed that many Input Formats and Output Designs in the current SAS System are identical or nearly identical to those in SAS 76 and should be filtered.
  • WPL demonstrated that the SAS Language should be filtered because it is open and free for public use.
  • WPL’s expert identified various allegedly copied materials that contained unprotectable elements such as open-source, factual, data, mathematical, statistical, process, system, method, and well-known and conventional display elements.

Bringing these together the Federal Circuit concluded that the defense had presented sufficient evidence to show uncopyrightability and that the district court was justified in requiring SAS to directly and particularly rebut the evidence rather than simply allowing a trial on the copyright as a whole.

The district court was correct to exercise its authority and require SAS to articulate a legally viable theory on which it expected to base its copyright infringement claims. Conversely, it would be improper for a district court to permit a matter to proceed to trial on the basis of vague and unidentified theories.

Slip Op.

Writing in dissent, Judge Newman argued that Fifth Circuit law protects this sort of computer software architecture even from non-literal copying.  The key citation is likely to a the Fifth Circuit’s 1994 Engineering Dynamics case:

Most courts confronted with the issue have determined that copyright protection extends not only to the literal elements of a program, i.e., its source code and object code, but also to its “nonliteral” elements, such as the program architecture, “structure, sequence and organization,” operational modules, and computer-user interface.

Eng’g Dynamics, Inc. v. Structural Software, Inc., 26 F.3d 1335 (5th Cir. 1994).   Judge Newman noted that “computer programs” are expressly protected within the Copyright Act

Copyright protection subsists . . . in original works of authorship . . . including . . . (5) computer programs.

17 U.S.C. 102. As the Nimmer treatise explains, this 1980 amendment to the laws “dispels any lingering doubts as to the copyrightability of computer programs. It is
therefore now firmly established that computer programs qualify as work of authorship in the form of literary works, subject to full copyright protection.”
1 NIMMER ON COPYRIGHT § 2A.10(B) (2022 ed.).

Here, Judge Newman particularly noted that the collection of the various input functions and output designs is easily copyrightable. And, this is the same analysis done by the Federal Circuit in its original Oracle v. Google decision.

Judge Newman also concluded that the district court improperly shifted the burden of proof to the copyright holder.

= = = (more…)

Federal Circuit: Software Function Equals Structure

Patent, , , , ,

by Dennis Crouch

KEYnetik, Inc. v. Samsung Electronics Co. (Fed. Cir. 2023)

This short non-precedential opinion authored by Chief Judge Moore affirms a PTAB IPR obviousness finding.  The case has one key sentence:

Normally, once the function to be performed by software has been identified, writing code to achieve that function is within the skill of the art.

Slip Op.  This statement sits well with modernist design principles aptly stated by architect Louis Sullivan: “Form ever follows function.”

The patent challenger had provided expert testimony that software modifications needed to transform the prior art into the claimed invention would be “straightforward” and “simple.”  Those statements were not backed-up with specific analysis showing exactly how the modifications would be done.  However, the Federal Circuit concluded that these general conclusions combined with the implied judicial notice from above were sufficient to support the PTAB’s factual finding that PHOSITA would have “a reasonable expectation of success” in making the transformation.

Going back to the function-equals-structure statement from above: The court does not explain or particularly justify its factual conclusion other than to cite  its own 1997 decision of Fonar Corp. v. Gen. Elec. Co., 107 F.3d 1543, 1549 (Fed. Cir. 1997).  Fonar Corp. did not deal with obviousness, but instead was an appeal on the issue of best-mode disclosure under Section 112.   The patentee had provided functions of the software in its disclosure but had not provided the computer code itself.  On appeal, the Federal Circuit found that disclosure of the functionality was sufficient to satisfy best mode:

As a general rule, where software constitutes part of a best mode of carrying out an invention, description of such a best mode is satisfied by a disclosure of the functions of the software. This is because, normally, writing code for such software is within the skill of the art, not requiring undue experimentation, once its functions have been disclosed. It is well established that what is within the skill of the art need not be disclosed to satisfy the best mode requirement as long as that mode is described. Stating the functions of the best mode software satisfies that description test. We have so held previously and we so hold today.

Id.  The Federal Circuit did not endeavor to work through its Section 112(f) jurisprudence where it has repeatedly held that disclosure of function is insufficient to satisfy the ‘structure’ requirements of that provision.

Are Copyright and Patent Overlapping or Mutually Exclusive in Protecting Software Innovations?

Patent,

Guest Post by Pamela Samuelson, Berkeley Law School.  Professor Samuelson’s newest article Functionality and Expression in Computer Programs: Refining the Tests for Software Copyright Infringement, is forthcoming in the Berkeley Technology Law Journal.

“Neither the Copyright Statute nor any other says that because a thing is patentable it may not be copyrighted. We should not so hold.” So said the Supreme Court in Mazer v. Stein, 347 U.S. 201, 217 (1954).

In Oracle Am. Inc. v. Google Inc., 750 F.3d 1339 (Fed. Cir. 2014), the Federal Circuit invoked this language in rejecting Google’s “policy” argument that application program interface (API) designs were more appropriately patent, not copyright, subject matter. Id. at 1380-81. The Oracle decision seemingly accepted as unobjectionable the possibility of overlapping utility patent and copyright protections in program interfaces, and perhaps even of copyright as a gap filler for interface designs for which patents had not been obtained.

Because the contours of copyright and patent protections for software innovations remain unclear notwithstanding more than 50 years of experience trying to apply these intellectual property (IP) regimes to these utilitarian writings and virtual machines, the question of whether or to what extent copyright and patent overlap or are mutually exclusive continues to bedevil the field. The Federal Circuit’s Oracle decision is unlikely to be the last word on this subject.

Recently, I rediscovered the 1991 study that the Patent & Trademark Office (PTO) and the Copyright Office wrote about the software IP overlap or exclusivity issue. The Patent-Copyright Laws Overlap Study (May 1991) was prepared at the behest of the House Subcommittee on Intellectual Property and the Administration of Justice. The Study is more than 90 pages in length and has more than 50 pages of appendices.

[1991 Patent-Copyright Overlap Study]

Among the most significant of the Study’s software findings is that there is “no overlap in subject matter: copyright protects the authorship in a set of statements that bring about a certain result in the operation of a computer, and patents cover novel and nonobvious computer processes.” Letter from Ralph Oman and Harry F. Manbeck to the Hon. William J. Hughes, July 17, 1991 (transmitting the Study to the then Chair of the House Subcommittee).

Another finding is that “[p]atent protection is not available for computer programs per se,” which supports the Study’s conclusion that copyright and utility patent for programs are not “coextensive.” Study at iii (emphasis in the original). The Study identifies the doctrinal rationale for this exclusivity: program innovations “consist of mental steps or printed matter.” Id. at vii. Copyright and patent could, however, protect “totally different aspects” of program innovations. Id. at 2. The Study cited to the Supreme Court’s decision in Baker v. Selden, 101 U.S. 99 (1879) as the “bedrock opinion for the view that patent and copyright are mutually exclusive.” Id. at 19.

As for user interface designs, the Study reports that “[t]he mere display on a screen of commands, menus, questions and answers, forms, or icons is not generally considered patentable subject matter for utility patents” because “it is generally considered to be merely printed matter.” Id. at 45-46. Yet processes to produce user interface displays might be eligible for utility patenting. Id. at 47. (The Study discusses the possibility of design patent protection for icons. Id. at 46-47.)

Insofar as user interface screen displays have original expressive elements (e.g., videogame graphics), they would be eligible for copyright protection. Id. at 60-67. However, many aspects of user interface designs are akin to blank forms and lack originality. Id. at 68-69. Some aspects of user interfaces, such as lists of commands, are uncopyrightable under the doctrines of merger and scenes a faire and the words and short phrases exclusion. Id. at 70-71.

The Study recognized that some commentators had raised concerns about overbroad copyright protection for programs; yet, others, it noted, think that expansive protection is needed. Id. at 86-87. The Study concluded that this debate notwithstanding, it would be “premature” to conclude that the risks of overbroad protections were significant as there is “no overlap in subject matter” between copyright and patent. Id. at 88-90. The Study urged Congress to wait and see how the law evolved. Id. at 89.

“At the bottom of this debate,” said the Study, “it appears is the question of protection of functionality….” Id. at 87. It would be contrary to the statutory exclusions set forth in 17 U.S.C. § 102(b) for copyright to protect program functionality. (“In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, principle, or discovery, regardless of the form in which it is described, explained, illustrated or embodied in such work.”) Study at 87. According to the Study, the protection of functionality “is assigned to patents where a much more rigorous test must be undergone and the barriers to entry in terms of time, cost, and complexity, are higher.” Id. at 88.

It is unfortunate that the Federal Circuit did not have access to this Study when deciding the copyrightability issue in the Oracle case, as its conclusions might have given the court pause about invoking the Mazer overlap-endorsing dicta in response to Google’s mutual exclusivity argument.

In a forthcoming article, Functionality and Expression in Computer Programs: Refining the Tests for Software Copyright Infringement, I challenge the Federal Circuit’s conclusion that copyright and utility patent can provide overlapping IP protections for software innovations. The article notes that the Mazer dicta was made in the context of a real, if partial, overlap in copyright and design patent subject matters. Stein’s statuette qualified as a work of art under U.S. copyright law. However, used as the base of a lamp, the design was also eligible for design patent protection as an ornamental design of an article of manufacture.

The Court in Mazer was unequivocal about copyright and utility patents having separate domains. It cited approvingly to two of Baker’s progeny that had held “that the Mechanical Patent Law and Copyright Laws are mutually exclusive,” Mazer, 201 U.S at 215, n.33 (emphasis added). See Taylor Instrument Co. v. Fawley-Brost Co., 139 F.2d 98 (7th Cir. 1943) (no copyright in temperature recording charts because they were integral parts of previously patented machines) and Brown Instrument Co. v. Warner, 161 F.2d 910 (D.C. Cir. 1947) (accord). Overlaps in design patent and copyright subject matters had, by contrast, long been accepted. Mazer, 201 U.S. at 215, n.33.

The exact contours of utility patent and copyright protections for software innovations may not shimmer with clarity, but the 1991 Study adheres to the Supreme Court’s long-standing pronouncements in Baker and Mazer that copyright and utility patent are and should be mutually exclusive. Now if only the Federal Circuit can be made to understand this.