Source: https://patents.google.com/patent/US8627197B2/en
Timestamp: 2019-04-18 21:47:26+00:00

Document:
A system, method, and apparatus for annotating an electronic document independently of its content is provided. According to one variation, a tablet and stylus-based computer is programmed with a document browser that permits a user to annotate documents viewed through the browser. The annotations are stored separately from the viewed document pages but are correlated with the pages such that when a previously annotated page is revisited, annotations relating to that page are retrieved and displayed on top of the page as an “ink” layer. Three different annotation modes are possible: ink, highlight, and erase. Each mode can be selected through a user interface supplied through the browser or through controls embedded in a document.
This application is a continuation of U.S. patent application Ser. No. 11/964,457, filed on Dec. 26, 2007, now issued as U.S. Pat. No. 7,975,216, which is a continuation of U.S. patent application Ser. No. 09/455,805, filed on Dec. 7, 1999, now issued as U.S. Pat. No. 7,337,389, both of which are incorporated herein by reference.
This invention relates generally to document browsers and pages that are displayed using such browsers. More particularly, the invention provides a method and apparatus for allowing a user to add annotations and other markings to an electronic document independently of the content of the document.
Web browsers are conventionally used to display documents created with a standard descriptive language such as Hyper Text Markup Language (HTML). Documents written in such languages can be displayed with various visual and audio effects such as color, animation, sound effects, and the like. The documents may include text, bitmap images, graphics, and other types of content.
Web browsers (or, more generally, “document browsers”) typically provide functions which permit a user to advance forward and backward among a series of related pages; to jump to a specified page; to jump to pages that are referenced via a so-called “hyperlink” embedded in a page; and to maintain a list of recently viewed pages. Although frequently used to navigate through web pages on the Internet, document browsers can be used to display pages that reside on a local area network or even a local computer on which the browser executes.
Recently, as computers have become smaller, it has become possible to run browsers on notebook computers, palm-sized computers, and so-called “tablet and stylus” computers. The latter devices typically comprise a thin computer roughly the size of a sheet of paper with a large writing surface that doubles as a display, and a stylus that substitutes for a keyboard. A user can display and edit documents using the stylus as a writing instrument.
One potential application for such hand-held computers is the display of mass-produced documents such as books, maps, and other descriptive material. For example, a user who purchases a textbook or fictional work on a CD-ROM or other medium can display the work using a small computer such as a tablet-based computer.
In some instances, a user may want to annotate or otherwise mark pages displayed on the computer. Using a conventional word processing program, a user can rearrange text, highlight certain words or phrases, or delete portions of the text. Such features require that the user have access to the underlying content (e.g., the descriptive material that forms the work). In the case of copyrighted materials, however, editing capabilities may not be available to modify the underlying materials. Certain text may be copy-protected or otherwise unavailable for editing using normal editing tools, or may not be in a format suitable for word processing. In such circumstances, there may be no practical way for a user to annotate such works. As one example, a student viewing a copy- or edit-protected textbook on a tablet-based computer may have no practical way of making notes directly in the textbook. Such a feature would be desirable notwithstanding the copy protection or unavailability of general editing functions for the document.
The present invention provides a method and apparatus for users to annotate documents in a document browser without changing the contents of the documents. According to one variation of the invention, a tablet and stylus-based computer is programmed with a document browser that permits a user to annotate documents that are viewed through the browser. The annotations are stored separately from the viewed document pages but are correlated with the pages such that when a previously annotated page is revisited, annotations relating to that page are retrieved and displayed on top of the page as an “ink” layer.
According to one variation of the invention, three different annotation modes are provided: ink, highlight, and erase. Each mode can be selected through a user interface supplied through the browser or through controls embedded in a document. The annotation functions can be implemented as an Active-X® control, as an Applet, or as dedicated code integrated into the browser. Other features and advantages of the invention will become apparent through the following description, the figures, and the appended claims.
FIG. 2 shows a conventional tablet and stylus-based computer that can be used according to one aspect of the invention.
FIG. 3 is a conceptual view showing an ink layer 302 arranged on top of an underlying document page 301. The ink layer may include opaque and translucent markings.
FIG. 4 shows a user interface on a computer screen including a menu 402 that permits a user to select from among a plurality of annotation modes on a displayed document.
FIG. 5 shows a user interface on a computer screen including an opaque annotation 501 and a highlighted annotation 502, both superimposed over a displayed document.
FIG. 6 shows a user interface on a computer screen including an opaque annotation 601 in a pre-erase state.
FIG. 7 shows a user interface on a computer screen including an opaque annotation 701 in a post-erase state, where the annotation has been partially erased.
FIG. 8 shows one possible software design for implementing various principles of the invention.
FIG. 9A shows a flowchart indicating various steps that can be executed to provide an annotation function according to certain inventive principles.
FIG. 9B shows a flowchart indicating how previously created annotations can be superimposed over a document page.
FIG. 3 is a conceptual view showing a computer screen on which a document page 301 is displayed using a document browser. As is conventional, the document page contains text and/or graphics of interest to the user (i.e., “content”). In accordance with the invention, a special “ink” layer 302 is superimposed over the document page 301. Using stylus 305, the user can highlight certain parts of the document 304, which are then shown in a highlighted color (e.g., yellow) against the background text.
Also using stylus 305, the user can mark opaque annotations 303 on the computer display, which appear to be written on the page itself. (Although ink layer 302 is shown as a separate layer in FIG. 3, this view is for conceptual purposes only; the user would see only document page 301 with annotations superimposed over the text and/or graphics on the page). According to one aspect of the invention, annotations made by a user on document page 301 are maintained as a separate “ink” layer 302 that is superimposed over and blended with pixels on the document page. Consequently, even though the annotations appear to be made directly on the underlying document, they are actually maintained in a separate display layer blended with the document page being viewed.
In one embodiment, annotations are specific to each user, such that other users who view the same document will not see a previous user's annotations. This feature can be implemented using log-ins or other user identifiers. For an identical document retrieved at two different remote computers each having the inventive features, annotations made on one remote computer would not show up on the other remote computer, since the annotations are made independently of the document content. It is, however, within the scope of the invention to permit sharing of annotations if desired.
Although the inventive principles are described with respect to a tablet and stylus computer, these principles can be applied to other types of computers, including desktop systems, notebook computers, and the like. Many types of input devices, such as touch-sensitive displays and the like, can be used to indicate those portions of the display that are to be annotated. Moreover, as explained above, many variations on a basic stylus are of course possible, including an embodiment in which the stylus includes a writing end and an “erasing” end.
FIG. 4 shows a user interface on a computer screen on which a document page 401 is displayed using a document browser. In accordance with one embodiment of the invention, the user interface includes an annotation mode selection menu 402 that permits a user to select from among a plurality of annotation modes for a displayed document. By tapping the stylus on pen button 403, the user can cause the annotation mode selection menu 402 to be displayed. A mode indicator 404 indicates the current annotation mode for the document browser.
According to one variation of the invention, these modes can include an “ink” mode, a “highlight” mode, and an “erase” mode. Additionally, a “selection” mode permits the user to switch to normal browser functions. As shown in FIG. 4, the user interface is already in “erase” mode (indicated by mode indicator 404), so that “erase” is not shown as one of the available modes in menu 402.
It is not necessary to provide an explicit “mode selection” feature as described above; instead, mode selection can be implicit in the manner by which the input device is used. As one example, a stylus could be used to provide an ink mode when the stylus is used as a writing implement; a highlighting mode when the stylus is held a certain way or when a button is pressed on the stylus; and an erase mode when an “erasing” end of the stylus is moved across portions of the display. As another example, one of the modes (e.g., the ink mode) could be established as a default mode when a user input device is manipulated, with other modes being selected based on additional user inputs or manipulations or even voice commands, for example. Many other variations are of course possible.
FIG. 5 shows a user interface on a computer screen including the document of FIG. 4. Using the “ink” mode, the user has annotated a portion of the document 501 with an opaque ink color (e.g., black or blue). The user has also highlighted a different portion of the document 502 using the “highlight” mode. The highlighted portion 502 appears in a translucent color (e.g., yellow) superimposed over the underlying document. Using the “ink” and “highlight” modes, the user is able to annotate pages viewed through the document browser as needed.
FIGS. 6 and 7 show one possible approach for implementing an “erase” mode. FIG. 6 shows a pre-erase screen in which the user has annotated a document page using an opaque ink color 601. FIG. 7 shows the same screen of FIG. 6 after the user has selected the “erase” mode and moved the stylus across a portion of the annotated region 601, leaving a partially erased annotation 701. Using the “erase” mode, the user can remove previous annotations from the computer screen. The width of the eraser function can be varied to suit various applications, or it can even be user-selectable.
FIG. 8 shows one possible software design for implementing various principles of the invention. As shown in FIG. 8, a document browser 801 permits a user to retrieve and view content in the form of documents from a document storage area 804. The documents can be stored locally on the user's computer (e.g., on CD-ROM disks and the like), or they can be stored remotely and retrieved across a network such as the Internet. Annotation editor 803 retrieves and stores annotations in “ink layers” stored in a storage device or area 805. As with document storage, ink layer storage area 805 can be local or remotely located.
Annotations retrieved from storage area 805 are provided to pixel blending function 802, which is indicated as a newly provided function within document browser 801. Alternatively, pixel blending function 802 can be provided separately (e.g., in the operating system, for example). In general, pixel blending function 802 blends pixels from a document page with corresponding pixels from an annotation or “ink” layer mapped to that document page, and generates a blended pixel image that is displayed as an annotated document page 806.
In one embodiment, each opaque annotation pixel replaces a corresponding pixel on a document page, whereas each translucent annotation pixel (e.g., highlighting) is blended with a corresponding pixel value on a document page to produce a different color from that in the original document. Pixel blending functions such as alpha blending are well known and no further elaboration of this feature is required.
Annotations can be saved as “strokes” in a data structure and stored locally in a file associated with the currently displayed page of the document. Each stroke can comprise a stroke type (e.g., annotate, highlight or erase), a stroke width, and a stroke color in addition to coordinates indicating the stroke trajectory. In various embodiments, annotation storage occurs automatically, such that whenever the input device is released (or lifted), a new stroke is automatically stored.
Alternatively, it is of course possible to store annotations as a bitmap image having the same or similar dimensions as the presently displayed document page, such that the annotation image can be superimposed over the document page. Combinations of these approaches are of course possible. For example, opaque annotations could be stored in a data structure, while highlighting could be stored as a bitmap image.
According to one embodiment, document browser 801 generates a title change event to annotation editor 803 each time a different document page is selected through document browser 801. This permits annotation editor 803 to retrieve previously stored annotations for a page, and to create a new annotation file for a newly displayed page. Annotation editor 803 intercepts stylus movements from a stylus or other cursor movement device and provides them to document browser 801 after any annotation processing has been performed. In one embodiment, browser 801 can constantly generate “screen paint” commands that are intercepted so that a blended image is continuously generated.
Annotation editor 803 can be implemented as an Active-X® control element, as an Applet, or as other forms of software functions. Annotation editor 803 and any related functions can be embedded into a document viewed through browser 801, such that viewing the document provides the annotation functions.
FIG. 9A shows a flowchart indicating various steps that can be executed to provide an annotation function according to one embodiment. It will be appreciated that many different approaches for carrying out the inventive principles are possible, and the steps shown are intended to be exemplary only. For example, although the steps are illustrated as being performed sequentially, they can in fact be performed by different components at different times in an object-oriented system using event-driven processing techniques. The steps shown can be implemented in software that is stored on a storage medium such as a disk.
Beginning in step 901, a stylus “down” event is detected. As noted previously, any of various input devices such as a mouse with key clicks or others can be used. In step 902, a test is performed to determine whether the annotation mode has been enabled. (See FIG. 4). If the annotation mode is not presently active, then in step 903 processing returns to the browser (i.e., the stylus movement command is passed through to document browser 801).
In step 904, after it has been determined that the annotation mode is active, the page identifier for the currently displayed page is retrieved. It is contemplated but not necessary that each document page have a unique identifier (e.g., a unique URL). In step 905, a test is performed to determine whether the currently displayed page has a previously existing “ink” or “annotation” file associated therewith. If such an ink file exists, it is retrieved from storage area 805 (see FIG. 8). If no such file exists, a new ink file is created in step 906, preferably using a name that readily corresponds to the displayed document page.
After an ink file has been retrieved or newly created, a test is performed in step 907 to determine whether the annotation mode is “ink” mode. If the current annotation mode is “ink” mode, then in step 911 opaque pixels are written into the ink file at the current stylus position. The number of pixels written can be varied depending on the width or “swath” to be used for the annotation. For a wide swath (e.g., a magic marker type of annotation), a plurality of pixels can be written surrounding the current stylus position. For a narrower swath (e.g., a pinpoint type of annotation), a smaller number of pixels (e.g., one pixel wide) can be written to the annotation file at the current stylus position. It is within the scope of the invention to permit the user to select or change the width of the annotation marks.
In step 914, a pixel blending operation is performed, such that the pixels in the ink file are blended with pixels from the document, which causes the document to be displayed with annotations. (As described above, opaque pixels may entirely replace those in the viewed document). In step 915, a test is performed to determine whether the stylus or other input device has been lifted or disengaged. If so, then in step 916 the ink layer is stored, and processing returns to the browser in step 917. Otherwise, annotations continue at step 902, and can be stored as part of the same stroke. If the user again presses the stylus or input device against the document, then annotations resume in step 901.
Returning to step 907, if the present mode is not “ink” mode, then a test is made in step 908 to determine whether highlight mode was selected. If highlight mode is active, then in step 912 translucent pixels are written at the current stylus position. For example, yellow, pink, or other translucent colors can be stored at the current stylus position. As before, the pixels are blended in step 914, changing the resulting pixels on output but nevertheless permitting the user to see the original document pixels in a modified form. Processing continues as described previously.
In step 908, if highlight mode is not currently active, then in step 909 a test is performed to determine whether erase mode is active. If so, then in step 913 the pixels at the current stylus position are cleared or zeroed out. As with highlight mode, the width of the erasure can be preset to a swath wider than one pixel, and the width can be different than the highlight or annotation pixel width. As before, the remaining non-erased pixels are blended with the original document image in step 914 and processing continues until the ink layer is stored.
FIG. 9B shows a flowchart indicating how previously created annotations can be superimposed over a document page. In step 918, a title change event is detected in document browser 801, and is sent to annotation editor 803. In various embodiments, a title change event occurs whenever the presently viewed document page changes. This may occur when the user jumps to a new document page, or when the user moves forward or backward among a sequence of related document pages, such as might occur in a book or a set of related hyperlinks. Other types of events, such as a “status change” event, for example, can be used instead of a title change event.
In step 919, a test is performed to determine whether an ink layer already exists for the new document page. If no ink layer exists for the page, processing returns to the document browser and the page is displayed normally. If an ink layer exists for the page, then in step 920 the ink layer is retrieved. In step 921, the pixels from the retrieved ink layer are blended with the displayed page and the resulting image appears on the computer display. Thereafter, processing returns to the browser. A separate ink layer file can be created for each document page, or one ink file can be created for an entire document and indexed according to pages on which the annotations appear. Other approaches are of course possible.
Thus has been described a system, method, and apparatus for annotating electronic document pages using an annotation editor that stores annotations independently of the content of the underlying document. It will be appreciated that many modifications and variations of the invention are possible, and the scope of the invention is not limited by the specific examples and descriptions herein.
(g) if the second end portion of the stylus is being moved across the computer display device, then selecting an eraser annotation mode.
2. The computer-implemented method of claim 1, further comprising the step of blending pixels in the annotation file with pixels in the electronic document to cause the computer display device to display the electronic document with annotations.
3. The computer-implemented method of claim 2, wherein blending pixels comprises execution of an alpha blending function.
if the second end portion of the stylus is being moved across the display device, then select an eraser annotation mode.
5. The computer-readable storage medium of claim 4, storing further computer-executable instructions that, when executed by the computer, cause the computer to blend pixels in the annotation file with pixels in the electronic document to cause the display device to display the electronic document with annotations.
6. The computer-readable storage medium of claim 5, wherein blending pixels comprises execution of an alpha blending function.
8. The computer system of claim 7, wherein the memory stores further processor-executable instructions that, when executed by the processor, cause the processor to blend pixels in the annotation file with pixels in the electronic document to cause the display device to display the electronic document with annotations.
9. The computer system of claim 8, wherein blending pixels comprises execution of an alpha blending function.
"Adobe Acrobat 3.0 Review", http://www.hmug.org/Reviews/, Mar. 1997, 1-18.
"Bizweb2000.com-screenshots of an e-book", http://web.archive.org/web/*/http://www.bizweb2000.com/eshots.htm, published on May 1999, 1-4.
"Bizweb2000.com—screenshots of an e-book", http://web.archive.org/web/*/http://www.bizweb2000.com/eshots.htm, published on May 1999, 1-4.
"Explore the Features of the Rocket eBook", wysiwyg://212http://www.rocketbook.com/Products/Tour/Index.html.
"Hucklefine Defined", http://www.ylem.org/artists/mmosher/huck.html, Apr. 1990, 1-3.
"Joke eBook", PrimaSoft PC, Inc., Electronic Book Series Version 1.0, Jul. 1998, 1-5.
"Rocket eBook Using the Rocket eBook", http://www.rocketbook.com/Products/Faq/using.html.
"Softbook.RTM. Press the Leader in Internet-Enabled Document Distribution and Reading Systems", http://www.softbook.com/consumer/reader.asp.
"Tour of Korea Hypercard Stack", Grose Educational Media, "http://www.entrenet.com/.about.groedmed/kor2.html", 1996, 1-2.
aha! 2.0 for Windows InkWriter The Power of Word Processing, The Convenience of Pen and Paper, (1995), 2 pages.
aha! Inkwriter of Magic Cap the Fastest, Most Convenient Way to Create Faxes, Notes and Messages, (1995), 2 pages.
aha! Inkwriter The Simplicity of Pen and Paper, the Power of Word Processing, (1995), 2 pages.
aha! Software Products, Web Page List of Products, Retrieved from: http://www.ahasoft.com//product.htm on Sep. 24, 1997 Aha Software Corporation, Mountain View, CA (1995), 5 pages.
Catlin, et al. "InterNote: Extending a Hypermedia Framework to Support Annotative Collaboration," Institute for Research in Information and Scholarship (IRIS), Brown University, Nov. 1989, pp. 365-378.
Chiu et al., "NoteLook: Taking Notes in Meetings with Digital Video and Ink", Proceedings of ACM Multimedia'99, Oct. 1999, 10 pages.
Crespo et al., "Responsive interaction for a large Web application: The meteor shower architecture in the WebWriter II Editor", 1997, 15 pages.
European Communication dated Jun. 17, 2004, in Application No. 00980988.0 (2 pages).
European Communication dated Mar. 7, 2008, in Application No. 00980988.0 (4 pages).
European Communication dated May 8, 2007, in Application No. 00980988.0 (3 pages).
European Communication dated Oct. 26, 2007, in Application No. 00980988.0 (3 pages).
Graefe et al, "Designing the muse: A Digital Music Stand for the Symphony Musician", Proceedings of Conference on Human Factors in Computing Systems, Apr. 13-18, 1996, 436-441.
Greenberg, "A Fisheye Text Editor for Relaxed-WYSIWIS Groupware", Chi'96, Conference companion on Human factors in computing systems: common ground, 1996, 2 pages.
Hirotsu et al., " Cmew/U-a multimedia Web annotation sharing system ", NTT Network Innovation Laboratories-Japan, Proceedings of the IEEE Region 10 Conference, TENCON 99, Sep. 15-17, 1999, 1, 356-359.
International Search Report mailed Feb. 27, 2001, in Application No. PCT/US00/33129 (29 pages).
Japanese Notice of Allowance mailed Aug. 21, 2009, in Application No. 2001-544200 (6 pages).
Japanese Notice of Decision of Final Rejection mailed Oct. 28, 2008, in Application No. 2001-544200 (5 pages).
Japanese Notice of Rejection dated Apr. 24, 2009, in Application No. 2001-544200 (6 pages).
Japanese Notice of Rejection mailed Feb. 1, 2008, in Application No. 2001-544200 (14 pages).
Kristensen, A. "Formsheets and the XML Forms Language" (Mar. 1999), downloaded from the Internet on May 13, 2003 (16 pages).
Kunikazu, T. Patent Abstracts of Japan, Publication No. 11327789 for Color Display and Electronic Blackboard System, published Nov. 30, 1999.
Kuo et al., "A Synchronization Scheme for Multimedia Annotation", Multimedia Information Networking Laboratory, Tamkang University-Taiwan, IEEE International Conference on Systems, Man, and Cybernetics (Computational Cybernetics and Simulation), Oct. 12-15, 1997, 1, 594-598.
Landay et al., "Making Sharing Pervasive: Ubiquitous Computing for Shared Note Taking", IBM Systems Journal, 1999, 38(4), 531-550.
Landay, "Using Note-Taking Appliances for Student Collaboration", 29th ASEE/IEEE Frontiers in Education Conference, IEEE Computer Society, Nov. 10-13, 1999, 12 c4/15-12c4/20.
Marshall, "Annotation from paper books to the digital library", ACM International Conf. on Digital Libraries, 1997, 10 pages.
Microsoft Corporation, Word 2000 (9.0 6926 Sp-3), 1999.
Munyan, "Everybook, Inc: Developing the E-Book in Relation to Publishing Standards", http://www.futureprint.kent.edu/articles/munyan01.htm, accessed, Sep. 1998, 1-7.
Nuvomedia, Inc. "Using the Rocket eBook," Retrieved from: http://www.rocketbook.com/Products/Faq/using.html, (1999) pp. 1-2.
Open eBook Forum, Open eBookTM Publication Structure 1.0, Sep. 16, 1999, downloaded on May 14, 2003 from http://www.ebxwg.org/oebps/eobps1.0/download/oeb1-oebps.htm (66 pages).
PCT Application PCT/US00/33082, International Search Report mailed Feb. 27, 2001, 40 pages.
PCT Application PCT/US00/33127, International Search Report mailed.
PhotoImpact 3.0, Ulead Systems Inc., 1996 (8 pages).
Schilit et al., "Digital Library information Appliances", Proceedings of the third ACM conference on Digital Libraries, Jun. 23-26, 1998, 217-226.
U.S. Appl. No. 09/455,754, Advisory Action mailed Oct. 5, 2005 (3 pages).
U.S. Appl. No. 09/455,754, Advisory Action mailed Sep. 28, 2004 (3 pages).
U.S. Appl. No. 09/455,754, Amendment and Response filed Apr. 27, 2005 (13 pages).
U.S. Appl. No. 09/455,754, Amendment and Response filed Jul. 21, 2004 (13 pages).
U.S. Appl. No. 09/455,754, Amendment and Response filed Mar. 1, 2004 (4 pages).
U.S. Appl. No. 09/455,754, Amendment and Response filed Mar. 27, 2006 (8 pages).
U.S. Appl. No. 09/455,754, Amendment and Response filed Oct. 27, 2003 (17 pages).
U.S. Appl. No. 09/455,754, Amendment and Response filed Sep. 13, 2005 (11 pages).
U.S. Appl. No. 09/455,754, Amendment filed May 8, 2003 (3 pages).
U.S. Appl. No. 09/455,754, Appeal Brief filed Feb. 8, 2007 (17 pages).
U.S. Appl. No. 09/455,754, Examiner's Answer to Appeal Brief mailed Jul. 2, 2007 (12 pages).
U.S. Appl. No. 09/455,754, Final Rejection mailed Jul. 13, 2005 (10 pages).
U.S. Appl. No. 09/455,754, Final Rejection mailed Jun. 8, 2006 (10 pages).
U.S. Appl. No. 09/455,754, Final Rejection mailed May 21, 2004 (10 pages).
U.S. Appl. No. 09/455,754, Non-Final Rejection mailed Dec. 27, 2005 (10 pages).
U.S. Appl. No. 09/455,754, Non-Final Rejection mailed Jan. 27, 2005 (10 pages).
U.S. Appl. No. 09/455,754, Non-Final Rejection mailed May 27, 2003 (9 pages).
U.S. Appl. No. 09/455,754, Patent Board Decision mailed Jun. 23, 2009 (16 pages).
U.S. Appl. No. 09/455,754, Reply Brief filed Sep. 4, 2007 (5 pages).
U.S. Appl. No. 09/455,805, Advisory Action mailed Feb. 24, 2004 (2 pages).
U.S. Appl. No. 09/455,805, Advisory Action mailed Feb. 24, 2006 (2 pages).
U.S. Appl. No. 09/455,805, Amendment After Final filed Jan. 26, 2006 (113 pages).
U.S. Appl. No. 09/455,805, Amendment and Response filed Aug. 14, 2007 (12 pages).
U.S. Appl. No. 09/455,805, Amendment and Response filed Aug. 23, 2006 (12 pages).
U.S. Appl. No. 09/455,805, Amendment and Response filed Feb. 12, 2004 (12 pages).
U.S. Appl. No. 09/455,805, Amendment and Response filed Jun. 18, 2003 (13 pages).
U.S. Appl. No. 09/455,805, Amendment, Response and Affidavit filed Aug. 11, 2005 (117 pages).
U.S. Appl. No. 09/455,805, Appeal Brief filed May 17, 2004 (25 pages).
U.S. Appl. No. 09/455,805, Final Rejection mailed May 15, 2007 (17 pages).
U.S. Appl. No. 09/455,805, Final Rejection mailed Oct. 31, 2005 (16 pages).
U.S. Appl. No. 09/455,805, Final Rejection mailed Sep. 16, 2003 (13 pages).
U.S. Appl. No. 09/455,805, Non-Final Rejection mailed Mar. 24, 2003 (9 pages).
U.S. Appl. No. 09/455,805, Non-Final Rejection mailed May 2, 2005 (13 pages).
U.S. Appl. No. 09/455,805, Non-Final Rejection mailed May 23, 2006 (14 pages).
U.S. Appl. No. 09/455,805, Notice of Allowance mailed Oct. 17, 2007 (6 pages).
U.S. Appl. No. 09/455,806, Amendment and Response filed Dec. 22, 2003, 13 pages.
U.S. Appl. No. 09/455,806, Amendment and Response filed Jul. 16, 2003, 10 pages.
U.S. Appl. No. 09/455,806, Amendment and Response filed Oct. 19, 2004, 4 pages.
U.S. Appl. No. 09/455,806, Notice of Allowance mailed Sep. 14, 2004, 9 pages.
U.S. Appl. No. 09/455,806, Office Action mailed Apr. 16, 2003, 6 pages.
U.S. Appl. No. 09/455,806, Office Action mailed Sep. 25, 2003, 9 pages.
U.S. Appl. No. 09/455,807, Advisory Action mailed Jun. 27, 2003, 2 pages.
U.S. Appl. No. 09/455,807, Amendment and Response filed Aug. 23, 2004, 15 pages.
U.S. Appl. No. 09/455,807, Amendment and Response filed Jan. 13, 2005, 12 pages.
U.S. Appl. No. 09/455,807, Amendment and Response filed Jan. 21, 2003, 6 pages.
U.S. Appl. No. 09/455,807, Amendment and Response filed Jun. 6, 2003, 9 pages.
U.S. Appl. No. 09/455,807, Amendment and Response filed Mar. 30, 2004, 9 pages.
U.S. Appl. No. 09/455,807, Amendment and Response filed Sep. 5, 2003, 8 pages.
U.S. Appl. No. 09/455,807, Notice of Allowance mailed May 31, 2005, 7 pages.
U.S. Appl. No. 09/455,807, Notice of Allowance mailed Sep. 19, 2005, 6 pages.
U.S. Appl. No. 09/455,807, Office Action mailed Apr. 9, 2003, 8 pages.
U.S. Appl. No. 09/455,807, Office Action mailed Dec. 30, 2003, 7 pages.
U.S. Appl. No. 09/455,807, Office Action mailed Jul. 19, 2002, 8 pages.
U.S. Appl. No. 09/455,807, Office Action mailed Jun. 15, 8 pages.
U.S. Appl. No. 09/455,807, Office Action mailed Nov. 29, 2004, 8 pages.
U.S. Appl. No. 09/455,808, Amendment and Response filed Sep. 10, 2003, 8 pages.
U.S. Appl. No. 09/456,975, Amendment and Response Aug. 7, 2003 (9 pages).
U.S. Appl. No. 09/456,975, Amendment and Response filed Aug. 20, 2013 (11 pages).
U.S. Appl. No. 09/456,975, Amendment and Response filed Feb. 10, 2004 (8 pages).
U.S. Appl. No. 09/456,975, Amendment and Response filed Jan. 15, 2003 (17 pages).
U.S. Appl. No. 09/456,975, Amendment and Response Jun. 27, 2003 (12 pages).
U.S. Appl. No. 09/456,975, Final Office Action mailed Mar. 27, 2003 (10 pages).
U.S. Appl. No. 09/456,975, Non-Final Office Action mailed Nov. 10, 2003 (12 pages).
U.S. Appl. No. 09/456,975, Non-Final Office Action mailed Oct. 22, 2002 (8 pages).
U.S. Appl. No. 09/456,975, Notice of Allowance mailed May 18, 2004 (8 pages).
U.S. Appl. No. 10/460,226, Amendment and Response filed Mar. 20, 2007, 10 pages.
U.S. Appl. No. 10/460,226, Notice of Allowance mailed Jul. 6, 2007, 2 pages.
U.S. Appl. No. 10/460,226, Notice of Allowance mailed May 21, 2007, 7 pages.
U.S. Appl. No. 10/460,226, Office Action mailed Dec. 20, 2006, 7 pages.
U.S. Appl. No. 10/875,174, Amendment and Response filed Jan. 22, 2008 (10 pages).
U.S. Appl. No. 10/875,174, Amendment and Response filed Jun. 7, 2007 (6 pages).
U.S. Appl. No. 10/875,174, Amendment and Response filed Nov. 15, 2006 (7 pages).
U.S. Appl. No. 10/875,174, Final Rejection mailed Feb. 7, 2007 (8 pages).
U.S. Appl. No. 10/875,174, Non-Final Rejection mailed Aug. 20, 2007 (10 pages).
U.S. Appl. No. 10/875,174, Non-Final Rejection mailed Aug. 23, 2006 (8 pages).
U.S. Appl. No. 10/875,174, Notice of Allowance mailed Oct. 20, 2008 (7 pages).
U.S. Appl. No. 10/891,050, Amendment and Response filed Apr. 6, 2007 (11 pages).
U.S. Appl. No. 10/891,050, Amendment and Response filed Nov. 15, 2006 (9 pages).
U.S. Appl. No. 10/891,050, Amendment and Response filed Oct. 9, 2007 (10 pages).
U.S. Appl. No. 10/891,050, Final Rejection mailed Dec. 19, 2007 (11 pages).
U.S. Appl. No. 10/891,050, Final Rejection mailed Feb. 6, 2007 (9 pages).
U.S. Appl. No. 10/891,050, Non-Final Rejection mailed Aug. 7, 2006 (8 pages).
U.S. Appl. No. 10/891,050, Non-Final Rejection mailed Jun. 25, 2007 (10 pages).
U.S. Appl. No. 11/224,936, Notice of Allowance mailed May 21, 2009, 6 pages.
U.S. Appl. No. 11/224,936, Office Action mailed Oct. 17, 2008, 4 pages.
U.S. Appl. No. 11/234,268, Notice of Allowance mailed Dec. 16, 2008, 10 pages.
U.S. Appl. No. 11/964,457, Amendment and Response mailed Dec. 29, 2010 (10 pages).
U.S. Appl. No. 11/964,457, Non-Final Rejection mailed Sep. 29, 2010 (9 pages).
U.S. Appl. No. 11/964,457, Notice of Allowance mailed Mar. 1, 2011 (16 pages).
U.S. Appl. No. 12/466,721, Amendment and Response filed Jul. 17, 2012, 11 pages.
U.S. Appl. No. 12/466,721, Amendment and Response filed May 10, 2013, 10 pages.
U.S. Appl. No. 12/466,721, Amendment and Response filed Sep. 28, 2012, 13 pages.
U.S. Appl. No. 12/466,721, Office Action mailed Apr. 17, 2012, 9 pages.
U.S. Appl. No. 12/466,721, Office Action mailed Aug. 1, 2012, 10 pages.
U.S. Appl. No. 12/466,721,, Notice of Allowance mailed Jun. 4, 2013, 7 pages.
U.S. Appl. No. 13/175,109, Amendment and Response filed Apr. 1, 2013, 8 pages.
U.S. Appl. No. 13/175,109, Notice of Allowance mailed Apr. 22, 2013, 9 pages.
U.S. Appl. No. 13/175,109, Notice of Allowance mailed Jul. 8, 2013, 9 pages.
U.S. Appl. No. 13/175,109, Office Action mailed Dec. 31, 2021, 12 pages.

References: Application No. 00980988
 Application No. 00980988
 Application No. 00980988
 Application No. 00980988
 Application No. 2001
 Application No. 2001
 Application No. 2001
 Application No. 2001