Analyst or Advocate:A review of the Eolas rebuttals to the USPTO's office actions with regard to US Patent No. 5,838,906.
I. Introduction
In August 2003, a jury awarded Eolas Technologies Inc. more than $500 million in damages for Microsoft's alleged infringement of US Patent No. 5,838,906. The '906 patent, which covers a method of embedding interactive content in Web pages, is unfortunately the type of patent that contributes to the negative reputation of software patents and, by extension, the USPTO. Moments after the ubiquitous anti-Microsoft celebration ended, the realization sunk in: this is not good for the Web.
In response, Tim Berners-Lee, father of the Web, author of the initial HTTP and HTML specifications and the director of the W3C, and others in the community urged the USPTO to re-examine the patent in light of a set of prior art herein referred to as the Raggett references. Berners-Lee cautioned that the patent would cause "substantial economic and technical damage to the operation of the World Wide Web," the impact of which "...will be felt not only by those who are alleged to directly infringe, but all whose web pages and applications rely on the stable, standards-based operation of browsers threatened by this patent."[1]
Like the '906 patent, the Raggett references teach a method of embedding interactive content in Web pages using interactive external applications. Based upon the Raggett references, the USPTO re-examined the '906 patent and issued an office action that rejected the '906 claims as being unpatentable.
In response, Eolas prepared and submitted rebuttal arguments to the USPTO. The bulk of the technical argument was presented through Dr. Edward Felten, a professor at Princeton and the paid expert for Eolas during the trial. While Dr. Felten framed his arguments in patent jargon, particularly with regard to the understanding of those "having ordinary skill in the art," in reality, the acceptance of his arguments required that one in the art suspend the application of common sense. Moreover, Dr. Felten's arguments as to how one of skill would have understood Dave Raggett's publications seemed directly contrary to how those working on the Web actually did understand Dave Raggett's words at the time of their publication.
Unfortunately, those who were concerned about the impact this patent could have on the Web may have reason to be concerned about the subsequent events in the USPTO. Despite the plain technical disclosures of the Raggett references, the USPTO returned a second office action which, although it upheld the rejection[2] of the '906 patent claims, seemed swayed at least in part by Dr. Felten's arguments. Eolas and Dr. Felten now seek to build on that through another recent filing in the USPTO that again seeks to suspend the application of common sense to any technical analysis. Those who urged this reexamination should be concerned that the USPTO may act upon this one-sided record.
II. Overview
The following is a summary of the main points addressed in the document. The summary outlines each topic in this document, and each topic links to the sections of the document that describe it thoroughly. The intent is that the reader of this document is able to digest the arguments quickly, but at any time may drill down into a given argument to access a more rigorous discussion.
1) Background (Section III) - Patent infringement disputes tend to make things more complicated than they need to be. Because of the potential for confusion, it is often a useful exercise to take a step back from the problem and apply a measure of common sense.
A large portion of Eolas' argument is based on the interactivity provided by the VIS application, however, the external application - including the type and amount of interactivity it provides - is not claimed by the '906 patent.
Interactivity on the Web existed before the '906 patent.
Mosaic helper applications provided the same type and amount of interactivity as well as the ability for the browser to support non-native formats using external applications. The difference between helper applications and the '906 patent was simply where the output of the programs was displayed.
Methods for embedding interactive objects were well
known in 1993.
Raggett teaches a method for object level embedding enabling the in-line display of foreign data formats without modification of the browser.
Raggett teaches an EMBED tag, including a type attribute identical to that described in the '906 patent.
Raggett teaches the use of external applications to provide interactivity with embedded objects.
Those of skill in the art understood the teachings of Raggett as a method to embed fully interactive content within Web pages.
Methods for displaying the output of applications in
any window, as well as methods for any client program to reparent another
client program's main window inside of its own window were functions of the
X-Window system and were present since its inception in 1984. Furthermore,
these methods were used by programs in and before 1993.
Mark Andreessen proposed using external applications to embed MIME documents in browser windows in 1993, including embedded controls that enabled interactivity with the embedded object.
Those of skill in the art understood the potential to
embed interactive content such as drawing objects, animations, spreadsheets,
message objects, and clickable areas within images.
2) Felten I (Section IV) - The Felten I declaration presents two major arguments in an attempt to convince the USPTO that the first office action is incorrect and the '906 patent should stand. First, Dr. Felten contends that the Raggett references are a "slight" extension of Berners-Lee's ability to display static images, and therefore teach away from interactivity.[3] Second, he argues that Raggett doesn't teach interactivity within a browser window, and that this type of interactivity is claimed by the '906 patents.[4]
Browsers in this time period provided the same level and types of interactivity as the '906 invention. Simply placing the output of external applications in the browser window did not change the level of interactivity on the Web.
The '906 patent claims were adjusted to distinguish the invention from existing interactivity on the Web. The limitations that the application providing interactive processing must be external to the browser, running on the client computer, and display its output within the browser window were added to overcome forms, scripts, and helper applications.
Interactivity within Web browsers was known in 1993.
Dr. Felten describes Mosaic's ability to launch an external HTML editor in order to edit the contents of a Web page. His argument is misleading; the external application must enable interactive processing with the embedded object, not the Web page itself.
Dr. Felten is also incorrect in asserting that there
was no realistic way to edit a Web page from a client workstation. This
technology existed in 1993 and is a popular feature of the Web today.
The use of static images, including rendering an image of an object server-side, does not preclude interactivity.
Dr. Felten misleadingly applies the term static to the input and output of the external application without regard to the fact that the '906 invention uses the same "static" object data and image data.
The '906 patent does not claim enabling interactive
processing of the embedded object by clicking the object's display window
inside the browser.
The Raggett references teach provision of interactivity within a browser window, support for non-native data types using external applications, addition of support for new types without modifying the browser, and the use of the EMBED tag, including MIME content-type information.
Dr. Felten's arguments against Raggett describing server-side rendering are misleading; his arguments against Raggett also describe how the '906 invention works.
Although Dr. Felten declares the provision of "Rich Interactivity," a differentiator, the type and level of interactivity and the external application providing that interactivity are not claimed by the '906 patent.
Embedding interactive content and enabling interactivity within the browser window was well known by those of skill in the art.
Contrary to Dr. Felten's declaration that Berners-Lee
was never implemented, Mosaic, admitted prior art, embodies the portions of
the Berners-Lee reference that pertain to the '906 patent.
Dr. Felten's argument that Raggett teaches away from interactivity is based on highly-selective definitions of the terms filter, render, and return.
Filters do not preclude interactivity.
Filtering is consistent with the '906 patent.
Although Dr. Felten limits his discussion to filters, Raggett taught DLLs, shared libraries, and separate programs in addition to filters.
The use of the terms "render" and "static images" do not preclude interactivity. In fact, they are consistent with the '906 patent.
Dr. Felten defines "return" in a manner other than that known in the art. "Returning" a rendered image does not preclude interactivity, and is consistent with the '906 invention.
Raggett teaches embedded interactivity, as well as types of "non-static" data such as MPEG movies. This was understood by those of skill in the art.
Dr. Felten falsely declares that interactivity must be
provided with the embedded object.
It is not important whether or not Raggett was implemented; it was disclosed to, and well understood by, those in the field. Furthermore, '906 patent admits that implementing these features is conventional and within the ability of a person of skill in the art.
One of skill would not implement Raggett to handle only single frame image data. Raggett teaches supporting content types registered in the MIME database. An implementer would implement a type-agnostic support mechanism to handle any MIME-compliant data and be general enough to accommodate future MIME data. The Raggett references support this statement by describing APIs and binding and calling mechanisms.
At the time, MPEG movies were a registered MIME content type, so an implementer would at least include support for multi-frame MPEG movies.
These ideas were understood by those of skill in the
art.
Raggett teaches more than the ability to embed equations and postscript documents. Raggett teaches support for data types specified by MIME content types. At the time, MIME included support for more applications than eqn and postscript, and also specified that a MIME compliant application should be scalable to accommodate future registered MIME types.
Dr. Felten misleadingly describes the importance of
windows DLLs and inter-process communication. The model he describes as an
argument against Raggett is consistent with the invention described in the'906
patent.
3) Felten II (Section V) - Dr. Felten declares that the combination of the Berners-Lee and Raggett references does not teach the claim element of automatically invoking an executable application to enable interactive processing. He is incorrect. Furthermore, the Toye reference also teaches this claim element.
Dr. Felten misleadingly restricts Berners-Lee to "static pages." In reality, an implementation of Berners-Lee, Mosaic, provided the same type and level of interactivity as the '906 patent.
Dr. Felten misleadingly defines "distributed hypermedia environment" to support a future argument that Toye does not teach a hypermedia environment.
Dr. Felten misleadingly restricts hyperlinks to
"simple, unidirectional hyperlinks" to support a future argument that Toye
does not teach a hypermedia browser. Hyperlinks are not limited in direction.
Furthermore, the '906 patent does not claim any kind of hyperlink.
c) Toye (Section V.c) - Assuming that the Raggett references lack the claim element of automatically invoking an executable application to enable interactive processing of an embedded object, the '906 invention is unpatentable over a combination of Berners-Lee, Raggett I, Raggett II, and Toye. Any arguments against Toye that don't pertain to this claim element are irrelevant, as they are taught by the Berners-Lee and Raggett references.
Use of centralized servers for content storage is consistent with the idea of a distributed environment. For example, Web sites may be located on a single server, but it is the presence of disparate servers that makes the Web a distributed environment.
Toye does teach distributed documents within distributed hypermedia environments.
This claim element is taught by Berners-Lee and
Raggett.
Dr. Felten's argument is misleading. It does not matter that Toye teaches more than the claims, the fact is that it teaches enabling interactive processing of an embedded object.
Furthermore, the goal of NoteMail, "a tool for
organizing, manipulating, and viewing information on the Internet. Foreseeable
enhancements include: a low level hypermedia browser... and a simple pen-based
interface for manipulating objects" is consistent with the '906 patent.
The Toye reference teaches automatic invocation to display the embedded object. As stated by Dr. Felten in his testimony, the patent does not claim that interactivity must be provided without a mouse click.
Toye's method of interactive processing is consistent with the '906 patent.
Toye supports "seamless embedding" which Dr. Felten
referred to as a principal benefit of the '906 patent.