Eolas Technologies Incorporated v. Adobe Systems Incorporated et al

Filing 1348

Additional Attachments to Main Document: 1347 Order,.. (Attachments: # 1 Exhibit C to 1342 (Part 2 of 17), # 2 Exhibit C to 1342 (Part 3 of 17), # 3 Exhibit C to 1342 (Part 4 of 17), # 4 Exhibit C to 1342 (Part 5 of 17), # 5 Exhibit C to 1342 (Part 6 of 17), # 6 Exhibit C to 1342 (Part 7 of 17), # 7 Exhibit C to 1342 (Part 8 of 17), # 8 Exhibit C to 1342 (Part 9 of 17), # 9 Exhibit C to 1342 (Part 10 of 17), # 10 Exhibit C to 1342 (Part 11 of 17), # 11 Exhibit C to 1342 (Part 12 of 17), # 12 Exhibit C to 1342 (Part 13 of 17), # 13 Exhibit C to 1342 (Part 14 of 17, # 14 Exhibit C to 1342 (Part 15 of 17), # 15 Exhibit C to 1342 (Part 16 of 17), # 16 Exhibit C to 1342 (Part 17 of 17)(Doan, Jennifer)

CLAIM CHART EXHIBIT 4
"VIOLA-FEB BETA"

INVALIDITY CLAIM CHART FOR U.S. PATENT NO. 5,838,906


VIOLA FEBRUARY BETA, DATED FEBRUARY 23, 1994 [PA-NAT-78\VIOLA\1994-02-23 FEBRUARY BETA RELEASE - EX AG TO
INV CONTENTIONS], (“VIOLA-FEB BETA”). THE BODY OF MY REPORT HAS A NARRATIVE DESCRIPTION THAT AUGMENTS AND
SHOULD BE CONSIDERED PART OF THIS CHART, AND VISE-VERSA FOR THIS AND ALL MY CHARTS.

Note: Reference is made in this chart to the files "link.html" and "vobjf.html." These are files that I am appending along with this
report and which I used in Viola Video 21. (See Appendix C.) Link.html and vobjf.html can be found on the accompanying DVD of
Video Exhibits, in the Related Materials subdirectory, under the folder for Viola Video 21.
Claim Text from ’906 Patent
906-1.a:
A method for running an application program in a
computer network environment, comprising:

Viola-Feb Beta
Viola-Feb Beta discloses an application program. See, e.g., :
ViolaWWW is a web browser computer program that was implemented
using the Viola toolkit/language system. (See, e.g.,
viola\www\objs\www.v, viola\violadocs\vw\about.html.)
By way of example, Viola's documentation states that “ViolaWWW is an
X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a computer network environment. See, e.g., :

906-1.b:
providing at least one client workstation and one
network server coupled to said network
environment, wherein said network environment is

ViolaWWW operates in a computer network environment, including local
area networks or the World Wide Web. ViolaWWW operates in computer
network environment consisting of clients and servers wherein a server —
such as a file server or HTTP server — publishes hypermedia documents
such as HMML and HTML files to client workstations. As Viola's
documentation notes, “ViolaWWW is an X-Windows World Wide Web
browser.” (See, e.g., viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a client workstation. See, e.g., :
ViolaWWW operated on a client workstation. By way of example,
ViolaWWW executed on Sun SPARCstations running a SunOS operating

1

Claim Text from ’906 Patent
a distributed hypermedia environment;

Viola-Feb Beta
system. This client workstation could interoperate with servers, such as
file servers or HTTP servers. Viola's documentation notes that
“ViolaWWW is an X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a network server. See, e.g., :
ViolaWWW operated with network servers. Viola's documentation notes
that “ViolaWWW is an X-Windows World Wide Web browser.” (See,
e.g., viola\violadocs\vw\about.html.) Servers that ViolaWWW operate
with include file servers or HTTP servers. These servers transmit
hypermedia documents, such as HMML or HTML files, and a client
workstation running ViolaWWW receives them.
Viola-Feb Beta discloses a distributed hypermedia environment. See, e.g., :

906-1.c:
executing, at said client workstation, a browser
application, that parses a first distributed
hypermedia document to identify text formats
included in said distributed hypermedia document
and for responding to predetermined text formats
to initiate processing specified by said text
formats;

ViolaWWW operates in a distributed hypermedia environment, including
local area networks or the World Wide Web. ViolaWWW operates in
computer network environment consisting of clients and servers wherein a
server — such as a file server or HTTP server — publishes hypermedia
documents such as HMML and HTML files to client workstations. As
Viola's documentation notes, “ViolaWWW is an X-Windows World Wide
Web browser.” (See, e.g., viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a browser application. See, e.g., :
ViolaWWW is a web browser computer program that was implemented
using the Viola toolkit/language system. (See, e.g.,
viola\www\objs\www.v, viola\violadocs\vw\about.html.)
By way of example, Viola's documentation states that “ViolaWWW is an
X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)

2

Claim Text from ’906 Patent

Viola-Feb Beta
Viola-Feb Beta discloses that the browser application parses a hypermedia
document. See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
document files (i.e., HTML and HMML documents) that contain enabling
information from a network server (e.g., a file server or HTTP server) over
a distributed hypermedia network environment. Examples of such
documents include those in viola\violadocs\vw.
The hypermedia document files received from the network server contain
predetermined text formats which enable a browser application to display
at least a portion of a distributed hypermedia document within a browsercontrolled window. For example, the hypermedia documents downloaded
by ViolaWWW may contain HMML tags or HTML tags. In particular,
the about.html hypermedia document contains the HTML tags (i.e., text
formats) TITLE, H2 and P. (See, e.g., about.html.) As another example,
the testAll.html file contains HTML tags, such as TITLE and H1.
The hypermedia document downloaded from the remote network server is
parsed by ViolaWWW to identify the tags. ViolaWWW then initiates
processing specified by the tags. For example, ViolaWWW displays the
text marked by the H1 tag in large, bold, header text and the text marked
by the ITALIC tag in italics. (See, e.g., www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v, and src\viola\sgml.c,
viola\src\libWWW.)
Viola-Feb Beta discloses a hypermedia document with text formats. See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
document files (i.e., HTML and HMML documents) that contain enabling
information from a network server (e.g., a file server or HTTP server) over
a distributed hypermedia network environment. Examples of such
documents include those in viola\violadocs\vw.
The hypermedia document files received from the network server contain

3

Claim Text from ’906 Patent

906-1.d:
utilizing said browser to display, on said client
workstation, at least a portion of a first hypermedia
document received over said network from said
server,

Viola-Feb Beta
predetermined text formats which enable a browser application to display
at least a portion of a distributed hypermedia document within a browsercontrolled window. For example, the hypermedia documents downloaded
by ViolaWWW may contain HMML tags or HTML tags. In particular,
the about.html hypermedia document contains the HTML tags (i.e., text
formats) TITLE, H2 and P. (See, e.g., about.html.) As another example,
the testAll.html file contains HTML tags, such as TITLE and H1.
The hypermedia document downloaded from the remote network server is
parsed by ViolaWWW to identify the tags. ViolaWWW then initiates
processing specified by the tags. For example, ViolaWWW displays the
text marked by the H1 tag in large, bold, header text and the text marked
by the ITALIC tag in italics. (See, e.g., www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v, and src\viola\sgml.c,
viola\src\libWWW.)
Viola-Feb Beta discloses that a hypermedia document is received from the
server. See, e.g., :
A client workstation running the ViolaWWW browser receives
hypermedia documents from a server. Examples of servers from which
ViolaWWW receives hypermedia documents include file servers or HTTP
servers. Examples of documents that ViolaWWW receives can be found
in viola\violadocs\vw folder, and include brief.html, about.html and
violaWWWDemo.html. Code files evidencing ViolaWWW's ability to
retrieve documents from servers include www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v and src\viola\cl_generic.c.
Viola-Feb Beta discloses that the browser displays a hypermedia document. See,
e.g., :
ViolaWWW displays hypermedia documents, including HMML and
HTML hypermedia documents. Examples of hypermedia HTML
documents that ViolaWWW displayed — either by retrieving them from a

4

Claim Text from ’906 Patent

906-1.e:
wherein the portion of said first hypermedia
document is displayed within a first browsercontrolled window on said client workstation,

906-1.f:
wherein said first distributed hypermedia
document includes an embed text format, located
at a first location in said first distributed
hypermedia document, that specifies the location
of at least a portion of an object external to the first
distributed hypermedia document,

Viola-Feb Beta
local directory or retrieving them from a server location — are stored in
viola\violadocs\vw, such as brief.html, about.html,
violaWWWDemo.html. ViolaWWW could display other hypermedia
documents as well.
ViolaWWW displays HTML and HMML documents by parsing them to
identify HMML or HTML tags, and then initiates processing specified by
the tags and displays the hypermedia document. For example,
ViolaWWW will display the text marked by the H1 tag in large, bold,
header text and the text marked by the ITALIC tag in italics. Other tags
are discussed in more detail elsewhere in this chart.
Viola-Feb Beta discloses that a hypermedia document is displayed in a browser
window. See, e.g., :
ViolaWWW displays hypermedia documents, including HMML and
HTML hypermedia documents. Examples of hypermedia HTML
documents that ViolaWWW displayed — either by retrieving them from a
local directory or retrieving them from a server location — are stored in
viola\violadocs\vw, such as brief.html, about.html,
violaWWWDemo.html. ViolaWWW could display other hypermedia
documents as well.
ViolaWWW displays HTML and HMML documents by parsing them to
identify HMML or HTML tags, and then initiates processing specified by
the tags. The documents are displayed in the ViolaWWW browser
window.
Viola-Feb Beta discloses an embed text format at a first location in a hypermedia
document. See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
documents (e.g., HTML and HMML documents) from a network server
(e.g., a file server or HTTP server) over the distributed hypermedia
network environment. The hypermedia document received from the
network server contains text formats which enable a browser application

5

Claim Text from ’906 Patent

Viola-Feb Beta
to display at least a portion of a distributed hypermedia document within a
browser-controlled window. These text formats include embed text
formats. For example, an HTML file can include an embed text format
called VOBJF or LINK tag with REL attribute as vobj. (See, e.g.,
viola\violadocs\vw\brief.html; viola\violadocs\vw\about.html; vobjf.html;
violadocs\vwtests\testSocket.html; link.html.) The VOBJF text format is
located at a first location in its hypermedia document. (See vobjf.html.)
Similarly, LINK text format with REL attribute as vobj is located at a first
location in its hypermedia document. (See link.html).
Viola-Feb Beta discloses that the embed text format specifies the location of an
object. See, e.g., :
The VOBJF embed text format and LINK text format with REL attribute
as vobj specify the location of an object.
For example, vobjf.html includes a VOBJF tag that shows the tag's syntax,
including that it specifies the location of an object based on a filepath
location in which the object can be found:
<VOBJF HREF=http://ncsaserver/WEI/plot.v >
(See vobjf.html.)
As another example, link.html includes a LINK tag with REL attribute as
vobj that shows the tag’s syntax, including that it spevidies the location of
an object based on a filepath location in which the object can be found:
<LINK REL=“vobj” HREF= http://ncsaserver/WEI/plot.v >
(See link.html.)
Viola-Feb Beta discloses an object that is external to a hypermedia document.
See, e.g., :
In one example, when a Viola applet is embedded in a ViolaWWW web
page, using the VOBJF tag or LINK tag with REL attribute as vobj, at

6

Claim Text from ’906 Patent

906-1.g:
wherein said object has type information
associated with it utilized by said browser to
identify and locate an executable application
external to the first distributed hypermedia
document, and

Viola-Feb Beta
least a portion of an object external to a hypermedia document, the default
grid, appears in the ViolaWWW window upon browser launch.
The data for the default grid is specified in the file plot.v by the command:
output("equation 0");
(See violadocs\objs\plot.v.)
Viola-Feb Beta discloses that the object has associated type information. See,
e.g., :
For example, the file plot.v contains type information associated with the
object.
/path{/usr/work/vplot/vplot}
(See viola\violadocs\objs\plot.v.)
The type information is used by the ViolaWWW to identify and locate the
vplot executable application.
switch (pid = vfork()) {
…
case 0: \* Child *\
…
execv(GET_path(self), args);
(See src\viola\cl_TTY.c.)
Viola-Feb Beta discloses that the browser uses type information to identify and
locate an executable application. See, e.g., :
For example, the file plot.v contains type information associated with the
object.
/path{/usr/work/vplot/vplot}
(See viola\violadocs\objs\plot.v.)
The type information is used by the ViolaWWW to identify and locate the
vplot executable application. ViolaWWW then invokes the executable
application.
switch (pid = vfork()) {

7

Claim Text from ’906 Patent

Viola-Feb Beta
…
case 0: \* Child *\
…
execv(GET_path(self), args);
(See viola\src\viola\cl_TTY.c.)
Viola-Feb Beta discloses that the executable application is external to the
hypermedia document. See, e.g., :

906-1.h:
wherein said embed text format is parsed by said
browser to automatically invoke said executable
application to execute on said client workstation in
order to display said object and enable an end-user
to directly interact with said object within a
display area created at said first location within the
portion of said first distributed hypermedia
document being displayed in said first browsercontrolled window.

For example, the vplot executable application is external to the vobjf.html
and link.html hypermedia documents. (See, e.g., vobjf.html, link.html.)
Thus, vplot is external to the hypermedia document. (See, e.g., PA-NAT00000078\vplot\)
Viola-Feb Beta discloses that the browser parses the embed text format. See,
e.g., :
The file containing enabling information is downloaded from the remote
network server and parsed by ViolaWWW to identify the text formats.
ViolaWWW then initiates processing specified by the text formats. For
example, ViolaWWW displays the text marked by the H1 tag in large,
bold, header text and the text marked by the ITALIC tag in italics. (See,
e.g., www\objs\VWHandler_hmml.v, www\objs\VWHandler_html2.v,
and src\viola\sgml.c, viola\src\libWWW.)
For hypermedia documents containing embed text formats, these embed
text formats are likewise identified by parsing the file. For example, when
parsing about.html or brief.html or vobjf.html, violaWWW identifies the
VOBJF tag while parsing. Similarly, when parsing testSocket.html or
link.html, violaWWW identifies the LINK tag with REL attribute as vobj
while parsing. (See, e.g., www\objs\VWHandler_html2.v,
src\viola\sgml.c, sgml\objs\HMML_vobjf.v, sgml\objs\HTML_vobjf.v,
sgml\objs\HTML_link.v, viola\src\libWWW,
viola\violadocs\vw\brief.html; viola\violadocs\vw\about.html; vobjf.html;

8

Claim Text from ’906 Patent

Viola-Feb Beta
violadocs\vwtests\testSocket.html; link.html.)
Viola-Feb Beta discloses automatic invocation of the executable application.
See, e.g., :
When ViolaWWW parses the VOBJF tag or LINK tag with REL attribute
as vobj, it automatically invokes the vplot executable application. The
automatic invocation does not require action by the user.
For example, when ViolaWWW parses the VOBJF tag in vobjf.html or
LINK tag with REL attribute as vobj in link.html, the vplot application is
automatically invoked as follows:
switch (pid = vfork()) {
…
case 0: \* Child *\
…
execv(GET_path(self), args);
(See src\viola\cl_TTY.c.)
Viola-Feb Beta discloses that the executable application displays the object. See,
e.g., :
For example, the vplot application displays the object as a grid inside the
ViolaWWW window that is displaying vobjf.html or link.html. The
object is displayed at the location in the window corresponding to the
VOBJF tag or LINK tag with REL attribute as vobj. (See vobjf.html,
link.html.)
Viola-Feb Beta discloses that the executable application enables direct
interaction with the object. See, e.g., :

9

Claim Text from ’906 Patent

Viola-Feb Beta
For example, the vplot executable application enables the user to directly
interact with the object using the slider bars to rotate the object around the
X, Y and Z axes. (See, e.g., viola\violadocs\objs\plot.v,
src\viola\cl_slider.c, src\viola\cl_client.c.)
Viola-Feb Beta discloses that interaction with the object is at a first location in
the hypermedia document. See, e.g., :
For example, the vplot executable application enables the user to directly
interact with the object using the slider bars to rotate the object around the
X, Y and Z axes. (See, e.g., viola\violadocs\objs\plot.v,
src\viola\cl_slider.c, src\viola\cl_client.c.) This interaction with the object
occurs at the first location within the portion of the HTML document
displayed in the ViolaWWW window. (See, e.g., vobjf.html, link.html,
violadocs\objs\plot.v)

906-2.a:
The method of claim 1, wherein said executable
application is a controllable application and further
comprising the step of: interactively controlling
said controllable application on said client
workstation via inter-process communications
between said browser and said controllable
application.

Viola-Feb Beta discloses interactive control via inter-process communications
between a browser and an application. See, e.g., :
ViolaWWW browser can communicate with an application using interprocess communication. As noted in Viola's documentation, “Viola is
message driven, and messages may be generated by a number of sources.
A message is typically caused by the user interacting with a graphical user
interface object, but it could also be generated by other objects, or by a
timer facility. Through a communication facility such as the socket, a
message may also be generated from another process on the network.”
(See violadocs/vw/brief.html.)
“The Viola language/toolkit system provides an environment where
applications are composed of groups of objects, where objects interact, by
message passing, with the user and with each other.” (See
violadocs/vw/brief.html.)

10

Claim Text from ’906 Patent

906-3.a:
The method of claim 2, wherein the
communications to interactively control said
controllable application continue to be exchanged
between the controllable application and the
browser even after the controllable application
program has been launched.

Viola-Feb Beta
In one example, the ViolaWWW browser communicates with vplot using
inter-process communication. (See, e.g., viola\violadocs\objs\plot.v,
viola\src\viola\cl_TTY.c.) (See also main.c of vplot source code,
available at, e.g., PA-NAT00000078\vplot\MS_SUPP_1205_001\petra\vplot.)
Viola-Feb Beta discloses ongoing inter-process communications. See, e.g., :
ViolaWWW browser can communicate with an application using interprocess communication. As noted in Viola's documentation, “Viola is
message driven, and messages may be generated by a number of sources.
A message is typically caused by the user interacting with a graphical user
interface object, but it could also be generated by other objects, or by a
timer facility. Through a communication facility such as the socket, a
message may also be generated from another process on the network.”
(See violadocs/vw/brief.html.)
“The Viola language/toolkit system provides an environment where
applications are composed of groups of objects, where objects interact, by
message passing, with the user and with each other.” (See
violadocs/vw/brief.html.)
In one example, the ViolaWWW browser communicates with vplot using
inter-process communication. (See, e.g., viola\violadocs\objs\plot.v,
viola\src\\viola\cl_TTY.c.) (See also main.c of vplot source code,
available at, e.g., PA-NAT00000078\vplot\MS_SUPP_1205_001\petra\vplot.) In this example, an
end-user can continue interacting with an object, such as the default grid,
in an ongoing basis using the slider bars to rotate the object around the X,
Y and Z axes. (See, e.g., viola\apps\plot.v, src\cl_slider.c, src\cl_client.c.)
These interactions are communicated between the browser and the vplot
executable eapplication on an ongoing basis so that vplot can process
those interactions.

11

Claim Text from ’906 Patent
906-6.a:
A computer program product for use in a system
having at least one client workstation and one
network server coupled to said network
environment, wherein said network environment is
a distributed hypermedia environment, the
computer program product comprising:
906-6.b:
a computer usable medium having computer
readable program code physically embodied
therein, said computer program product further
comprising:

906-6.c:
computer readable program code for causing said
client workstation to execute a browser application
to parse a first distributed hypermedia document to
identify text formats included in said distributed
hypermedia document and to respond to
predetermined text formats to initiate processes
specified by said text formats;
906-6.d:
computer readable program code for causing said
client workstation to utilize said browser to
display, on said client workstation, at least a
portion of a first hypermedia document received

Viola-Feb Beta
Viola-Feb Beta discloses an application program in a computer network
environment. See evidence recited for 906-1.a.
Viola-Feb Beta also discloses a client workstation and a network server in a
distributed hypermedia environment. See evidence recited for 906-1.b.
Viola-Feb Beta discloses computer code physically embodied on a medium.
See, e.g., :
The computer on which ViolaWWW executes includes computer usable
media having computer readable program code physically embodied
therein. By way of example, ViolaWWW executed on Sun
SPARCstations running a SunOS operating system. ViolaWWW could be
executed on the Sun SPARCstation with the command “viola –o www.”
Viola, including the www.v file that implements the ViolaWWW browser,
contains computer readable code that is stored on the SPARCstation's
computer usable media.
Viola-Feb Beta discloses a browser application that parses a hypermedia
document with text formats and responds to predetermined text formats to
initiate processing specified by the text formats. See evidence recited for 9061.c.

Viola-Feb Beta discloses a hypermedia document received from a server and a
browser that displays the hypermedia document. See evidence recited for 9061.d.

12

Claim Text from ’906 Patent
over said network from said server,
906-6.e:
wherein the portion of said first hypermedia
document is displayed within a first browsercontrolled window on said client workstation,
906-6.f:
wherein said first distributed hypermedia
document includes an embed text format, located
at a first location in said first distributed
hypermedia document, that specifies the location
of at least a portion of an object external to the first
distributed hypermedia document,
906-6.g:
wherein said object has type information
associated with it utilized by said browser to
identify and locate an executable application
external to the first distributed hypermedia
document, and
906-6.h:
wherein said embed text format is parsed by said
browser to automatically invoke said executable
application to execute on said client workstation in
order to display said object and enable an end-user
to directly interact with said object within a
display area created at said first location within the
portion of said first distributed hypermedia
document being displayed in said first browsercontrolled window.

Viola-Feb Beta
Viola-Feb Beta discloses that the hypermedia document is displayed in a
browser window. See evidence recited for 906-1.e.
Viola-Feb Beta discloses an embed text format at a first location in a hypermedia
document; that the embed text format specifies the location of an object; and that
the object is external to the hypermedia document. See evidence recited for 9061.f.

Viola-Feb Beta discloses that the object has associated type information, that the
browser uses the type information to identify and locate an executable
application, and that the executable application is external to the hypermedia
document. See evidence recited for 906-1.g.
Viola-Feb Beta discloses that the browser parses the embed text format; that the
browser automatically invokes the executable application; that the executable
application displays the object and enables an end-user to directly interact with
it; and that interaction with the object is at a first location in the hypermedia
document. See evidence recited for 906-1.h.

906-7.a:
Viola-Feb Beta discloses interactive control via inter-process communications
The computer program product of claim 6, wherein between a browser and an application. See evidence recited for 906-2.a.
said executable application is a controllable

13

Claim Text from ’906 Patent
application and further comprising:
computer readable program code for causing said
client workstation to interactively control said
controllable application on said client workstation
via inter-process communications between said
browser and said controllable application.

Viola-Feb Beta

906-8.a:
Viola-Feb Beta discloses ongoing inter-process communications. See evidence
The computer program product of claim 7, wherein recited for 906-3.a.
the communications to interactively control said
controllable application continue to be exchanged
between the controllable application and the
browser even after the controllable application
program has been launched.
906-11.a:
The method of claim 3, wherein additional
instructions for controlling said controllable
application reside on said network server, wherein
said step of interactively controlling said
controllable application includes the following
substeps:

Viola-Feb Beta discloses additional instructions on the server See, e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, additional instructions would reside on the server.
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with any distributed application, including VIS.
ViolaWWW works with a distributed application in the same way that it

14

Claim Text from ’906 Patent
906-11.b:
issuing, from the client workstation, one or more
commands to the network server;

Viola-Feb Beta
works with an executable application on the client workstation
Viola-Feb Beta discloses that the client issues commands to the server. See,
e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, the client would issue commands to the server. These facilities
provide for a client issuing commands to a server.

906-11.c:
executing, on the network server, one or more
instructions in response to said commands;

Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with any distributed application, including VIS.
ViolaWWW works with a distributed application in the same way that it
works with an executable application on the client workstation
Viola-Feb Beta discloses that the server executes instructions in response to
client commands. See, e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed

15

Claim Text from ’906 Patent

906-11.d:
sending information from said network server to
said client workstation in response to said executed
instructions; and

906-11.e:

Viola-Feb Beta
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, the server would execute in response to commands from the client.
These facilities provide for a server executing in response to the comments
from the client.
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with any distributed application, including VIS.
ViolaWWW works with a distributed application in the same way that it
works with an executable application on the client workstation.
Viola-Feb Beta discloses that the server responds with information to the client.
See, e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, the server would respond with information to the client. These
facilities provide for the server responding to the command issued by the
client with information to the client.
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with distributed applications such as VIS.
ViolaWWW works with a distributed application in the same way that it
works with an executable application on the client workstation.
Viola-Feb Beta discloses that the client uses information from the server to

16

Claim Text from ’906 Patent
processing said information at the client
workstation to interactively control said
controllable application.

Viola-Feb Beta
interactively control the application. See, e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, the client would use information from the server to control the
application. These facilities provide for the server responding to the
command issued by the client with information to the client. The client
can then use that information to control the executable application.
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with distributed applications such as VIS.
ViolaWWW works with a distributed application in the same way that it
works with an executable application on the client workstation

906-13.a:
The computer program product of claim 8, wherein
additional instructions for controlling said
controllable application reside on said network
server, wherein said computer readable program
code for causing said client workstation to
interactively control said controllable application
on said client workstation includes:
906-13.b:
computer readable program code for causing said

Viola-Feb Beta discloses additional instructions on the server See evidence
recited for 906-11.a.

Viola-Feb Beta discloses that the client issues commands to the server. See
evidence recited for 906-11.b.

17

Claim Text from ’906 Patent
client workstation to issue from the client
workstation, one or more commands to the
network server;
906-13.c:
computer readable program code for causing said
network server to execute one or more instructions
in response to said commands;
906-13.d:
computer readable program code for causing said
network sever to send information to said client
workstation in response to said executed
instructions; and
906-13.e:
computer readable program code for causing said
client workstation to process said information at
the client workstation to interactively control said
controllable application.

Viola-Feb Beta

Viola-Feb Beta discloses that the server executes instructions in response to
client commands. See evidence recited for 906-11.c.
Viola-Feb Beta discloses that the server responds with information to the client.
See evidence recited for 906-11.d.

Viola-Feb Beta discloses that the client uses information from the server to
interactively control the application. See evidence recited for 906-11.e.

18

INVALIDITY CLAIM CHART FOR U.S. PATENT NO. 7,599,985


VIOLA FEBRUARY BETA, DATED FEBRUARY 23, 1994 [PA-NAT-78\VIOLA\1994-02-23 FEBRUARY BETA RELEASE - EX AG TO
INV CONTENTIONS], (“VIOLA-FEB BETA”). THE BODY OF MY REPORT HAS A NARRATIVE DESCRIPTION THAT AUGMENTS AND
SHOULD BE CONSIDERED PART OF THIS CHART, AND VISE-VERSA FOR THIS AND ALL MY CHARTS.

Claim Text from ’985 Patent
985-1.a:
A method for running an application program in a
distributed hypermedia network environment,
wherein the network environment comprises at
least one client workstation and one network
server coupled to the network environment, the
method comprising:

Viola-Feb Beta
Viola-Feb Beta discloses an application program. See, e.g., :
ViolaWWW is a web browser computer program that was implemented
using the Viola toolkit/language system. (See, e.g.,
viola\www\objs\www.v, viola\violadocs\vw\about.html.)
By way of example, Viola's documentation states that “ViolaWWW is an
X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a distributed hypermedia environment. See, e.g., :
ViolaWWW operates in a distributed hypermedia environment, including
local area networks or the World Wide Web. ViolaWWW operates in
computer network environment consisting of clients and servers wherein a
server — such as a file server or HTTP server — publishes hypermedia
documents such as HMML and HTML files to client workstations. As
Viola's documentation notes, “ViolaWWW is an X-Windows World Wide
Web browser.” (See, e.g., viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a client workstation. See, e.g., :
ViolaWWW operated on a client workstation. By way of example,
ViolaWWW executed on Sun SPARCstations running a SunOS operating
system. This client workstation could interoperate with servers, such as

19

Claim Text from ’985 Patent

Viola-Feb Beta
file servers or HTTP servers. Viola's documentation notes that
“ViolaWWW is an X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a network server. See, e.g., :
ViolaWWW operated with network servers. Viola's documentation notes
that “ViolaWWW is an X-Windows World Wide Web browser.” (See,
e.g., viola\violadocs\vw\about.html.) Servers that ViolaWWW operate
with include file servers or HTTP servers. These servers transmit
hypermedia documents, such as HMML or HTML files, and a client
workstation running ViolaWWW receives them.
Viola-Feb Beta discloses a distributed hypermedia environment. See, e.g., :

985-1.b:
receiving, at the client workstation from the
network server over the network environment, at
least one file containing information to enable a
browser application to display at least a portion of
a distributed hypermedia document within a
browser-controlled window;

ViolaWWW operates in a distributed hypermedia environment, including
local area networks or the World Wide Web. ViolaWWW operates in
computer network environment consisting of clients and servers wherein a
server — such as a file server or HTTP server — publishes hypermedia
documents such as HMML and HTML files to client workstations. As
Viola's documentation notes, “ViolaWWW is an X-Windows World Wide
Web browser.” (See, e.g., viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a browser application. See, e.g., :
ViolaWWW is a web browser computer program that was implemented
using the Viola toolkit/language system. (See, e.g.,
viola\www\objs\www.v, viola\violadocs\vw\about.html.)
By way of example, Viola's documentation states that “ViolaWWW is an
X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses a file containing enabling information. See, e.g., :

20

Claim Text from ’985 Patent

Viola-Feb Beta
ViolaWWW running on the client workstation can receive hypermedia
document files (i.e., HTML and HMML documents) that contain enabling
information from a network server (e.g., a file server or HTTP server) over
a distributed hypermedia network environment. Examples of such
documents include those in viola\violadocs\vw.
The hypermedia document files received from the network server contain
predetermined text formats which enable a browser application to display
at least a portion of a distributed hypermedia document within a browsercontrolled window. For example, the hypermedia documents downloaded
by ViolaWWW may contain HMML tags or HTML tags. In particular,
the about.html hypermedia document contains the HTML tags (i.e., text
formats) TITLE, H2 and P. (See, e.g., about.html.) As another example,
the testAll.html file contains HTML tags, such as TITLE and H1.
The hypermedia document downloaded from the remote network server is
parsed by ViolaWWW to identify the tags. ViolaWWW then initiates
processing specified by the tags. For example, ViolaWWW displays the
text marked by the H1 tag in large, bold, header text and the text marked
by the ITALIC tag in italics. (See, e.g., www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v, and src\viola\sgml.c,
viola\src\libWWW.)
Viola-Feb Beta discloses that the file is received at the client workstation from
the network server. See, e.g., :
A client workstation running the ViolaWWW browser receives
hypermedia documents from a server. Examples of servers from which
ViolaWWW receives hypermedia documents include file servers or HTTP
servers. Examples of documents that ViolaWWW receives can be found
in viola\violadocs\vw folder, and include brief.html, about.html and
violaWWWDemo.html. Code files evidencing ViolaWWW's ability to
retrieve documents from servers include www\objs\VWHandler_hmml.v,

21

Claim Text from ’985 Patent

Viola-Feb Beta
www\objs\VWHandler_html2.v and src\viola\cl_generic.c.
Viola-Feb Beta discloses that the browser displays at least a portion of a
distributed hypermedia document. See, e.g., :
ViolaWWW displays hypermedia documents, including HMML and
HTML hypermedia documents. Examples of hypermedia HTML
documents that ViolaWWW displayed — either by retrieving them from a
local directory or retrieving them from a server location — are stored in
viola\violadocs\vw, such as brief.html, about.html,
violaWWWDemo.html. ViolaWWW could display other hypermedia
documents as well.
ViolaWWW displays HTML and HMML documents by parsing them to
identify HMML or HTML tags, and then initiates processing specified by
the tags and displays the hypermedia document. For example,
ViolaWWW will display the text marked by the H1 tag in large, bold,
header text and the text marked by the ITALIC tag in italics. Other tags
are discussed in more detail elsewhere in this chart.
Viola-Feb Beta discloses that at least a portion of a hypermedia document is
displayed in a browser-controlled window. See, e.g., :
ViolaWWW displays hypermedia documents, including HMML and
HTML hypermedia documents. Examples of hypermedia HTML
documents that ViolaWWW displayed — either by retrieving them from a
local directory or retrieving them from a server location — are stored in
viola\violadocs\vw, such as brief.html, about.html,
violaWWWDemo.html. ViolaWWW could display other hypermedia
documents as well.
ViolaWWW displays HTML and HMML documents by parsing them to
identify HMML or HTML tags, and then initiates processing specified by
the tags. The documents are displayed in the ViolaWWW browser

22

Claim Text from ’985 Patent
985-1.c:
executing the browser application on the client
workstation, with the browser application:

985-1.d:
responding to text formats to initiate processing
specified by the text formats;

Viola-Feb Beta
window.
Viola-Feb Beta discloses a browser application executing on the client
workstation. See, e.g., :
ViolaWWW is a web browser computer program that was implemented
using the Viola toolkit/language system. (See, e.g.,
viola\www\objs\www.v, viola\violadocs\vw\about.html.)
By way of example, Viola's documentation states that “ViolaWWW is an
X-Windows World Wide Web browser.” (See, e.g.,
viola\violadocs\vw\about.html.)
Viola-Feb Beta discloses responding to text formats to initiate processing
specified by the text formats, i.e., parsing text formats. See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
document files (i.e., HTML and HMML documents) that contain enabling
information from a network server (e.g., a file server or HTTP server) over
a distributed hypermedia network environment. Examples of such
documents include those in viola\violadocs\vw.
The hypermedia document files received from the network server contain
predetermined text formats which enable a browser application to display
at least a portion of a distributed hypermedia document within a browsercontrolled window. For example, the hypermedia documents downloaded
by ViolaWWW may contain HMML tags or HTML tags. In particular,
the about.html hypermedia document contains the HTML tags (i.e., text
formats) TITLE, H2 and P. (See, e.g., about.html.) As another example,
the testAll.html file contains HTML tags, such as TITLE and H1.
The hypermedia document downloaded from the remote network server is
parsed by ViolaWWW to identify the tags. ViolaWWW then initiates
processing specified by the tags. For example, ViolaWWW displays the
text marked by the H1 tag in large, bold, header text and the text marked
by the ITALIC tag in italics. (See, e.g., www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v, and src\viola\sgml.c,

23

Claim Text from ’985 Patent

Viola-Feb Beta
viola\src\libWWW.)

985-1.e:
displaying at least a portion of the document
within the browser-controlled window;

Viola-Feb Beta discloses that the browser displays a hypermedia document. See,
e.g., :
ViolaWWW displays hypermedia documents, including HMML and
HTML hypermedia documents. Examples of hypermedia HTML
documents that ViolaWWW displayed — either by retrieving them from a
local directory or retrieving them from a server location — are stored in
viola\violadocs\vw, such as brief.html, about.html,
violaWWWDemo.html. ViolaWWW could display other hypermedia
documents as well.
ViolaWWW displays HTML and HMML documents by parsing them to
identify HMML or HTML tags, and then initiates processing specified by
the tags and displays the hypermedia document. For example,
ViolaWWW will display the text marked by the H1 tag in large, bold,
header text and the text marked by the ITALIC tag in italics. Other tags
are discussed in more detail elsewhere in this chart.
Viola-Feb Beta discloses that a hypermedia document is displayed in a browser
window. See, e.g., :
ViolaWWW displays hypermedia documents, including HMML and
HTML hypermedia documents. Examples of hypermedia HTML
documents that ViolaWWW displayed — either by retrieving them from a
local directory or retrieving them from a server location — are stored in
viola\violadocs\vw, such as brief.html, about.html,
violaWWWDemo.html. ViolaWWW could display other hypermedia
documents as well.
ViolaWWW displays HTML and HMML documents by parsing them to
identify HMML or HTML tags, and then initiates processing specified by
the tags. The documents are displayed in the ViolaWWW browser

24

Claim Text from ’985 Patent
985-1.f:
identifying an embed text format which
corresponds to a first location in the document,
where the embed text format specifies the location
of at least a portion of an object external to the file,
where the object has type information associated
with it;

Viola-Feb Beta
window.
Viola-Feb Beta discloses identifying an embed text format. See, e.g., :
The file containing enabling information is downloaded from the remote
network server and parsed by ViolaWWW to identify the text formats.
ViolaWWW then initiates processing specified by the text formats. For
example, ViolaWWW displays the text marked by the H1 tag in large,
bold, header text and the text marked by the ITALIC tag in italics. (See,
e.g., www\objs\VWHandler_hmml.v, www\objs\VWHandler_html2.v,
and src\viola\sgml.c, viola\src\libWWW.)
For hypermedia documents containing embed text formats, these embed
text formats are likewise identified by parsing the file. For example, when
parsing about.html or brief.html or vobjf.html, violaWWW identifies the
VOBJF tag while parsing.
As another example, when parsing testSocket.html or link.html,
violaWWW identifies the LINK tag with REL attribute as vobj while
parsing. (See, e.g., www\objs\VWHandler_html2.v, src\viola\sgml.c,
sgml\objs\HMML_vobjf.v, sgml\objs\HTML_vobjf.v,
sgml\objs\HTML_link.v, viola\src\libWWW).
Viola-Feb Beta discloses that the embed text format corresponds to a first
location in the hypermedia document. See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
documents (e.g., HTML and HMML documents) from a network server
(e.g., a file server or HTTP server) over the distributed hypermedia
network environment. The hypermedia document received from the
network server contains text formats which enable a browser application
to display at least a portion of a distributed hypermedia document within a
browser-controlled window. These text formats include embed text
formats. For example, an HTML file can include an embed text format
called VOBJF or LINK with REL attribute as vobj. (See, e.g.,

25

Claim Text from ’985 Patent

Viola-Feb Beta
viola\violadocs\vw\brief.html; viola\violadocs\vw\about.html; vobjf.html;
violadocs\vwtests\testSocket.html; link.html.) The VOBJF text format
corresponds to a first location in the hypermedia document. Similarly,
LINK text format with REL attribute as vobj corresponds to a first
location in the hypermedia document. Vobjf.html is a file I am appending
along with this report and which I used in Viola Video 21 (see Appendix
C).
Viola-Feb Beta discloses that the embed text format specifies the location of an
object. See, e.g., :
The VOBJF embed text format and LINK text format with REL attribute
as vobj specify the location of an object.
For example, vobjf.html includes a VOBJF tag that shows the tag's syntax,
including that it specifies the location of an object based on a filepath
location in which the object can be found:
<VOBJF HREF=http://ncsaserver/WEI/plot.v >
(See vobjf.html.)
As another example, link.html includes a LINK tag with REL attribute as
vobj that shows the tag’s syntax, including that it spevidies the location of
an object based on a filepath location in which the object can be found:
<LINK REL=“vobj” HREF= http://ncsaserver/WEI/plot.v >
(See link.html.)
Viola-Feb Beta discloses that the object is external to the file containing enabling
information. See, e.g., :
In one example, when a Viola applet is embedded in a ViolaWWW web
page, using the VOBJF tag or LINK tag with REL attribute as vobj, at
least a portion of an object external to a hypermedia document, the default
grid, appears in the ViolaWWW window upon browser launch.

26

Claim Text from ’985 Patent

Viola-Feb Beta
The data for the default grid is specified in the file plot.v by the command:
output("equation 0");
(See violadocs\objs\plot.v.)
Viola-Feb Beta discloses that the object has associated type information. See,
e.g., :

For example, the file plot.v contains type information associated with the
object.
/path{/usr/work/vplot/vplot}
(See viola\violadocs\objs\plot.v.)
The type information is used by the ViolaWWW to identify and locate the
vplot executable application.
switch (pid = vfork()) {
…
case 0: \* Child *\
…
execv(GET_path(self), args);
(See src\viola\cl_TTY.c.)
985-1.g:
Viola-Feb Beta discloses that the browser uses type information to identify and
utilizing the type information to identify and locate locate an executable application. See, e.g., :
an executable application external to the file; and
For example, the file plot.v contains type information associated with the
object.
/path{/usr/work/vplot/vplot}
(See viola\violadocs\objs\plot.v.)
The type information is used by the ViolaWWW to identify and locate the
vplot executable application. ViolaWWW then invokes the executable
application.
switch (pid = vfork()) {
…
case 0: \* Child *\

27

Claim Text from ’985 Patent

Viola-Feb Beta
…
execv(GET_path(self), args);
(See viola\src\viola\cl_TTY.c.)
Viola-Feb Beta discloses that the executable application is external to the file
containing enabling information. See, e.g., :

985-1.h:
automatically invoking the executable application,
in response to the identifying of the embed text
format, to execute on the client workstation in
order to display the object and enable an end-user
to directly interact with the object while the object
is being displayed within a display area created at
the first location within the portion of the
hypermedia document being displayed in the
browser-controlled window.

For example, the vplot executable application is external to the vobjf.html
and link.html files containing enabling information. (See, e.g., vobjf.html,
link.html.) Thus, vplot is external to the hypermedia document. (See, e.g.,
PA-NAT-00000078\vplot\)
Viola-Feb Beta discloses that the browser parses the embed text format. See,
e.g., :
The file containing enabling information is downloaded from the remote
network server and parsed by ViolaWWW to identify the text formats.
ViolaWWW then initiates processing specified by the text formats. For
example, ViolaWWW displays the text marked by the H1 tag in large,
bold, header text and the text marked by the ITALIC tag in italics. (See,
e.g., www\objs\VWHandler_hmml.v, www\objs\VWHandler_html2.v,
and src\viola\sgml.c, viola\src\libWWW.)
For hypermedia documents containing embed text formats, these embed
text formats are likewise identified by parsing the file. For example, when
parsing about.html or brief.html or vobjf.html, violaWWW identifies the
VOBJF tag while parsing. Similarly, when parsing testSocket.html or
link.html, violaWWW identifies the LINK tag with REL attribute as vobj
while parsing. (See, e.g., www\objs\VWHandler_html2.v,
src\viola\sgml.c, sgml\objs\HMML_vobjf.v, sgml\objs\HTML_vobjf.v,
sgml\objs\HTML_link.v, viola\src\libWWW,
viola\violadocs\vw\brief.html; viola\violadocs\vw\about.html; vobjf.html;
violadocs\vwtests\testSocket.html; link.html.)

28

Claim Text from ’985 Patent

Viola-Feb Beta
Viola-Feb Beta discloses automatic invocation of the executable application.
See, e.g., :
When ViolaWWW parses the VOBJF tag or LINK tag with REL attribute
as vobj, it automatically invokes the vplot executable application. The
automatic invocation does not require action by the user.
For example, when ViolaWWW parses the VOBJF tag in vobjf.html or
LINK tag with REL attribute as vobj in link.html, the vplot application is
automatically invoked as follows:
switch (pid = vfork()) {
…
case 0: \* Child *\
…
execv(GET_path(self), args);
(See src\viola\cl_TTY.c.)
Viola-Feb Beta discloses that the executable application displays the object. See,
e.g., :
For example, the vplot application displays the object as a grid inside the
ViolaWWW window that is displaying vobjf.html or link.html. The
object is displayed at the location in the window corresponding to the
VOBJF tag or LINK tag with REL attribute as vobj. (See vobjf.html,
link.html.)
Viola-Feb Beta discloses that the executable application enables direct
interaction with the object. See, e.g., :
For example, the vplot executable application enables the user to directly
interact with the object using the slider bars to rotate the object around the

29

Claim Text from ’985 Patent

Viola-Feb Beta
X, Y and Z axes. (See, e.g., viola\violadocs\objs\plot.v,
src\viola\cl_slider.c, src\viola\cl_client.c.)
Viola-Feb Beta discloses that interaction with the object is at a first location in
the hypermedia document. See, e.g., :
For example, the vplot executable application enables the user to directly
interact with the object using the slider bars to rotate the object around the
X, Y and Z axes. (See, e.g., viola\violadocs\objs\plot.v,
src\viola\cl_slider.c, src\viola\cl_client.c.) This interaction with the object
occurs at the first location within the portion of the HTML document
displayed in the ViolaWWW window. (See, e.g., vobjf.html, link.html,
violadocs\objs\plot.v)

985-2.a:
The method of claim 1 where: the information to
enable comprises text formats.

Viola-Feb Beta discloses that the enabling information in the file is text formats.
See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
document files (i.e., HTML and HMML documents) that contain enabling
information from a network server (e.g., a file server or HTTP server) over
a distributed hypermedia network environment. Examples of such
documents include those in viola\violadocs\vw.
The hypermedia document files received from the network server contain
predetermined text formats which enable a browser application to display
at least a portion of a distributed hypermedia document within a browsercontrolled window. For example, the hypermedia documents downloaded
by ViolaWWW may contain HMML tags or HTML tags. In particular,
the about.html hypermedia document contains the HTML tags (i.e., text
formats) TITLE, H2 and P. (See, e.g., about.html.) As another example,
the testAll.html file contains HTML tags, such as TITLE and H1.
The hypermedia document downloaded from the remote network server is

30

Claim Text from ’985 Patent

Viola-Feb Beta
parsed by ViolaWWW to identify the tags. ViolaWWW then initiates
processing specified by the tags. For example, ViolaWWW displays the
text marked by the H1 tag in large, bold, header text and the text marked
by the ITALIC tag in italics. (See, e.g., www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v, and src\viola\sgml.c,
viola\src\libWWW.)

985-3.a:
The method of claim 2 where the text formats are
HTML tags.

Viola-Feb Beta discloses that the text formats are HTML tags. See, e.g., :

985-4.a:
The method of claim 1 where the information
contained in the file received comprises at least
one embed text format.

Viola-Feb Beta discloses that the enabling information in the file includes an
embed text format. See, e.g., :

ViolaWWW running on the client workstation can receive hypermedia
document files that contain text formats in the form of HTML tags from a
network server (e.g., a file server or HTTP server) over a distributed
hypermedia network environment. Examples of such documents include
those in viola\violadocs\vw.
For example, the testAll.html file contains HTML tags, such as TITLE and
H1

ViolaWWW running on the client workstation can receive hypermedia
documents (e.g., HTML and HMML documents) from a network server
(e.g., a file server or HTTP server) over the distributed hypermedia
network environment. The hypermedia document received from the
network server contains text formats which enable a browser application
to display at least a portion of a distributed hypermedia document within a
browser-controlled window. These text formats include embed text
formats.
For example, an HTML file can include an embed text format called
VOBJF. (See, e.g., viola\violadocs\vw\brief.html;
viola\violadocs\vw\about.html; vobjf.html).

31

Claim Text from ’985 Patent

985-5.a:
The method of claim 1 where the step of
identifying an embed text format comprises:
parsing the received file to identify text formats
included in the received file.

Viola-Feb Beta
As another example, an HTML file can include an embed text format
called LINK tag with REL attribute as vobj. (See, e.g.,
violadocs\vwtests\testSocket.html, link.html)
Viola-Feb Beta discloses that the embed text format is identified by parsing the
file containing enabling information. See, e.g., :
The file containing enabling information is downloaded from the remote
network server and parsed by ViolaWWW to identify the text formats.
ViolaWWW then initiates processing specified by the text formats. For
example, ViolaWWW displays the text marked by the H1 tag in large,
bold, header text and the text marked by the ITALIC tag in italics. (See,
e.g., www\objs\VWHandler_hmml.v, www\objs\VWHandler_html2.v,
and src\viola\sgml.c, viola\src\libWWW.)
For hypermedia documents containing embed text formats, these embed
text formats are likewise identified by parsing the file. For example, when
parsing about.html or brief.html or vobjf.html, violaWWW identifies the
VOBJF tag while parsing.
As another example, when parsing testSocket.html or link.html,
violaWWW identifies the LINK tag with REL attribute as vobj while
parsing. (See, e.g., www\objs\VWHandler_html2.v, src\viola\sgml.c,
sgml\objs\HMML_vobjf.v, sgml\objs\HTML_vobjf.v,
sgml\objs\HTML_link.v, viola\src\libWWW.)

985-6.a:
The method of claim 5 where the parsing is by a
parser in the browser.

Viola-Feb Beta discloses that the parser is in the browser See, e.g., :
Viola includes files for parsing. (See, e.g.,
www\objs\VWHandler_hmml.v, www\objs\VWHandler_html2.v and
src\viola\sgml.c, viola\src\libWWW.)
Furthermore, as discussed within my report, HTML and\or HMML parsers
were readily available and inherent to the operation of world wide web

32

Claim Text from ’985 Patent

Viola-Feb Beta
browser applications.

985-7.a:
The method of claim 1 where the processing
specified by the text formats is specified directly.

Viola-Feb Beta discloses that the text formats directly specify the processing.
See, e.g., :
ViolaWWW running on the client workstation can receive hypermedia
document files (i.e., HTML and HMML documents) that contain enabling
information from a network server (e.g., a file server or HTTP server) over
a distributed hypermedia network environment. Examples of such
documents include those in viola\violadocs\vw.
The hypermedia document files received from the network server contain
predetermined text formats which enable a browser application to display
at least a portion of a distributed hypermedia document within a browsercontrolled window. For example, the hypermedia documents downloaded
by ViolaWWW may contain HMML tags or HTML tags. In particular,
the about.html hypermedia document contains the HTML tags (i.e., text
formats) TITLE, H2 and P. (See, e.g., about.html.) As another example,
the testAll.html file contains HTML tags, such as TITLE and H1.
The hypermedia document downloaded from the remote network server is
parsed by ViolaWWW to identify the tags. ViolaWWW then initiates
processing specified by the tags. For example, ViolaWWW displays the
text marked by the H1 tag in large, bold, header text and the text marked
by the ITALIC tag in italics. (See, e.g., www\objs\VWHandler_hmml.v,
www\objs\VWHandler_html2.v, and src\viola\sgml.c,
viola\src\libWWW.)

985-8.a:
The method of claim 1 where the correspondence
is implied by the order of the text format in a set of
all of the text formats.

Viola-Feb Beta discloses that the correspondence is implied by the order of text
formats. See, e.g., :
In ViolaWWW, the correspondence between the location in the document
and the text formats is implied by the order of the text formats.
For example, about.html has several HTML tags (text formats). In

33

Claim Text from ’985 Patent

Viola-Feb Beta
about.html, TITLE tag appears before the BODY tag. Inside the BODY
tag, the first P element appears before a VOBJF element. When
ViolaWWW displays the document, the title (associated with TITLE tag)
is displayed before the contents of the P tag. A paragraph (associated with
P tag) follows. An object is embedded later in the document whtere
VOBJF tag is specified. (See, e.g., viola/violaDocs/vw/about.html.)
Similarly, for testAll.html, a title (associated with a TITLE tag) is
displayed ahead of Header 1 (associated with a subsequent header tag),
which is displayed ahead of Header 2 (associated with a still subsequent
header tag). (See violadocs\vwtests\testAll.html.)

985-9.a:
The method of claim 1 where the embed text
format specifies the location of at least a portion of
an object directly.

Viola-Feb Beta discloses that the embed text format specifies the location of the
object directly. See, e.g., :

985-10.a:
The method of claim 1 where having type
information associated is by including type
information in the embed text format.

Viola-Feb Beta discloses that the type information is in the embed text format.
See, e.g., :

The VOBJF embed text format and LINK text format with REL attribute
as vobj specify the location of an object.
For example, vobjf.html includes a VOBJF tag that shows the tag's syntax,
including that it specifies the location of an object based on a filepath
location in which the object can be found:
<VOBJF HREF=http://ncsaserver/WEI/plot.v >
(See vobjf.html.)
As another example, link.html includes a LINK tag with REL attribute as
vobj that shows the tag’s syntax, including that it spevidies the location of
an object based on a filepath location in which the object can be found:
<LINK REL=“vobj” HREF= http://ncsaserver/WEI/plot.v >
(See link.html.)

For example, the file plot.v (which contains type information as described
above) is in the VOBJF embed text format or LINK tag with REL attribute

34

Claim Text from ’985 Patent

Viola-Feb Beta
as vobj.
<VOBJF HREF=http://ncsaserver/WEI/plot.v >
(See vobjf.html.) Vobjf.html is a file I am appending along with this
report and which I used in Viola Video 21 (see Appendix C). In Viola
Video 21 I show how [Viola-Feb beta] parses the VOBFJ embed tag.
<LINK REL=“vobj” HREF= http://ncsaserver/WEI/plot.v >
(See link.html.)

985-11.a:
The method of claim 1 where automatically
invoking does not require interactive action by the
user.

Viola-Feb Beta discloses that automatic invocation does not require interactive
action by the user. See, e.g., :

985-16.a:
One or more computer readable media encoded
with software comprising computer executable
instructions, for use in a distributed hypermedia
network environment, wherein the network
environment comprises at least one client

Viola-Feb Beta discloses computer code physically embodied on a medium.
See, e.g., :

When ViolaWWW parses the VOBJF tag or LINK tag with REL attribute
as vobj, it automatically invokes the vplot executable application. The
automatic invocation does not require action by the user.
For example, when ViolaWWW parses the VOBJF tag in vobjf.html or
LINK tag with REL attribute as vobj in link.html, the vplot application is
automatically invoked without any interactive action by the user, as
follows:
switch (pid = vfork()) {
…
case 0: \* Child *\
…
execv(GET_path(self), args);
(See src\viola\cl_TTY.c.)

The computer on which ViolaWWW executes includes computer usable
media having computer readable program code physically embodied
therein. By way of example, ViolaWWW executed on Sun

35

Claim Text from ’985 Patent
workstation and one network server coupled to the
network environment, and when the software is
executed operable to:

985-16.b:
receive, at the client workstation from the network
server over the network environment, at least one
file containing information to enable a browser
application to display at least a portion of a
distributed hypermedia document within a
browser-controlled window;
985-16.c:
cause the client workstation to utilize the browser
to:
985-16.d:
respond to text formats to initiate processing
specified by the text formats;
985-16.e:
display at least a portion of the document within
the browser-controlled window;
985-16.f:
identify an embed text format corresponding to a
first location in the document, the embed text
format specifying the location of at least a portion
of an object external to the file, with the object
having type information associated with it;
985-16.g:
utilize the type information to identify and locate

Viola-Feb Beta
SPARCstations running a SunOS operating system. ViolaWWW could be
executed on the Sun SPARCstation with the command “viola –o www.”
Viola, including the www.v file that implements the ViolaWWW browser,
contains computer readable code that is stored on the SPARCstation's
computer usable media.
Viola-Feb Beta discloses a client workstation and a network server in a
distributed hypermedia environment. See evidence recited for 985-1.a.
Viola-Feb Beta discloses a browser application; a file containing enabling
information received from a server; that the browser displays at least a portion of
a distributed hypermedia document; and that the display is in a browsercontrolled window. See evidence recited for 985-1.b.

Viola-Feb Beta discloses a browser application executing on the client
workstation. See evidence recited for 985-1.c.
Viola-Feb Beta discloses parsing text formats. See evidence recited for 985-1.d.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses identifying an embed text format; that the embed text
format corresponds to a first location in a hypermedia document; that the embed
text format specifies the location of at least a portion of an object external to the
file containing enabling information; and that the object has associated type
information. See evidence recited for 985-1.f.
Viola-Feb Beta discloses using type information to identify and locate an
executable application external to the file. See evidence recited for 985-1.g.

36

Claim Text from ’985 Patent
an executable application external to the file; and
985-16.h:
automatically invoke the executable application, in
response to the identifying of the embed text
format, to execute on the client workstation in
order to display the object and enable an end-user
to directly interact with the object while the object
is being displayed within a display area created at
the first location within the portion of the
hypermedia document being displayed in the
browser-controlled window.

Viola-Feb Beta
Viola-Feb Beta discloses automatically invoking the executable application; that
the executable application displays the object and enables an end-user to directly
interact with it; and that the interaction with the object is at a first location in a
hypermedia document. See evidence recited for 985-1.h.

985-17.a:
The computer readable media of claim 16 where:
the information to enable comprises text formats.

Viola-Feb Beta discloses that the enabling information in the file is text formats.
See evidence recited for 985-2.a.

985-18.a:
The computer readable media of claim 17 where:
the text formats are HTML tags.

Viola-Feb Beta discloses that the text formats are HTML tags. See evidence
recited for 985-3.a.

985-19.a:
The computer readable media of claim 16 where:
the information contained in the file received
comprises at least one embed text format.

Viola-Feb Beta discloses that the enabling information in the file includes an
embed text format. See evidence recited for 985-4.a.

985-20.a:
A method of serving digital information in a
computer network environment having a network
server coupled the network environment, and
where the network environment is a distributed
hypermedia environment, the method comprising:

Viola-Feb Beta discloses digital information. See, e.g., :
The information that is exchanged between a client workstation running
ViolaWWW and a network server (such as web server or file server) is
digital information.
For example, ViolaWWW running on the client workstation can receive
hypermedia documents (HTML and HMML documents) from a network
37

Claim Text from ’985 Patent

Viola-Feb Beta
server over the distributed hypermedia network environment. These
documents are transmitted according to network protocols that transmit
information in digital form. Examples of the types of documents that can
be served in digital form can be found in viola\violadocs\vw, including
brief.html, about.html, violaWWWDemo.html.
ViolaWWW also could receive *.v files over networks in digital form.
Examples of *.v files are in viola\violadocs\objs, and include plot.v.
Viola-Feb Beta discloses a network server in a distributed hypermedia
environment. See evidence recited for 985-1.a.
Viola-Feb Beta discloses a client workstation. See evidence recited for 985-1.a.

985-20.b:
communicating via the network server with at least
one client workstation over said network in order
Viola-Feb Beta discloses communicating via network server in order to cause the
to cause said client workstation to:
client workstation to act. See, e.g., :

985-20.c:
receive, over said network environment from said
server, at least one file containing information to
enable a browser application to display at least a
portion of a distributed hypermedia document

The ViolaWWW browser operating on a client workstation requests
hypermedia documents from a server, such as a file server or an HTTP
server. The server responds by communicating to the client workstation.
By way of example, the server transmits hypermedia documents, examples
of which can be found in viola\violadocs\vw. The server can transmit *.v
files, examples of which are found in viola\violadocs\objs. For example,
the server can transmit about.html or plot.v to the client workstation.
The client workstation, after receiving the hypermedia document and/or
*.v file from the network server, parses the hypermedia document and
responds to the text formats contained in the hypermedia document to
initiate processing specified by the text formats and/or by initiating
processing according to a *.v file. (See, e.g., src\viola\sgml.c.)
Viola-Feb Beta discloses a browser application; a file containing enabling
information received from a server; that the browser displays at least a portion of
a distributed hypermedia document; and that the display is in a browsercontrolled window. See evidence recited for 985-1.b.

38

Claim Text from ’985 Patent
within a browser-controlled window;
985-20.d:
execute, at said client workstation, a browser
application, with the browser application:
985-20.e:
responding to text formats to initiate processing
specified by the text formats;
985-20.f:
displaying, on said client workstation, at least a
portion of the document within the browsercontrolled window;
985-20.g:
identifying an embed text format which
corresponds to a first location in the document,
where the embed text format specifies the location
of at least a portion of an object external to the file,
where the object has type information associated
with it;
985-20.h:
utilizing the type information to identify and locate
an executable application external to the file; and
985-20.i:
automatically invoking the executable application,
in response to the identifying of the embed text
format, to execute on the client workstation in
order to display the object and enable an end-user
to directly interact with the object while the object
is being displayed within a display area created at
the first location within the portion of the
hypermedia document being displayed in the
browser-controlled window.

Viola-Feb Beta
Viola-Feb Beta discloses a browser application executing on the client
workstation. See evidence recited for 985-1.c.
Viola-Feb Beta discloses parsing text formats. See evidence recited for 985-1.d.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses identifying an embed text format; that the embed text
format corresponds to a first location in a hypermedia document; that the embed
text format specifies the location of at least a portion of an object external to the
file containing enabling information; and that the object has associated type
information. See evidence recited for 985-1.f.
Viola-Feb Beta discloses using type information to identify and locate an
executable application external to the file. See evidence recited for 985-1.g.
Viola-Feb Beta discloses automatically invoking the executable application; that
the executable application displays the object and enables an end-user to directly
interact with it; and that the interaction with the object is at a first location in a
hypermedia document. See evidence recited for 985-1.h.

39

Claim Text from ’985 Patent
985-21.a:
The method of claim 20 where: the information to
enable comprises text formats.

Viola-Feb Beta
Viola-Feb Beta discloses that the enabling information in the file is text formats.
See evidence recited for 985-2.a.

985-22.a:
The method of claim 21 where: the text formats
are HTML tags.

Viola-Feb Beta discloses that the text formats are HTML tags. See evidence
recited for 985-3.a.

985-23.a:
The method of claim 20 where: the information
contained in the file received comprises at least
one embed text format.

Viola-Feb Beta discloses that the enabling information in the file includes an
embed text format. See evidence recited for 985-4.a.

985-24.a:
A method for running an executable application in
a computer network environment, wherein said
network environment has at least one client
workstation and one network server coupled to a
network environment, the method comprising:
985-24.b:
enabling an end-user to directly interact with an
object by utilizing said executable application to
interactively process said object while the object is
being displayed within a display area created at a
first location within a portion of a hypermedia
document being displayed in a browser-controlled
window,

Viola-Feb Beta discloses a client workstation and a network server in a network
environment. See evidence recited for 985-1.a.
Viola-Feb Beta discloses an executable application. See evidence recited for
985-1.g.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses an object external to a file containing enabling
information. See evidence recited for 985-1.f.
Viola-Feb Beta discloses that there is enabling of an end-user to directly interact
with the object. See, e.g., :
For example, the vplot executable application enables the user to directly
interact with the object using the slider bars to rotate the object around the
X, Y and Z axes. (See, e.g., viola\violadocs\objs\plot.v,
src\viola\cl_slider.c, src\viola\cl_client.c.)

40

Claim Text from ’985 Patent

Viola-Feb Beta
Viola-Feb Beta discloses that the interaction with the object is at a first location
in a hypermedia document. See evidence recited for 985-1.h.
Viola-Feb Beta discloses that the object is displayed at a first location within a
portion of the hypermedia document being displayed. See, e.g., :

985-24.c:
wherein said network environment is a distributed
hypermedia environment,
985-24.d:
wherein said client workstation receives, over said
network environment from said server, at least one
file containing information to enable said browser
application to display, on said client workstation,
at least said portion of said distributed hypermedia
document within said browser-controlled window,
985-24.e:
wherein said executable application is external to
said file,
985-24.f:
wherein said client workstation executes the
browser application, with the browser application
responding to text formats to initiate processing

In one example, the object is displayed and interactive processing of the
object occurs at the first location within the portion of the hypermedia
document displayed in the ViolaWWW window.
For example, the vplot application displays the object as a grid (the default
grid) inside the ViolaWWW window. The object is displayed at the first
location in the portion of the vobjf.html or link.html hypermedia document
being displayed in the ViolaWWW window. (See, e.g., vobjf.html,
link.html.)
Viola-Feb Beta discloses a client workstation and a network server in a
distributed hypermedia environment. See evidence recited for 985-1.a.
Viola-Feb Beta discloses a browser application; a file containing enabling
information received from a server; that the browser displays at least a portion of
a distributed hypermedia document; and that the display is in a browsercontrolled window. See evidence recited for 985-1.b.

Viola-Feb Beta discloses an executable application external to the file. See
evidence recited for 985-1.g.
Viola-Feb Beta discloses a browser application executing on the client
workstation. See evidence recited for 985-1.c.
Viola-Feb Beta discloses parsing text formats. See evidence recited for 985-1.d.

41

Claim Text from ’985 Patent
specified by the text formats,
985-24.g:
wherein at least said portion of the document is
displayed within the browser-controlled window,
985-24.h:
wherein an embed text format which corresponds
to said first location in the document is identified
by the browser,
985-24.i:
wherein the embed text format specifies the
location of at least a portion of said object external
to the file,
985-24.j:
wherein the object has type information associated
with it,
985-24.k:
wherein the type information is utilized by the
browser to identify and locate said executable
application, and
985-24.l:
wherein the executable application is automatically
invoked by the browser, in response to the
identifying of the embed text format.

Viola-Feb Beta
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses identifying an embed text format and that the embed
text format corresponds to a first location in a hypermedia document. See
evidence recited for 985-1.f.
Viola-Feb Beta discloses that the embed text format specifies the location of at
least a portion of an object external to the file containing enabling information.
See evidence recited for 985-1.f.
Viola-Feb Beta discloses that the object has associated type information. See
evidence recited for 985-1.f.
Viola-Feb Beta discloses using type information to identify and locate an
executable application external to the file. See evidence recited for 985-1.g.
Viola-Feb Beta discloses automatically invoking the executable application. See
evidence recited for 985-1.h.

985-25.a:
The method of claim 24 where: the information to
enable comprises text formats.

Viola-Feb Beta discloses that the enabling information in the file is text formats.
See evidence recited for 985-2.a.

985-26.a:
The method of claim 25 where: the text formats
are HTML tags.

Viola-Feb Beta discloses that the text formats are HTML tags. See evidence
recited for 985-3.a.

42

Claim Text from ’985 Patent
985-27.a:
The method of claim 24 where: the information
contained in the file received comprises at least
one embed text format.
985-28.a:
One or more computer readable media encoded
with software comprising an executable
application for use in a system having at least one
client workstation and one network server coupled
to a network environment, operable to:
985-28.b:
cause the client workstation to display an object
and enable an end-user to directly interact with
said object while the object is being displayed
within a display area created at a first location
within a portion of a hypermedia document being
displayed in a browser-controlled window,

Viola-Feb Beta
Viola-Feb Beta discloses that the enabling information in the file includes an
embed text format. See evidence recited for 985-4.a.

Viola-Feb Beta discloses computer code physically embodied on a medium. See
evidence recited for 985-16.a.
Viola-Feb Beta discloses a client workstation and a network server in a network
environment. See evidence recited for 985-1.a.
Viola-Feb Beta discloses an executable application. See evidence recited for
985-1.g.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses an object external to a file containing enabling
information. See evidence recited for 985-1.f.
Viola-Feb Beta discloses that there is enabling of an end-user to directly interact
with the object. See evidence recited for 985-24.b.
Viola-Feb Beta discloses that the interaction with the object is at a first location
in a hypermedia document. See evidence recited for 985-1.h.
Viola-Feb Beta discloses that the object is displayed within a display area
created at the first location.. See, e.g., :
In one example, the object is displayed and interactive processing of the
object occurs at the first location within the portion of the hypermedia
document displayed in the ViolaWWW window.
For example, the vplot application displays the object as a grid (the default

43

Claim Text from ’985 Patent

985-28.c:
wherein said network environment is a distributed
hypermedia environment,
985-28.d:
wherein said client workstation receives, over said
network environment from said server, at least one
file containing information to enable said browser
application to display, on said client workstation,
at least said portion of said distributed hypermedia
document within said browser-controlled window,
985-28.e:
wherein said executable application is external to
said file,
985-28.f:
wherein said client workstation executes said
browser application, with the browser application
responding to text formats to initiate processing
specified by the text formats,
985-28.g:
wherein at least said portion of the document is
displayed within the browser-controlled window,
985-28.h:
wherein an embed text format which corresponds
to said first location in the document is identified
by the browser,
985-28.i:
wherein the embed text format specifies the
location of at least a portion of said object external

Viola-Feb Beta
grid) inside the ViolaWWW window. The object is displayed at the first
location in the portion of the vobjf.html or link.html hypermedia document
being displayed in the ViolaWWW window. (See, e.g., vobjf.html,
link.html.)
Viola-Feb Beta discloses a client workstation and a network server in a
distributed hypermedia environment. See evidence recited for 985-1.a.
Viola-Feb Beta discloses a browser application; a file containing enabling
information received from a server; that the browser displays at least a portion of
a distributed hypermedia document; and that the display is in a browsercontrolled window. See evidence recited for 985-1.b.

Viola-Feb Beta discloses an executable application external to the file. See
evidence recited for 985-1.g.
Viola-Feb Beta discloses a browser application executing on the client
workstation. See evidence recited for 985-1.c.
Viola-Feb Beta discloses parsing text formats. See evidence recited for 985-1.d.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses identifying an embed text format and that the embed
text format corresponds to a first location in a hypermedia document. See
evidence recited for 985-1.f.
Viola-Feb Beta discloses that the embed text format specifies the location of at
least a portion of an object external to the file containing enabling information.
See evidence recited for 985-1.f.

44

Claim Text from ’985 Patent
to the file,
985-28.j:
wherein the object has type information associated
with it,
985-28.k:
wherein the type information is utilized by the
browser to identify and locate said executable
application, and
985-28.l:
wherein the executable application is automatically
invoked by the browser, in response to the
identifying of the embed text format.
985-36.a:
A method for running an application program in a
distributed hypermedia network environment,
wherein the distributed hypermedia network
environment comprises at least one client
workstation and one remote network server
coupled to the distributed hypermedia network
environment, the method comprising:
985-36.b:
receiving, at the client workstation from the
network server over the distributed hypermedia
network environment, at least one file containing
information to enable a browser application to
display at least a portion of a distributed
hypermedia document within a browser-controlled
window;
985-36.c:
executing the browser application on the client
workstation, with the browser application:

Viola-Feb Beta
Viola-Feb Beta discloses that the object has associated type information. See
evidence recited for 985-1.f.
Viola-Feb Beta discloses using type information to identify and locate an
executable application external to the file. See evidence recited for 985-1.g.
Viola-Feb Beta discloses automatically invoking the executable application. See
evidence recited for 985-1.h.

Viola-Feb Beta discloses an application program in a distributed hypermedia
environment comprising at least client workstation and network server. See
evidence recited for 985-1.a.

Viola-Feb Beta discloses a browser application; a file containing enabling
information; that the file is received at the client workstation from the network
server; that the browser displays at least a portion of a distributed hypermedia
document; and that at least a portion of a hypermedia document is displayed in a
browser-controlled window. See evidence recited for 985-1.b.

Viola-Feb Beta discloses a browser application executing on the client
workstation. See evidence recited for 985-1.c.

45

Claim Text from ’985 Patent
985-36.d:
responding to text formats to initiate processing
specified by the text formats;
985-36.e:
displaying at least a portion of the document
within the browser-controlled window;
985-36.f:
identifying an embed text format which
corresponds to a first location in the document,
where the embed text format specifies the location
of at least a portion of an object;

985-36.g:
identifying and locating an executable application
associated with the object; and

Viola-Feb Beta
Viola-Feb Beta discloses parsing text formats. See evidence recited for 985-1.d.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses an object. See, e.g., :
In one example, when a Viola applet is embedded in a ViolaWWW web
page, using the VOBJF tag or LINK tag with REL attribute as vobj, at
least a portion of an object, the default grid, appears in the ViolaWWW
window upon browser launch.
The data for the default grid is specified in the file plot.v by the command:
output("equation 0");
(See violadocs\objs\plot.v.)
Viola-Feb Beta discloses identifying an embed text format; that the embed text
format corresponds to a first location in the hypermedia document; and that the
embed text format specifies the location of an object. See evidence recited for
985-1.f.
Viola-Feb Beta discloses that the browser identifies and locates an executable
application associated with the object. See, e.g.,
For example, the file plot.v contains type information associated with the
object.
/path{/usr/work/vplot/vplot}
(See viola\violadocs\objs\plot.v.)
The type information is used by the ViolaWWW to identify and locate the
vplot executable application. ViolaWWW then invokes the executable
application.
switch (pid = vfork()) {
…

46

Claim Text from ’985 Patent

985-36.h:
automatically invoking the executable application,
in response to the identifying of the embed text
format, in order to enable an end-user to directly
interact with the object, while the object is being
displayed within a display area created at the first
location within the portion of the hypermedia
document being displayed in the browsercontrolled window,

Viola-Feb Beta
case 0: \* Child *\
…
execv(GET_path(self), args);
(See viola\src\viola\cl_TTY.c.)
Viola-Feb Beta discloses identifying an embed text format. See evidence recited
in 985-1.f.
Viola-Feb Beta discloses automatic invocation of the executable application; that
the executable application displays the object; that the executable application
enables direct interaction with the object; and that interaction with the object is
at a first location in the hypermedia document. See evidence recited in 985-1.h.
Viola-Feb Beta discloses that the object is displayed at a first location within a
portion of the hypermedia document being displayed. See evidence recited at
985-24.b.
Viola-Feb Beta discloses that a hypermedia document is displayed in a browser
window. See, e.g., evidence recited for 985-1.e.

985-36.i:
wherein the executable application is part of a
distributed application, and

Viola-Feb Beta discloses a distributed application. See, e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this

47

Claim Text from ’985 Patent

Viola-Feb Beta
case, a portion of the computations would be performed on a process on a
remote server.
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with distributed applications, such as VIS. See
examples below. ViolaWWW works with a distributed application in the
same way that it works with an executable application on the client
workstation.

VIS
Viola-Feb Beta discloses that the executable application is part of a distributed

48

Claim Text from ’985 Patent

Viola-Feb Beta
application. See, e.g., :

985-36.j:
wherein at least a portion of the distributed
application is for execution on a remote network
server coupled to the distributed hypermedia
network environment.

Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, the executable application is part of a distributed application.
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with distributed applications such as VIS.
ViolaWWW works with a distributed application in the same way that it
works with an executable application on the client workstation.
Viola-Feb Beta discloses that the distributed application executes at least
partially on a network server. See, e.g., :
Viola's documentation states that "Through a communication facility such
as the socket, a message may also be generated from another process on
the network." (See, e.g., viola\violadocs\vw\brief.html.) By way of
example, and as discussed elsewhere in this chart, ViolaWWW provides
for automatically invoking the vplot executable application using the
execv system call. (See viola\src\viola\cl_TTY.c.) Vplot can be
implemented as a distributed application wherein a portion of the
computations — for example, graphics transformations — can be executed
on a remote server by using the rexec socket-based system call or other
Unix socket-based system calls in leiu of the execv system call. In this
case, a portion of the computations would be performed on a process on a
remote server.

49

Claim Text from ’985 Patent

Viola-Feb Beta
Furthermore, as discussed in my report and in Viola video 24.avi, vplot
can be interchanged with any distributed application, including VIS.
ViolaWWW works with a distributed application in the same way that it
works with an executable application on the client workstation.

985-37.a:
The method of claim 36 where: the information to
enable comprises text formats.

Viola-Feb Beta discloses that the enabling information in the file is text formats.
See evidence recited for 985-2.a.

985-38.a:
The method of claim 37 where: the text formats
are HTML tags.

Viola-Feb Beta discloses that the text formats are HTML tags. See evidence
recited for 985-3.a.

985-39.a:
The method of claim 36 where: the information
contained in the file received comprises at least
one embed text format.

Viola-Feb Beta discloses that the enabling information in the file includes an
embed text format. See evidence recited for 985-4.a.

985-40.a:
A method of serving digital information in a
computer network environment having a network
server coupled to said computer network
environment, and where the network environment
is a distributed hypermedia network environment,
the method comprising:
985-40.b:
communicating via the network server with at least
one remote client workstation over said computer
network environment in order to cause said client
workstation to:
985-40.c:
receive, over said computer network environment

Viola-Feb Beta discloses digital information. See evidence recited for 985-20.a.
Viola-Feb Beta discloses a network server in a distributed hypermedia
environment. See evidence recited for 985-1.a.

Viola-Feb Beta discloses a client workstation. See evidence recited for 985-1.a.
Viola-Feb Beta discloses communicating via network server in order to cause the
client workstation to act. See evidence recited for 985-20.b.
Viola-Feb Beta discloses a browser application; a file containing enabling
information received from a server; that the browser displays at least a portion of
50

Claim Text from ’985 Patent
from the network server, at least one file
containing information to enable a browser
application to display at least a portion of a
distributed hypermedia document within a
browser-controlled window;
985-40.d:
execute, at said client workstation, a browser
application, with the browser application:
985-40.e:
responding to text formats to initiate processing
specified by the text formats;
985-40.f:
displaying, on said client workstation, at least a
portion of the document within the browsercontrolled window;
985-40.g:
identifying an embed text format which
corresponds to a first location in the document,
where the embed text format specifies the location
of at least a portion of an object;
985-40.h:
identifying and locating an executable application
associated with the object; and
985-40.i:
automatically invoking the executable application,
in response to the identifying of the embed text
format, in order to enable an end-user to directly
interact with the object while the object is being
displayed within a display area created at the first
location within the portion of the hypermedia
document being displayed in the browser-

Viola-Feb Beta
a distributed hypermedia document; and that the display is in a browsercontrolled window. See evidence recited for 985-1.b.

Viola-Feb Beta discloses a browser application executing on the client
workstation. See evidence recited for 985-1.c.
Viola-Feb Beta discloses parsing text formats. See evidence recited for 985-1.d.
Viola-Feb Beta discloses displaying at least a portion of the document within the
browser-controlled window. See evidence recited for 985-1.e.
Viola-Feb Beta discloses an object. See evidence recited for 985-36.f.
Viola-Feb Beta discloses identifying an embed text format; that the embed text
format corresponds to a first location in the hypermedia document; and that the
embed text format specifies the location of an object. See evidence recited for
985-1.f.
Viola-Feb Beta discloses that the browser identifies and locates an executable
application associated with the object. See evidence recited for 985-36.g.
Viola-Feb Beta discloses identifying an embed text format. See evidence recited
in 985-1.f.
Viola-Feb Beta discloses automatic invocation of the executable application; that
the executable application displays the object; that the executable application
enables direct interaction with the object; and that interaction with the object is
at a first location in the hypermedia document. See evidence recited in 985-1.h.

51

Claim Text from ’985 Patent
controlled window,

Viola-Feb Beta
Viola-Feb Beta discloses that the object is displayed at a first location within a
portion of the hypermedia document being displayed. See evidence recited for
985-24.b.
Viola-Feb Beta discloses that a hypermedia document is displayed in a browser
window. See, e.g., evidence recited for 985-1.e.

985-40.j:
wherein the executable application is part of a
distributed application, and
985-40.k:
wherein at least a portion of the distributed
application is for execution on the network server.

Viola-Feb Beta discloses that the executable application is part of a distributed
application. See evidence recited in 985-36.i.

985-41.a:
The method of claim 40 where: the information to
enable comprises text formats.

Viola-Feb Beta discloses that the enabling information in the file is text formats.
See evidence recited for 985-2.a.

985-42.a:
The method of claim 41 where: the text formats
are HTML tags.

Viola-Feb Beta discloses that the text formats are HTML tags. See evidence
recited for 985-3.a.

985-43.a:
The method of claim 40 where: the information
contained in the file received comprises at least
one embed text format.

Viola-Feb Beta discloses that the enabling information in the file includes an
embed text format. See evidence recited for 985-4.a.

Viola-Feb Beta discloses that the distributed application executes at least
partially on a network server. See evidence recited for 985-36.j.

52