Obviousness

Obviousness Analysis of U.S. Patent 6,546,397

To: File
From: Senior Patent Analyst
Date: May 12, 2026
Subject: Obviousness Analysis of U.S. Patent 6,546,397 in View of Prior Art

1. Introduction

This analysis evaluates the patentability of the claims of U.S. Patent 6,546,397 ("the '397 patent") under 35 U.S.C. § 103, focusing on the doctrine of obviousness. The '397 patent, with a priority date of December 2, 1999, describes a browser-based tool for creating websites. As established in the PTAB challenges section of this file, all claims of the '397 patent have been found unpatentable in multiple inter partes review (IPR) proceedings. This analysis synthesizes and confirms those findings, demonstrating that the claimed invention would have been obvious to a Person Having Ordinary Skill in the Art (POSITA) at the time the invention was made.

A POSITA in late 1999 would have been a web developer or software engineer with knowledge of HTML, JavaScript, and server-side technologies, and familiarity with existing web authoring tools like Adobe PageMill or Microsoft FrontPage.

2. Deconstruction of Independent Claim 1

Claim 1, the sole independent claim, is the focus of this analysis. It can be broken down into the following key elements:

• a) A method for building a web page by a user.
• b) Providing a build tool operable in a web browser.
• c) The build tool comprising a build engine and a user interface.
• d) The user interface presenting a WYSIWYG ("what you see is what you get") representation of the web page.
• e) The user interface receiving user inputs to construct the web page.
• f) The build engine processing the user inputs.
• g) The build engine generating a single run time file and an associated database.
• h) The run time file, when executed, producing the web page.

3. Prior Art References

The successful IPR challenges relied on combinations of several key prior art references available before the December 1999 priority date. This analysis will focus on two such references that are dispositive.

• Lemay et al., "Teach Yourself Web Publishing with HTML 4 in a Week," 4th Ed., 1997 (hereinafter "Lemay"): Lemay is a well-known instructional book that teaches users how to create web pages. It describes the tools and techniques used in web publishing at the time, including WYSIWYG editors like Microsoft FrontPage and Adobe PageMill, which allowed users to build web pages visually without writing raw HTML code. Lemay, therefore, discloses a tool for building a web page with a WYSIWYG user interface (Elements a, d, e).

• U.S. Patent 5,838,906 to Doyle et al., filed October 17, 1994, issued November 17, 1998 (hereinafter "Doyle"): Doyle describes a system for embedding program objects, or "applets," within a hypermedia document (i.e., a web page). The core teaching of Doyle is allowing a user's browser to access and execute an embedded program object, which could be located on a remote server. This discloses the concept of a client-side browser executing a program file received over a network to provide interactive content, which is analogous to the "run time file" of the '397 patent. Doyle teaches packaging functionality into an executable object that is delivered with a web document to provide an interactive user experience.

4. Obviousness Combination: Lemay in View of Doyle

A POSITA would have found it obvious to combine the teachings of Lemay and Doyle to arrive at the invention claimed in the '397 patent.

Mapping of Combination to Claim Elements:

• Elements a, b, c, d, e, f (The Browser-Based WYSIWYG Builder): Lemay explicitly teaches the use of WYSIWYG web authoring tools. These tools inherently comprise a user interface for receiving input (the visual editor) and a build engine (the software that processes the visual inputs and generates the underlying HTML code). While these prior-art tools were often standalone applications rather than purely "browser-based," the concept of applications running within a browser (via Java applets or plugins) was well-established, as shown by Doyle. A POSITA would have recognized the clear advantages of creating a web authoring tool that could run directly in the browser, eliminating the need for separate software installation and improving accessibility. Thus, adapting the known WYSIWYG editor concept from Lemay into a browser-operable format would have been a predictable and obvious step.

• Elements g, h (Generating a Single Run Time File and Database): Lemay's WYSIWYG tools generate static HTML and image files. Doyle teaches the concept of a program object (an applet or "run time file") embedded within a web page that executes on the client-side to provide functionality. A POSITA, seeking to create more dynamic, interactive, and efficiently managed websites than those built with the static tools described by Lemay, would have been motivated to combine these teachings.

Motivation to Combine:

The motivation to combine the WYSIWYG editor of Lemay with the executable object model of Doyle would have been driven by the clear and recognized need to solve problems inherent in late-1990s web development.

1. Efficiency and Portability: Managing websites with dozens of individual HTML files, as produced by the tools in Lemay, was cumbersome. A POSITA would have seen the value in consolidating the site's structure, content, and logic into a more compact, manageable package. Doyle's teaching of embedding program objects provided a blueprint for packaging functionality. Combining these would mean the output of the WYSIWYG tool is not a collection of static files, but a dynamic application (a run time file and its data), making the entire site easier to deploy, update, and manage. This addresses a well-known problem with a predictable solution.

2. Enhanced Functionality: Static HTML pages were limited. The '397 patent itself criticizes conventional HTML and JavaScript for lacking computational power and multimedia capabilities. Doyle explicitly addresses adding enhanced, interactive functionality to web pages via executable applets. A POSITA using a WYSIWYG editor would have naturally sought to incorporate such advanced features (animations, dynamic content scaling, etc.) into the sites they were building. The obvious way to do this would be to have the builder tool generate not just static HTML, but an executable runtime engine as taught by Doyle, which could render these advanced features in the user's browser.

3. Predictable Results: The combination would have yielded no more than predictable results. It was well known that a software tool (the build engine) could process user inputs from a GUI (the user interface) and output code. It was also well known from Doyle and the rise of Java applets that this code could be an executable file that runs in a browser. Combining these two known concepts—a visual editor and a browser-executable runtime—to create a visual website builder that outputs a browser-executable website is a classic example of combining prior art elements according to known methods to yield predictable results.

5. Conclusion

The invention claimed in U.S. Patent 6,546,397 represents an obvious combination of known elements in the prior art. The concept of a WYSIWYG web page editor was well-established (Lemay), and the method of delivering and executing program objects within a web browser to provide dynamic functionality was also known (Doyle). A person of ordinary skill in the art in 1999, facing the known limitations of static HTML and the challenges of managing multi-page websites, would have been motivated to combine these concepts to create a more efficient and powerful browser-based web authoring tool. The resulting invention would have been the predictable implementation of such a combination. Therefore, the claims of the '397 patent are invalid as obvious under 35 U.S.C. § 103. This conclusion is strongly supported by the multiple PTAB Final Written Decisions that reached the same outcome, one of which was summarily affirmed by the Court of Appeals for the Federal Circuit.