US20080109720A1 - Structured document browser - Google Patents

Structured document browser Download PDF

Info

Publication number
US20080109720A1
US20080109720A1 US11/710,230 US71023007A US2008109720A1 US 20080109720 A1 US20080109720 A1 US 20080109720A1 US 71023007 A US71023007 A US 71023007A US 2008109720 A1 US2008109720 A1 US 2008109720A1
Authority
US
United States
Prior art keywords
processor
display
selectors
selector
cause
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/710,230
Inventor
Robert Schumacher
James Matthews
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
RPX Corp
Original Assignee
AT&T Intellectual Property I LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AT&T Intellectual Property I LP filed Critical AT&T Intellectual Property I LP
Priority to US11/710,230 priority Critical patent/US20080109720A1/en
Publication of US20080109720A1 publication Critical patent/US20080109720A1/en
Assigned to AT&T INTELLECTUAL PROPERTY 1, L.P. reassignment AT&T INTELLECTUAL PROPERTY 1, L.P. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: SBC PROPERTIES, L.P.
Assigned to RPX CORPORATION reassignment RPX CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AT&T INTELLECTUAL PROPERTY I, L.P.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0623Item investigation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/957Browsing optimisation, e.g. caching or content distillation
    • G06F16/9577Optimising the visualization of content, e.g. distillation of HTML documents
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G06F16/986Document structures and storage, e.g. HTML extensions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0489Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using dedicated keyboard keys or combinations thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/103Formatting, i.e. changing of presentation of documents
    • G06F40/106Display of layout of documents; Previewing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/12Use of codes for handling textual entities
    • G06F40/14Tree-structured documents
    • G06F40/143Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241Advertisements
    • G06Q30/0277Online advertisement
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0641Shopping interfaces

Definitions

  • This invention relates to computer applications for viewing documents, and in particular, to a computer program for viewing documents having a predefined structure.
  • GUI graphical user interface
  • GUI's are generated using a set of software tools that put graphical objects on the computer display.
  • One of these graphical objects is a screen pointer that the user controls with a mouse or a trackball. The user moves the mouse to position the pointer on the screen over selected objects on the screen.
  • the user can select an object by using a selecting device which is typically a mouse switch. By selecting an object, the user instructs the operating system or an application to execute the function associated with the object.
  • the GUI objects can include the graphical representation of buttons, menus or any other graphic object.
  • GUI's are the foundation of hypertext and hypermedia applications. Such applications allow computer users to create interfaces in which graphical objects are configured to correspond, or to link to objects of information. For example, a user may create an interface having the graphical representation of a button to display a motion video by selecting the button with a screen pointer. Similarly, the button can be configured to make a sound, display an image or display a separate text file.
  • SGML Standard Generalized Markup Language
  • SGML was developed by the International Standards Organization and has been adopted by the Department of Defense and other government agencies as a way of standardizing documentation.
  • SGML is machine-based in a manner similar to a computer language.
  • An SGML Document Type Definition (DTD) may be defined according to the specifications of SGML for a given document structure. The DTD defines elements to be embedded in a document. The documents are then viewed using a viewer or browser that interprets the elements in the document according to the data structure defined in the DTD.
  • DTD SGML Document Type Definition
  • HTML HyperText Markup Language
  • Browsers display the documents according to stylesheets associated with the embedded codes.
  • stylesheets contain rules or instructions that dictate the appearance of a document as presented by a browser.
  • Stylesheets may also contain references to other documents in different computers. These references may be used in conjunction with context-sensitive regions of the documents such that a user retrieves the document reference by selecting the region. In this manner, an author links one document to others in a meaningful way such that a viewer may provide a user with access to information in documents that are linked together in a web-like fashion.
  • the links to information are presented solely within documents.
  • the links may take the user to other documents or to locations within the same document, but typically, the elements that provide the link-control are within the documents.
  • a structured document browser is provided with a user interface that remains uniform and familiar as the user browses documents according to their structure instead of their contents.
  • the browser uses codes embedded in the document to identify sections of the structure of the document.
  • the user interface includes graphical user interface objects, such as buttons, that are configured to display a standard section of the document structure when selected by the user.
  • the structured document browser may also include menus that allow a user to select a document from among different documents, or a document structure type from among different structure types.
  • FIG. 1 is a block diagram of a preferred embodiment of the structured document browser showing how it communicates with other components of the computer.
  • FIG. 2 illustrates a sample structure for a document.
  • FIG. 3 illustrates a portion of a document having the structure shown in FIG. 2 after it has been marked with SGML tags.
  • FIG. 4 illustrates an SGML document type definition (DTD) created for use by a structured document browser for a document having the structure shown in FIG. 2 .
  • DTD SGML document type definition
  • FIG. 5 is a representation of an example of a user interface of the structured document browser for FIG. 1 .
  • FIG. 6 is a flow chart showing the process of retrieving a structured document and illustrates playing the section of a document in response to the selection of a button.
  • FIG. 7 illustrates an example of a bks data structure.
  • FIG. 8 is a diagram that shows the interaction between a button, a map file and bit map file.
  • FIGS. 9A & 9B illustrate the operation of the browser of FIG. 1 .
  • FIG. 10 illustrates one example of an alternative implementation of the user interface.
  • FIG. 11 illustrates a second alternative implementation of the user interface.
  • FIG. 12 illustrates a third alternative implementation of the user interface.
  • FIG. 13 illustrates a fourth alternative implementation of the user interface.
  • a presently preferred embodiment of this invention includes an application program called browser.exe that has been developed using the ‘c’ programming language in the Windows environment.
  • the browser.exe executable file is programmed to make function calls to three dynamic link libraries named sit.dll, cgrmzv.dll and ct13d.dll.
  • These libraries are components of Dynatext Version 2.0, a user interface development system from Electronic Book Technologies, Inc.
  • Dynatext libraries provide functions that implement the SGML related functions and the graphic input/output functions. Further information regarding the Dynatext program may be obtained by contacting Electronic Book Technologies, Inc. at One Richmond Square, Buffalo, R.I. 02906.
  • the browser.exe program uses data structures in several support files that are in the same directory tree as browser.exe. These support files will be described in more detail in the description that follows.
  • a listing of the present version of browser.exe is attached as Appendix I of this specification.
  • the listing is an octal representation of browser.exe.
  • the presently preferred embodiment may be carried out by converting the octal to a binary executable file using methods that are well known in the art. After conversion, the browser.exe file may be executed from a directory that includes the dynamic link libraries and the support files described in this disclosure.
  • FIG. 1 is a block diagram describing at a high level the browser 80 in the computing environment.
  • the components of the browser 80 in its operating environment include the browser 80 itself, an operating system 104 with GUI capabilities, storage media 108 , a keyboard 110 , a pointing device 100 , a selecting device 102 and a monitor 112 .
  • the operating system 104 further includes an I/O system 114 and a GUI system 116 .
  • the double headed arrows 118 denote the communication between the respective components.
  • the communication at 118 may entail communication over a network where appropriate.
  • the hardware devices 108 , 110 , 100 , 102 , 112 may be implemented by choosing from among many alternatives for each device.
  • a pointing device 100 may be implemented using a mouse, a trackball or any other device that controls the position of a screen pointer.
  • a selecting device 102 is typically implemented with mouse buttons or buttons that operate in conjunction with a trackball. In general, any device that may be used to effect the selection of an object at the location of the screen pointer may be used as a selecting device 102 .
  • a selecting device 102 ′ may even include a key on the keyboard 110 .
  • the storage media 108 is understood to include random access memory (RAM), the temporary storage out of which programs are executed as well as the mass storage devices in which programs are stored.
  • the hardware devices 108 , 110 , 100 , 102 , 112 are understood to include the software drivers necessary for their operation in the computing environment.
  • the browser 80 includes at least a controller 82 and a system interface 84 .
  • the system interface 84 is responsible for processing the communication between the browser 80 and the operating system 104 , the I/O system 114 and the GUI system 116 .
  • the controller 82 receives and interprets requests from the system interface 84 to perform a browser function.
  • the system interface 84 receives signals from the I/O system 114 that the pointing device 100 and the selecting device 102 were used to press a button or icon, to request a display of a section of a document.
  • the controller 82 receives the information from the system interface 84 to determine which document section to display.
  • the system interface 84 includes the functions provided by the Dynatext development system and any operating system or I/O system functions.
  • the controller 82 in a preferred embodiment is the executable program browser.exe. It is to be understood that the diagram in FIG. 1 is by way of illustration and is not intended to limit the software structure chosen to carry out the invention.
  • the browser 80 operates with documents that have been prepared as described below. Because the browser 80 is designed to navigate documents according to their structure, the utility of the browser 80 is maximized when an organization establishes a standard structure for its key documents.
  • a software engineering group for example may find it desirable to maintain a uniform structure for the software requirement specifications that the group develops.
  • a different structure is desirable for the group's design specifications, and yet a different structure works for the group's test documentation. The group's goal for such documentation is to maintain uniformity.
  • a marketing group might maintain product descriptions for its company's product line in documents having the predefined document structure 10 .
  • This structure is predefined to have headings 12 that provide overview information, sales information, product availability information, ordering information, billing information, troubleshooting information and product support information.
  • the structure also has sub-headings 14 within each heading where relevant.
  • the overview section 16 has sub-headings 14 for sections devoted to a product description, aliases, product features and instructions on how to use the product.
  • a specific document of the predefined structure in FIG. 2 is marked with codes for viewing with the browser 80 .
  • codes are used to mark the document as shown in FIG. 3 .
  • the codes shown in FIG. 3 have angle brackets around them.
  • the codes are SGML elements. These codes may be replaced by elements of other markup tools in alternative embodiments.
  • the application identification code 22 indicates that the document has been marked for use by the browser 80 .
  • the overall document structure is identified with a product name code 24 .
  • Each standard structure component is then marked with an appropriate code or element.
  • the sections in a document are preferably marked according to a convention.
  • the beginning of a section is marked by a code or element.
  • the ⁇ OVER> element 26 identifies the beginning of the section of the document that provides an overview of the product.
  • the ⁇ OVER> element 26 is followed by the heading and text that constitute the Overview section of the document.
  • a begin section name element 28 indicates that the information that follows the element 28 specifies the name that will appear in all documents of the same structure for that section.
  • the name of the overview section is “Overview” 30 .
  • an end section name element 32 indicates the end of that section name such that the text between the begin section name element 28 and the end section name element 32 is the text 30 that will appear in the heading.
  • an end section element 34 indicates the end of the section.
  • the element ⁇ /OVER> 34 marks the end of the overview section. The convention of marking the beginning and the end of parts of the document is used to mark other sections (as shown at 36 , 38 , 39 and 42 ) that form the standard document structure.
  • Begin sub-section elements 38 and end sub-section elements 42 mark the sub-sections of the document, using the same convention, with the stipulation that the end elements 39 are in an order that keeps the sub-sections nested within the sections.
  • Documents may have sub-sections within sub-sections.
  • the structure of documents is defined by a document type definition (DTD).
  • the DTD 40 in FIG. 4 illustrates how a document structure is represented in SGML.
  • Codes such as those referenced at 24 , 25 , 26 and 38 , that are used to indicate a section or structure part of the document as shown in FIG. 3 are defined by setting an element name, as shown at 42 and 44 in FIG. 4 ; setting a heading name, as shown at 47 and 49 ; and listing sub-parts as shown at 46 .
  • the code for the product name 24 in FIG. 3 is defined in the DTD 40 as the element name 42 for the high level document structure composed of the list of sections 46 .
  • the list of sections 46 comprises the codes defining the sections of the document.
  • the codes used in FIG. 3 for the begin section codes 25 are defined in the DTD 40 of FIG. 4 as element names 44 for the respective section level data structures.
  • the respective name codes such as the begin section name element 27 in FIG. 3 , is shown as part of a section, as shown at 45 in FIG. 4 .
  • the name element 45 is also defined at 51 . If a section has sub-parts, or sub-sections, the codes for the sub-sections within the section are listed in the definition of the section code as shown at 48 . Each sub-section code is then defined individually as shown at 43 . More details on the syntax and constructs of SGML may be obtained by referring to the ISO Standard for SGML ISO 8879: 1986/A1: 1988(E).
  • a document having a basic word processing format may be converted to a marked document 20 , also known as an SGML instance, using an SGML utility.
  • a utility called DYNATAG from Electronic Book Technologies, Inc. uses documents having the structure described in FIG. 2 to create a DTD 40 , illustrated in FIG. 4 , as well as an SGML instance 20 , illustrated in FIG. 3 .
  • Other SGML utilities may be used to create DTD's and SGML instances.
  • the discussion of the DTD 40 is presented to illustrate how alternative embodiments might implement a program that interprets SGML DTD's to operate with the browser.
  • DTD's may be used, including common DTD's such as the HTML DTD.
  • other embodiments of this invention may not use SGML as a markup language. Any other suitable markup language, including a proprietary markup language, may be used as well, provided that the appropriate software components are available to translate the code.
  • Other embodiments of this invention may be designed to support the use of more than one markup language.
  • the browser 80 may be started on a computer.
  • the user invokes the browser 80 by using the pointing device 100 and the selecting device 102 to select the browser 80 in a manner dictated by the GUI of the operating system 104 .
  • the operating system 104 is the Windows Operating System (Version 3.1 and later for purposes of this example)
  • the pointing device 100 is a mouse
  • the selecting device 102 includes a pair of mouse buttons (left and right buttons).
  • the Windows user interface 106 as it appears on the monitor 112 , includes a menu bar 68 , icons 66 representing application programs ready for initialization and a screen pointer 62 controlled by the user with the mouse pointing device 100 .
  • the mouse 100 may be used to place the screen pointer 62 over the browser icon 64 in the operating system interface 106 and the left mouse button may be double-clicked.
  • the graphical user interface changes from the Windows user interface 106 in FIG. 1 to that of the browser user interface as shown at 50 in FIG. 5 .
  • the user interface 50 of the browser 80 gives the user the capability of selecting a particular document and then selecting different sections of the document for display.
  • the objects used to browse through the documents remain on the user interface 50 regardless of where in a document a user is browsing.
  • the user interface remains familiar to the user and responsive to the document structure.
  • the user interface so of the browser 80 includes a document menu 52 , a document type menu 54 , a first row of selectors 56 , a second row of selectors 58 and a display window 60 .
  • the user selects a document for browsing by using the document menu 52 .
  • the document menu 52 is implemented with standard graphical user interface menu objects such that the user selects a document menu arrow 70 to display the full menu of the documents available.
  • the user then selects the document desired from the menu using the selecting device 102 in combination with the screen pointer 62 .
  • the user interface 50 of the browser 80 is configured in a manner that allows the document types, or standard structures of different types, to be listed in a document type menu 54 .
  • the document type is selected by the user in the same manner that the user selects a document.
  • the name of the document type is the name or alias of directories designated by the browser to have documents of a consistent structure.
  • the names listed in the document menu are changed according to the names of the available documents having the new document type.
  • selectors 56 , 58 are examples of document navigation tools that may be used for browsing documents in a presently preferred embodiment. More specifically, selectors 56 , 58 are display regions in the user interface that are configured to perform pre-defined operations when the user places the screen pointer 62 over one of the selectors 56 , 58 and then selects it with the selecting device 102 . In the presently preferred embodiment, the display regions are depicted as icons that make them look like buttons with graphic images on them. The image may be designed to convey a sense of the operation to be performed if the icon is selected.
  • the first row of selectors 56 is configured to correspond to the first level of sections in a document.
  • the first selector 68 in the first row 56 is configured to correspond to the Overview section 16 in the document shown in FIG. 2 .
  • Each selector is configured so that when the user places the screen pointer 62 over the selector and then selects it with the selecting device 102 , the system interface 84 (described above with reference to FIG. 1 ) receives data indicating which selector was selected. The system interface 84 may then determine the document section associated with the selector and send the request to display that section to the controller 82 (described above with reference to FIG. 1 ). Alternatively, the system interface 84 may send to the controller 82 the identification of the chosen selector and let the controller 82 determine what section to display. The controller 82 will cause the document to be searched for the document section that matches the selector chosen. When the chosen section is found, the browser 80 displays in the display window 60 the section of the document structure that corresponds to the selector.
  • the user may navigate within the section by selecting one of the second row of selectors 58 .
  • the second row of selectors 58 is configured to correspond to the sub-sections 14 within the section 12 being displayed (as shown in FIG. 2 ).
  • a document structure having sub-sections within its sub-sections may also be accommodated so that three rows of selectors might be present in the user interface.
  • the number of sub-sections within sections of a document may be further accommodated with rows of selectors as desired, or as limited by system constraints, such as the size of the display window 60 .
  • the user may also navigate within the section by controlling the display window scroll bar 96 with the screen pointer 62 and the selecting device 102 .
  • documents are converted into “books” which are actually directory trees that reside in a directory called the “ ⁇ xyz ⁇ books” directory.
  • books are actually directory trees that reside in a directory called the “ ⁇ xyz ⁇ books” directory.
  • selection and “library” are defined and used according to the specifications of the Dynatext development system.
  • DYNATAG creates a DTD (as shown in FIG. 4 ) and an SGML instance (as shown in FIG. 3 ) of the document.
  • the SGML instance and the DTD are used as input files to MKBOOK, another Dynatext utility.
  • the MKBOOK utility creates a binary instance of the document, a directory tree, or a “book,” and some of the support files used by the browser 80 .
  • the document for Widget having the structure for products descriptions defined in FIG. 2 is processed with MKBOOK to create the book “ ⁇ xyz ⁇ books ⁇ widget,” a sub-directory of “ ⁇ xyz ⁇ books.”
  • the browser 80 uses a number of data files to define how a document is found and displayed in the browser. These files and their names in the preferred embodiment are 1) the browser executable (browser.exe); 2) an initialization file (browser.ini); 3) a set of dynamic link libraries (sit.dll, cgmzv.dll, & ct13d.dll); 4) a bks file which is an ASCII file that contains information about a book, a library or collection of documents, and names in the browser menus (named *.bks where the * represents the name of a document); 5) a bitmap containing up to 100 regions for icons (named *.bmp or default.bmp) and 6) an ASCII file that provides the linking of the document element names to the icons in the bmp file and for pop-up text in the executable (named *.map or default.map).
  • FIG. 6 is a flowchart describing the steps taken to browse a document.
  • the operating system launches the browser.exe executable file as shown at block 120 .
  • This file is located in a directory called the “ ⁇ xyz” directory.
  • browser.exe When browser.exe is launched it first looks for the three required dynamic link libraries (DLL's) in the same directory as shown at block 122 .
  • the DLL's supplied by Electronic Book Technologies, contain functions related to the user interface, SGML processing and access to the books.
  • the browser checks for the browser.ini file as shown in 124 . If the browser.ini file is present, the browser 80 reads its contents, as shown at block 126 .
  • the browser.ini file contains objects, or data structures that include the [Files] object, the [DTEXT] object, and the [MAP] object.
  • the [FILES] object defines an annotation file.
  • the annotation file is a repository for feedback from users of the browser regarding the documents being reviewed.
  • the [DTEXT] object contains file names that the executable will use to find the location of the data directory, security key, and public and private directories.
  • the [MAP] object provides the file name of the initial map file that is to be loaded (typically, the name is “default.map”).
  • the map file as discussed in detail below, contains the associations between the document elements and the icons.
  • the browser checks for a file called default.bks at block 128 .
  • the default.bks file is an ASCII file which provides the browser with the information required to display a standard initial document, such as a document that displays a message of the day.
  • default.bks file If a default.bks file is not found, the browser initializes without a book as shown at 130 . Otherwise, the contents of default.bks are loaded as shown at 132 and the user interface is presented on the display to the user as shown at 134 .
  • the bks files will be described by reference to FIG. 7 .
  • the bks files are ASCII files that contain information about how the book should be loaded into the menus in the browser and which map file to use.
  • the bks file always begins with the [Book] object 140 in FIG. 7 .
  • the next line identifies the “collection.”
  • a collection also called a library, refers to the directory containing the books to which the browser 80 has access. In FIG. 7 , the collection is located in the “ ⁇ xyz” directory.
  • the next line in a bks file as shown in FIG. 7 identifies the collection title 144 which defines a document type for the document type menu 54 .
  • the collection title 144 is an alias for the group of books that will be listed under a heading in the document type menu 54 called “Products.”
  • the name of the book 146 is on the next line of the bks file.
  • the book name is actually the name of the directory tree that must be present under the collection path specified in line two 142 of the bks file.
  • the book title at 148 specifies an alias for the book.
  • the book title contains the name the user will see on the document menu 52 (at FIG. 5 ).
  • the map file name 150 is optional. It designates the map file that associates the tag names with the icons in the .bmp file. If specified, the browser will use the file name 152 to access the map file. Otherwise, the browser will assume a file name based on a pre-defined naming convention.
  • a user requests a document 160 by using the document menu 52 or the document type menu 54 in the user interface 50 (shown in FIG. 5 ).
  • the bks file is read in and the menu lists document and document type names according to the contents of the bks file.
  • the browser retrieves the document itself as shown at 162 and the map file associated with that document as shown at 164 .
  • the browser then verifies that the elements in the map file match the SGML DTD and the structure codes in the document as shown at 166 . If there are no discrepancies, the browser 80 reads the bmp file as shown at 168 which is specified in the map file. Also, in block 168 , the browser 80 locates fly-by text for description of icons. The bmp file allows the browser to display the icons as shown at 170 for the selectors 56 , 58 (in FIG. 5 ). The browser also displays the text in the chosen document as shown at 170 .
  • the user may select a section of the document to view by pressing a selector button that corresponds to that section as shown at 172 .
  • the correspondence between the selectors 56 , 58 and the document structure is established in the map file and in the bmp file. This correspondence will be described with reference to FIG. 8 .
  • FIG. 8 shows a portion of the map file 200 for the document having the structure in FIG. 2 , a bmp file 210 and the location on the user interface in which the selectors are placed 220 .
  • the first object in the map file is the [MAP] object 180 which identifies the data structure.
  • the next line in the map file is the icon line 182 which is a filename that is used by the browser 80 to obtain the bmp file for the structure corresponding to the map file.
  • the next line in the map file shown in FIG. 8 contains the [SECTIONS] object 184 .
  • the [SECTIONS] object 184 marks the beginning of a set of definitions of data structures 186 that help tie the selector icons to the sections in the document.
  • the order of these data structures indicates the order in which the sections appear in the document.
  • the RBW-DOC,PROD.NAME 190 label indicates that the section identified in this line is in the first or highest level section.
  • the OVER label 192 in the line matches the ⁇ OVER> tag 26 used to identify the overview section in the marked structure document shown in FIG. 3 .
  • the text following the colon at 194 is used in fly-by help or bubble help messages. For example, when the screen pointer 62 is positioned over an icon 222 as shown in FIG. 8 , a Help message 196 is displayed to indicate the function of the button.
  • FIG. 8 An example of the bmp file is shown in FIG. 8 at 210 .
  • the icons are stored in the bmp file as a single rectangular bitmap. Each icon is 16 pixels wide by 15 pixels high. In the presently preferred embodiment, the icons make the selectors appear to be buttons.
  • the icon index starts at 1 and proceeds from left to right. So the icon index might appear as follows: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 ⁇ etc>
  • FIG. 8 An example of how the map file relates to the bmp file is given in FIG. 8 .
  • the user moves the screen pointer 62 to the troubleshooting icon, which is the sixth selector or 222 in the top row of selectors 56 and then selects it.
  • the sixth button 222 corresponds to the sixth icon 224 in the bmp file.
  • the line at 226 defines the TROUBL element as the element that must be searched when the sixth button in the first row 222 is selected.
  • a prd.map provides the mappings for all books in the products (i.e., prd) library
  • a prd.bmp provides the icons for all books in the products (i.e., prd) library.
  • the icons should relate to the hierarchical structure of the document structure as specified in the document type definition.
  • FIGS. 9A & 9B demonstrate the operation of the browser 80 by illustrating the way in which the user interface 50 changes in response to the pressing of a button.
  • FIG. 9A shows the user interface 50 in an initial state with the Overview section 16 of the widget products document from FIG. 2 in the display window 60 .
  • the selectors 58 of the second row are represented by icons that correspond to the sub-sections 246 of the description section.
  • the user of the browser 80 may wish to view information that is known to exist in the troubleshooting section 18 of the widget product description. As shown in FIG. 2 , the troubleshooting section 18 is towards the end of the document. Standard documents may be as short as one printed page or long enough to fill several binders.
  • the browser 80 simplifies the retrieval of information by allowing access to a pre-defined section of a document by pushing a button.
  • the screen pointer 62 may be moved from an initial position 240 to the position over the icon for the troubleshooting button 222 .
  • the user selects the troubleshooting button 222 by enabling the selecting device 102 .
  • the browser 80 using the process illustrated in FIG. 8 , then searches through the binary instance of the document for the troubleshooting section.
  • the browser 80 displays the found section 242 in the display window 60 as shown in FIG. 9B .
  • the browser 80 updates the second row of selectors 58 to correspond to the sub-sections 248 in the found section 242 .
  • the user interface 50 of the browser 80 may be enhanced by adding objects to give the user more tools with which to view the documents.
  • the user interface 50 shown in FIG. 9A , includes a next section button 92 , a previous section button 94 , a go forward button 72 , a go backward button 74 and string search tools 78 , 86 , 88 , 89 . These objects may be programmed into the browser 80 along with the software components that provide the indicated functions.
  • next section button 92 When the next section button 92 is selected with the combined action of the screen pointer 62 and the selecting device 102 , a user views the next section in the document.
  • the next section after the Overview section 16 in FIG. 9A is the Sales section (See FIG. 2 ). Selecting the next section button 92 in FIG. 9A causes the browser 80 to display the Sales section.
  • the previous section button 94 operates in the same manner as the next section button 92 except that the previous section is shown.
  • the go forward button 72 and go backward button 74 may be used to scroll text in the display window 60 .
  • the user interface 50 as shown in FIG. 9A may also include string search tools 78 , 86 , 88 .
  • the string search entry box 78 may be used to input a text string that the user wishes to locate in the document.
  • the next found and previous found buttons 86 , 88 may be used to display the locations in the document in which the string was found.
  • the clear search button 89 clears the text in the search entry box 78 .
  • the feedback entry function gives the user the ability to provide feedback on a document for those who may browse the document at a later time.
  • a text box 260 opens up to allow the user to enter a note.
  • the text box 260 may be a compilation of messages to which users append notes, or the contents of the text box 260 may be saved into a separate repository of data periodically.
  • the compilation of messages may be saved to a SGML-based file for support as a document that may be viewed by implementation of the browser 80 .
  • the textbox 260 may be replaced by a view of the messages in the display window 60 .
  • FIGS. 9A & 9B is one example of the user interface in the present invention.
  • the appearance and the choice of graphic objects may be varied to suit the needs of the intended users.
  • buttons 56 , 58 are merely display regions of the user interface configured to perform a function when selected with the screen pointer 62 and the selecting device 102 .
  • the selectors are represented by button icons. As shown in FIG. 10 , these icons may be replaced with words or phrases 268 that are descriptive of the section that they are configured to display.
  • FIG. 11 Another variation, shown in FIG. 11 , uses a distributed user interface in which the buttons 288 are located in their own window that is detached from the display window 60 .
  • FIG. 11 illustrates the separate windows 50 , 288 as they might appear on a monitor screen 274 .
  • keys on the keyboard 110 may be configured as functional equivalents of the screen pointer 62 to select document section selectors 56 , 58 .
  • FIG. 12 illustrates a monitor screen 274 connected to a keyboard 110 via connection 275 .
  • the selectors 56 , 58 may be mapped to function keys 270 on the keyboard 110 .
  • the browser 80 may first, highlight a selector in response to certain keys such as a TAB key 266 , or an arrow key 264 , and then select the highlighted selector 280 in response to another key such as the ENTER key 272 .
  • the user interface 50 may also be implemented in an environment that lacks a GUI, such as a character-based system interface.
  • the selectors 56 , 58 are words or phrases that have features such as a character-based border identifying them as selectors. The user then selects a selector using the keys on the keyboard as described above.
  • the selectors 56 , 58 are not used at all and the entire screen is the display window.
  • Function keys 270 on the keyboard 110 are implemented in place of the selectors.
  • the function keys 270 may be mapped according to the labels indicated at 290 .

Abstract

A structured document browser includes a constant user interface for displaying and viewing sections of a document that is organized according to a pre-defined structure. The structured document browser displays documents that have been marked with embedded codes that specify the structure of the document. The tags are mapped to correspond to a set of icons. When the icon is selected while browsing a document, the browser will display the section of the structure corresponding to the icon selected, while preserving the constant user interface.

Description

  • A portion of the disclosure of this document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by any one of the patent disclosure as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights to copyright protection whatsoever.
  • FIELD OF THE INVENTION
  • This invention relates to computer applications for viewing documents, and in particular, to a computer program for viewing documents having a predefined structure.
  • BACKGROUND OF THE INVENTION
  • Current computing environments typically include a graphical user interface (GUI). IBM personal computers and IBM compatibles run either OS/2 or Windows. The Macintosh has always had GUI capabilities as part of its operating system. Even higher end computers, including those that run Unix or VAX/VMS operating systems, are available with components that provide a GUI environment.
  • GUI's are generated using a set of software tools that put graphical objects on the computer display. One of these graphical objects is a screen pointer that the user controls with a mouse or a trackball. The user moves the mouse to position the pointer on the screen over selected objects on the screen. The user can select an object by using a selecting device which is typically a mouse switch. By selecting an object, the user instructs the operating system or an application to execute the function associated with the object. The GUI objects can include the graphical representation of buttons, menus or any other graphic object.
  • GUI's are the foundation of hypertext and hypermedia applications. Such applications allow computer users to create interfaces in which graphical objects are configured to correspond, or to link to objects of information. For example, a user may create an interface having the graphical representation of a button to display a motion video by selecting the button with a screen pointer. Similarly, the button can be configured to make a sound, display an image or display a separate text file.
  • Today's increasing interest in the Internet is due in part to the improvements in hypermedia applications. The World Wide Web is growing dramatically due to the evolution of standard markup languages that allow users to mark documents with links to other documents, and of presenters or viewers that interpret the markup language in the documents allowing the users to view the links.
  • One of the first markup tools was the Standard Generalized Markup Language (SGML). SGML was developed by the International Standards Organization and has been adopted by the Department of Defense and other government agencies as a way of standardizing documentation. SGML is machine-based in a manner similar to a computer language. An SGML Document Type Definition (DTD) may be defined according to the specifications of SGML for a given document structure. The DTD defines elements to be embedded in a document. The documents are then viewed using a viewer or browser that interprets the elements in the document according to the data structure defined in the DTD.
  • The HyperText Markup Language (HTML) is an instance of a DTD defined by SGML. HTML elements or codes are embedded into documents for use with HTML browsers. Browsers display the documents according to stylesheets associated with the embedded codes. The stylesheets contain rules or instructions that dictate the appearance of a document as presented by a browser. Stylesheets may also contain references to other documents in different computers. These references may be used in conjunction with context-sensitive regions of the documents such that a user retrieves the document reference by selecting the region. In this manner, an author links one document to others in a meaningful way such that a viewer may provide a user with access to information in documents that are linked together in a web-like fashion.
  • One common characteristic of many browsers is that the links to information are presented solely within documents. The links may take the user to other documents or to locations within the same document, but typically, the elements that provide the link-control are within the documents.
  • Having the control to the information links within the documents themselves is adequate where the documents are short and where the purpose is to obtain information in brief, concise statements. But where a document is long, it becomes difficult to browse the document since the only potential access to other destinations are in whatever part of the document is currently being displayed.
  • Moreover, organizations often work with standardized documents. These documents typically have a carefully defined purpose and are usually characterized by a standard structure. These documents may be long and the main purpose for viewing the documents is often to access information found in a specific section of the well-known structure of the document.
  • SUMMARY OF THE INVENTION
  • In view of the above, a structured document browser is provided with a user interface that remains uniform and familiar as the user browses documents according to their structure instead of their contents. The browser uses codes embedded in the document to identify sections of the structure of the document. The user interface includes graphical user interface objects, such as buttons, that are configured to display a standard section of the document structure when selected by the user.
  • The structured document browser may also include menus that allow a user to select a document from among different documents, or a document structure type from among different structure types.
  • It is another object of the invention to provide a method for browsing a document by using a screen pointer to select a graphical user interface object and displaying a section of the document that corresponds to the graphical user interface object.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram of a preferred embodiment of the structured document browser showing how it communicates with other components of the computer.
  • FIG. 2 illustrates a sample structure for a document.
  • FIG. 3 illustrates a portion of a document having the structure shown in FIG. 2 after it has been marked with SGML tags.
  • FIG. 4 illustrates an SGML document type definition (DTD) created for use by a structured document browser for a document having the structure shown in FIG. 2.
  • FIG. 5 is a representation of an example of a user interface of the structured document browser for FIG. 1.
  • FIG. 6 is a flow chart showing the process of retrieving a structured document and illustrates playing the section of a document in response to the selection of a button.
  • FIG. 7 illustrates an example of a bks data structure.
  • FIG. 8 is a diagram that shows the interaction between a button, a map file and bit map file.
  • FIGS. 9A & 9B illustrate the operation of the browser of FIG. 1.
  • FIG. 10 illustrates one example of an alternative implementation of the user interface.
  • FIG. 11 illustrates a second alternative implementation of the user interface.
  • FIG. 12 illustrates a third alternative implementation of the user interface.
  • FIG. 13 illustrates a fourth alternative implementation of the user interface.
  • DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS
  • In the description that follows, reference is made to the drawings where like elements are identified by like numerals throughout.
  • A presently preferred embodiment of this invention includes an application program called browser.exe that has been developed using the ‘c’ programming language in the Windows environment. The browser.exe executable file is programmed to make function calls to three dynamic link libraries named sit.dll, cgrmzv.dll and ct13d.dll. These libraries are components of Dynatext Version 2.0, a user interface development system from Electronic Book Technologies, Inc. These Dynatext libraries provide functions that implement the SGML related functions and the graphic input/output functions. Further information regarding the Dynatext program may be obtained by contacting Electronic Book Technologies, Inc. at One Richmond Square, Providence, R.I. 02906.
  • The browser.exe program uses data structures in several support files that are in the same directory tree as browser.exe. These support files will be described in more detail in the description that follows.
  • A listing of the present version of browser.exe is attached as Appendix I of this specification. The listing is an octal representation of browser.exe. The presently preferred embodiment may be carried out by converting the octal to a binary executable file using methods that are well known in the art. After conversion, the browser.exe file may be executed from a directory that includes the dynamic link libraries and the support files described in this disclosure.
  • It is to be understood however, that an embodiment of the present invention may be developed for any computing environment using any suitable development system.
  • The browser application in a presently preferred embodiment is referred to in the following detailed description as the browser 80 as shown in FIG. 1. FIG. 1 is a block diagram describing at a high level the browser 80 in the computing environment. The components of the browser 80 in its operating environment include the browser 80 itself, an operating system 104 with GUI capabilities, storage media 108, a keyboard 110, a pointing device 100, a selecting device 102 and a monitor 112. The operating system 104 further includes an I/O system 114 and a GUI system 116.
  • The double headed arrows 118 denote the communication between the respective components. The communication at 118 may entail communication over a network where appropriate.
  • The hardware devices 108, 110, 100, 102, 112 may be implemented by choosing from among many alternatives for each device. A pointing device 100 may be implemented using a mouse, a trackball or any other device that controls the position of a screen pointer. A selecting device 102 is typically implemented with mouse buttons or buttons that operate in conjunction with a trackball. In general, any device that may be used to effect the selection of an object at the location of the screen pointer may be used as a selecting device 102. A selecting device 102′ may even include a key on the keyboard 110. The storage media 108 is understood to include random access memory (RAM), the temporary storage out of which programs are executed as well as the mass storage devices in which programs are stored. The hardware devices 108, 110, 100, 102, 112 are understood to include the software drivers necessary for their operation in the computing environment.
  • The browser 80 includes at least a controller 82 and a system interface 84. The system interface 84 is responsible for processing the communication between the browser 80 and the operating system 104, the I/O system 114 and the GUI system 116. The controller 82 receives and interprets requests from the system interface 84 to perform a browser function. For example, the system interface 84 receives signals from the I/O system 114 that the pointing device 100 and the selecting device 102 were used to press a button or icon, to request a display of a section of a document. The controller 82 receives the information from the system interface 84 to determine which document section to display.
  • In a presently preferred embodiment, the system interface 84 includes the functions provided by the Dynatext development system and any operating system or I/O system functions. The controller 82 in a preferred embodiment is the executable program browser.exe. It is to be understood that the diagram in FIG. 1 is by way of illustration and is not intended to limit the software structure chosen to carry out the invention.
  • The browser 80 operates with documents that have been prepared as described below. Because the browser 80 is designed to navigate documents according to their structure, the utility of the browser 80 is maximized when an organization establishes a standard structure for its key documents. A software engineering group, for example may find it desirable to maintain a uniform structure for the software requirement specifications that the group develops. A different structure is desirable for the group's design specifications, and yet a different structure works for the group's test documentation. The group's goal for such documentation is to maintain uniformity.
  • Referring to FIG. 2, a marketing group might maintain product descriptions for its company's product line in documents having the predefined document structure 10. This structure is predefined to have headings 12 that provide overview information, sales information, product availability information, ordering information, billing information, troubleshooting information and product support information. The structure also has sub-headings 14 within each heading where relevant. The overview section 16 has sub-headings 14 for sections devoted to a product description, aliases, product features and instructions on how to use the product.
  • A specific document of the predefined structure in FIG. 2 is marked with codes for viewing with the browser 80. In a preferred embodiment, codes are used to mark the document as shown in FIG. 3. The codes shown in FIG. 3 have angle brackets around them. In a preferred embodiment, the codes are SGML elements. These codes may be replaced by elements of other markup tools in alternative embodiments. In the marked document 20, the application identification code 22 indicates that the document has been marked for use by the browser 80. The overall document structure is identified with a product name code 24. Each standard structure component is then marked with an appropriate code or element.
  • The sections in a document are preferably marked according to a convention. First, the beginning of a section is marked by a code or element. For example, the <OVER> element 26 identifies the beginning of the section of the document that provides an overview of the product. The <OVER> element 26 is followed by the heading and text that constitute the Overview section of the document. A begin section name element 28 indicates that the information that follows the element 28 specifies the name that will appear in all documents of the same structure for that section. In the marked document 20 in FIG. 3, the name of the overview section is “Overview” 30. Immediately after the name, an end section name element 32 indicates the end of that section name such that the text between the begin section name element 28 and the end section name element 32 is the text 30 that will appear in the heading. Similarly, an end section element 34 indicates the end of the section. In this case, the element </OVER> 34 marks the end of the overview section. The convention of marking the beginning and the end of parts of the document is used to mark other sections (as shown at 36, 38, 39 and 42) that form the standard document structure.
  • Begin sub-section elements 38 and end sub-section elements 42 mark the sub-sections of the document, using the same convention, with the stipulation that the end elements 39 are in an order that keeps the sub-sections nested within the sections. Documents may have sub-sections within sub-sections.
  • In a preferred embodiment, the structure of documents is defined by a document type definition (DTD). The DTD 40 in FIG. 4 illustrates how a document structure is represented in SGML. Codes such as those referenced at 24, 25, 26 and 38, that are used to indicate a section or structure part of the document as shown in FIG. 3, are defined by setting an element name, as shown at 42 and 44 in FIG. 4; setting a heading name, as shown at 47 and 49; and listing sub-parts as shown at 46. For example, the code for the product name 24 in FIG. 3 is defined in the DTD 40 as the element name 42 for the high level document structure composed of the list of sections 46. The list of sections 46 comprises the codes defining the sections of the document. The codes used in FIG. 3 for the begin section codes 25 are defined in the DTD 40 of FIG. 4 as element names 44 for the respective section level data structures. The respective name codes, such as the begin section name element 27 in FIG. 3, is shown as part of a section, as shown at 45 in FIG. 4. The name element 45 is also defined at 51. If a section has sub-parts, or sub-sections, the codes for the sub-sections within the section are listed in the definition of the section code as shown at 48. Each sub-section code is then defined individually as shown at 43. More details on the syntax and constructs of SGML may be obtained by referring to the ISO Standard for SGML ISO 8879: 1986/A1: 1988(E).
  • In a preferred embodiment, a document having a basic word processing format may be converted to a marked document 20, also known as an SGML instance, using an SGML utility. For example, a utility called DYNATAG from Electronic Book Technologies, Inc., uses documents having the structure described in FIG. 2 to create a DTD 40, illustrated in FIG. 4, as well as an SGML instance 20, illustrated in FIG. 3. Other SGML utilities may be used to create DTD's and SGML instances. The discussion of the DTD 40 is presented to illustrate how alternative embodiments might implement a program that interprets SGML DTD's to operate with the browser.
  • An infinite number of DTD's may be used, including common DTD's such as the HTML DTD. In addition, other embodiments of this invention may not use SGML as a markup language. Any other suitable markup language, including a proprietary markup language, may be used as well, provided that the appropriate software components are available to translate the code. Other embodiments of this invention may be designed to support the use of more than one markup language.
  • Once a document has been marked and converted into a format that is appropriate for the browser 80, the browser 80 may be started on a computer. Referring back to FIG. 1, the user invokes the browser 80 by using the pointing device 100 and the selecting device 102 to select the browser 80 in a manner dictated by the GUI of the operating system 104. In the preferred embodiment, the operating system 104 is the Windows Operating System (Version 3.1 and later for purposes of this example), the pointing device 100 is a mouse, and the selecting device 102 includes a pair of mouse buttons (left and right buttons). The Windows user interface 106, as it appears on the monitor 112, includes a menu bar 68, icons 66 representing application programs ready for initialization and a screen pointer 62 controlled by the user with the mouse pointing device 100.
  • To initialize the browser 80 in the Windows environment, the mouse 100 may be used to place the screen pointer 62 over the browser icon 64 in the operating system interface 106 and the left mouse button may be double-clicked.
  • Once the browser 80 has been initialized, the graphical user interface changes from the Windows user interface 106 in FIG. 1 to that of the browser user interface as shown at 50 in FIG. 5.
  • Referring to FIG. 5, the user interface 50 of the browser 80 gives the user the capability of selecting a particular document and then selecting different sections of the document for display. The objects used to browse through the documents remain on the user interface 50 regardless of where in a document a user is browsing. The user interface remains familiar to the user and responsive to the document structure.
  • The user interface so of the browser 80 includes a document menu 52, a document type menu 54, a first row of selectors 56, a second row of selectors 58 and a display window 60.
  • The user selects a document for browsing by using the document menu 52. The document menu 52 is implemented with standard graphical user interface menu objects such that the user selects a document menu arrow 70 to display the full menu of the documents available. The user then selects the document desired from the menu using the selecting device 102 in combination with the screen pointer 62.
  • The user interface 50 of the browser 80 is configured in a manner that allows the document types, or standard structures of different types, to be listed in a document type menu 54. The document type is selected by the user in the same manner that the user selects a document. The name of the document type is the name or alias of directories designated by the browser to have documents of a consistent structure. When a different document type is selected, the names listed in the document menu are changed according to the names of the available documents having the new document type.
  • The selectors 56, 58 are examples of document navigation tools that may be used for browsing documents in a presently preferred embodiment. More specifically, selectors 56, 58 are display regions in the user interface that are configured to perform pre-defined operations when the user places the screen pointer 62 over one of the selectors 56, 58 and then selects it with the selecting device 102. In the presently preferred embodiment, the display regions are depicted as icons that make them look like buttons with graphic images on them. The image may be designed to convey a sense of the operation to be performed if the icon is selected.
  • The first row of selectors 56 is configured to correspond to the first level of sections in a document. For example, the first selector 68 in the first row 56 is configured to correspond to the Overview section 16 in the document shown in FIG. 2.
  • Each selector is configured so that when the user places the screen pointer 62 over the selector and then selects it with the selecting device 102, the system interface 84 (described above with reference to FIG. 1) receives data indicating which selector was selected. The system interface 84 may then determine the document section associated with the selector and send the request to display that section to the controller 82 (described above with reference to FIG. 1). Alternatively, the system interface 84 may send to the controller 82 the identification of the chosen selector and let the controller 82 determine what section to display. The controller 82 will cause the document to be searched for the document section that matches the selector chosen. When the chosen section is found, the browser 80 displays in the display window 60 the section of the document structure that corresponds to the selector.
  • Once the desired section is in the display window 60, the user may navigate within the section by selecting one of the second row of selectors 58. Each time a selector from the first row of selectors 56 is selected, the second row of selectors 58 is configured to correspond to the sub-sections 14 within the section 12 being displayed (as shown in FIG. 2). A document structure having sub-sections within its sub-sections may also be accommodated so that three rows of selectors might be present in the user interface. The number of sub-sections within sections of a document may be further accommodated with rows of selectors as desired, or as limited by system constraints, such as the size of the display window 60.
  • The user may also navigate within the section by controlling the display window scroll bar 96 with the screen pointer 62 and the selecting device 102.
  • To describe the manner in which the selectors 56, 58 in the browser user interface 50 are configured, the initialization of the browser will be described in conjunction with exemplary files or data structures that are utilized during browsing operations. It is to be understood that this is only one implementation of the preferred embodiment, and that the files may be replaced, or integrated, or revised to form different data structures without departing from the scope of the invention. Furthermore, the Dynatext development tools may be replaced by other functionally equivalent tools.
  • In the presently preferred embodiment, documents are converted into “books” which are actually directory trees that reside in a directory called the “\xyz\books” directory. The terms “book,” “collection” and “library” are defined and used according to the specifications of the Dynatext development system.
  • In order to create the Dynatext books, the documents that have been coded as illustrated in FIG. 3 are supplied as input to a utility called DYNATAG which is a component of the Dynatext system. DYNATAG creates a DTD (as shown in FIG. 4) and an SGML instance (as shown in FIG. 3) of the document. The SGML instance and the DTD are used as input files to MKBOOK, another Dynatext utility. The MKBOOK utility creates a binary instance of the document, a directory tree, or a “book,” and some of the support files used by the browser 80. For example, the document for Widget having the structure for products descriptions defined in FIG. 2 is processed with MKBOOK to create the book “\xyz\books\widget,” a sub-directory of “\xyz\books.”
  • The browser 80 uses a number of data files to define how a document is found and displayed in the browser. These files and their names in the preferred embodiment are 1) the browser executable (browser.exe); 2) an initialization file (browser.ini); 3) a set of dynamic link libraries (sit.dll, cgmzv.dll, & ct13d.dll); 4) a bks file which is an ASCII file that contains information about a book, a library or collection of documents, and names in the browser menus (named *.bks where the * represents the name of a document); 5) a bitmap containing up to 100 regions for icons (named *.bmp or default.bmp) and 6) an ASCII file that provides the linking of the document element names to the icons in the bmp file and for pop-up text in the executable (named *.map or default.map).
  • The execution of the browser 80 will be described with reference to FIG. 6 which is a flowchart describing the steps taken to browse a document. When the user starts the structured document browser in the manner described above in reference to FIG. 1, the operating system launches the browser.exe executable file as shown at block 120. This file is located in a directory called the “\xyz” directory. When browser.exe is launched it first looks for the three required dynamic link libraries (DLL's) in the same directory as shown at block 122. The DLL's, supplied by Electronic Book Technologies, contain functions related to the user interface, SGML processing and access to the books.
  • If the DLL's are available, the browser then checks for the browser.ini file as shown in 124. If the browser.ini file is present, the browser 80 reads its contents, as shown at block 126.
  • As the sample file in Table 1 shows, the browser.ini file contains objects, or data structures that include the [Files] object, the [DTEXT] object, and the [MAP] object. The [FILES] object defines an annotation file. The annotation file is a repository for feedback from users of the browser regarding the documents being reviewed. The [DTEXT] object contains file names that the executable will use to find the location of the data directory, security key, and public and private directories. The [MAP] object provides the file name of the initial map file that is to be loaded (typically, the name is “default.map”). The map file, as discussed in detail below, contains the associations between the document elements and the icons.
    TABLE 1
    Sample browser.ini File
    [Files]
    AnnotationFile=\xyz\annot.txt
    [DTEXT]
    DATA_DIR=\xyz\data
    DTEXT_AUTH=@\xyz\data\security
    PUBLIC_DIR=\xyz\tmp\public
    PRIVATE_DIR=\xyz\tmp\private
    [MAP]
    Icons=default.bmp
  • Referring back to FIG. 6, once the browser.ini file is processed at 126, the browser checks for a file called default.bks at block 128. The default.bks file is an ASCII file which provides the browser with the information required to display a standard initial document, such as a document that displays a message of the day.
  • If a default.bks file is not found, the browser initializes without a book as shown at 130. Otherwise, the contents of default.bks are loaded as shown at 132 and the user interface is presented on the display to the user as shown at 134.
  • The bks files will be described by reference to FIG. 7. The bks files are ASCII files that contain information about how the book should be loaded into the menus in the browser and which map file to use. The bks file always begins with the [Book] object 140 in FIG. 7. The next line identifies the “collection.” In a preferred embodiment, a collection, also called a library, refers to the directory containing the books to which the browser 80 has access. In FIG. 7, the collection is located in the “\xyz” directory.
  • The next line in a bks file as shown in FIG. 7 identifies the collection title 144 which defines a document type for the document type menu 54. The collection title 144 is an alias for the group of books that will be listed under a heading in the document type menu 54 called “Products.”
  • The name of the book 146 is on the next line of the bks file. The book name is actually the name of the directory tree that must be present under the collection path specified in line two 142 of the bks file. The book title at 148 specifies an alias for the book. The book title contains the name the user will see on the document menu 52 (at FIG. 5). The map file name 150 is optional. It designates the map file that associates the tag names with the icons in the .bmp file. If specified, the browser will use the file name 152 to access the map file. Otherwise, the browser will assume a file name based on a pre-defined naming convention.
  • Referring back to FIG. 6, a user requests a document 160 by using the document menu 52 or the document type menu 54 in the user interface 50 (shown in FIG. 5). When the menu is selected (before a document is selected), the bks file is read in and the menu lists document and document type names according to the contents of the bks file. When a user requests to receive a document as shown at 160, the browser retrieves the document itself as shown at 162 and the map file associated with that document as shown at 164.
  • The browser then verifies that the elements in the map file match the SGML DTD and the structure codes in the document as shown at 166. If there are no discrepancies, the browser 80 reads the bmp file as shown at 168 which is specified in the map file. Also, in block 168, the browser 80 locates fly-by text for description of icons. The bmp file allows the browser to display the icons as shown at 170 for the selectors 56, 58 (in FIG. 5). The browser also displays the text in the chosen document as shown at 170.
  • Once the selectors on the user interface match the structure requirements of the document, the user may select a section of the document to view by pressing a selector button that corresponds to that section as shown at 172. The correspondence between the selectors 56, 58 and the document structure is established in the map file and in the bmp file. This correspondence will be described with reference to FIG. 8.
  • FIG. 8 shows a portion of the map file 200 for the document having the structure in FIG. 2, a bmp file 210 and the location on the user interface in which the selectors are placed 220. The first object in the map file is the [MAP] object 180 which identifies the data structure. The next line in the map file is the icon line 182 which is a filename that is used by the browser 80 to obtain the bmp file for the structure corresponding to the map file.
  • The next line in the map file shown in FIG. 8 contains the [SECTIONS] object 184. The [SECTIONS] object 184 marks the beginning of a set of definitions of data structures 186 that help tie the selector icons to the sections in the document. The order of these data structures indicates the order in which the sections appear in the document.
  • The first item under [sections] is “RBW-DOC, PROD.NAME, OVER=1:Overview” 188. The RBW-DOC,PROD.NAME 190 label indicates that the section identified in this line is in the first or highest level section. The OVER label 192 in the line matches the <OVER> tag 26 used to identify the overview section in the marked structure document shown in FIG. 3. The expression OVER=1 192 specifies which icon in the bmp file corresponds to the section identified. The text following the colon at 194 is used in fly-by help or bubble help messages. For example, when the screen pointer 62 is positioned over an icon 222 as shown in FIG. 8, a Help message 196 is displayed to indicate the function of the button. The expression OVER=1 192 and the fly-by-help text 194 are read by the browser 80 during block 168 in FIG. 6.
  • An example of the bmp file is shown in FIG. 8 at 210. The icons are stored in the bmp file as a single rectangular bitmap. Each icon is 16 pixels wide by 15 pixels high. In the presently preferred embodiment, the icons make the selectors appear to be buttons. The icon index starts at 1 and proceeds from left to right. So the icon index might appear as follows:
    1 2 3 4 5 6 7 8 9 10
    11 12 13 14 15 16 17 18 19 20
    21 22 <etc>
  • An example of how the map file relates to the bmp file is given in FIG. 8. Assume the user moves the screen pointer 62 to the troubleshooting icon, which is the sixth selector or 222 in the top row of selectors 56 and then selects it. The sixth button 222 corresponds to the sixth icon 224 in the bmp file. The browser 80 refers to the map file at the line RBW-DOC, PROD.NAME,TROUBL=6:Troubleshooting 226 to determine which element name must be searched. The line at 226 defines the TROUBL element as the element that must be searched when the sixth button in the first row 222 is selected.
  • While every book could have a separate map file and bmp file, these files relate to all books in a library. In other words, all books in the product library should have the same document structure (i.e., document type definition). Thus, a prd.map provides the mappings for all books in the products (i.e., prd) library and, a prd.bmp provides the icons for all books in the products (i.e., prd) library. The icons should relate to the hierarchical structure of the document structure as specified in the document type definition.
  • FIGS. 9A & 9B demonstrate the operation of the browser 80 by illustrating the way in which the user interface 50 changes in response to the pressing of a button. FIG. 9A shows the user interface 50 in an initial state with the Overview section 16 of the widget products document from FIG. 2 in the display window 60. The selectors 58 of the second row are represented by icons that correspond to the sub-sections 246 of the description section.
  • The user of the browser 80 may wish to view information that is known to exist in the troubleshooting section 18 of the widget product description. As shown in FIG. 2, the troubleshooting section 18 is towards the end of the document. Standard documents may be as short as one printed page or long enough to fill several binders. The browser 80 simplifies the retrieval of information by allowing access to a pre-defined section of a document by pushing a button. The screen pointer 62 may be moved from an initial position 240 to the position over the icon for the troubleshooting button 222. The user then selects the troubleshooting button 222 by enabling the selecting device 102. The browser 80, using the process illustrated in FIG. 8, then searches through the binary instance of the document for the troubleshooting section. The browser 80 displays the found section 242 in the display window 60 as shown in FIG. 9B. In addition to displaying the found section 242, the browser 80 updates the second row of selectors 58 to correspond to the sub-sections 248 in the found section 242.
  • The user interface 50 of the browser 80 may be enhanced by adding objects to give the user more tools with which to view the documents. The user interface 50, shown in FIG. 9A, includes a next section button 92, a previous section button 94, a go forward button 72, a go backward button 74 and string search tools 78, 86, 88, 89. These objects may be programmed into the browser 80 along with the software components that provide the indicated functions.
  • When the next section button 92 is selected with the combined action of the screen pointer 62 and the selecting device 102, a user views the next section in the document. For example, the next section after the Overview section 16 in FIG. 9A is the Sales section (See FIG. 2). Selecting the next section button 92 in FIG. 9A causes the browser 80 to display the Sales section. The previous section button 94 operates in the same manner as the next section button 92 except that the previous section is shown.
  • The go forward button 72 and go backward button 74 may be used to scroll text in the display window 60.
  • The user interface 50 as shown in FIG. 9A may also include string search tools 78, 86, 88. The string search entry box 78 may be used to input a text string that the user wishes to locate in the document. The next found and previous found buttons 86, 88 may be used to display the locations in the document in which the string was found. The clear search button 89 clears the text in the search entry box 78.
  • The feedback entry function gives the user the ability to provide feedback on a document for those who may browse the document at a later time. As shown in FIG. 9B, by selecting a feedback file in a menu, or by selecting a tools button 90, a text box 260 opens up to allow the user to enter a note. The text box 260 may be a compilation of messages to which users append notes, or the contents of the text box 260 may be saved into a separate repository of data periodically. In a preferred embodiment, the compilation of messages may be saved to a SGML-based file for support as a document that may be viewed by implementation of the browser 80. In addition, the textbox 260 may be replaced by a view of the messages in the display window 60.
  • It is to be understood that the appearance of the user interface 50 shown in FIGS. 9A & 9B is one example of the user interface in the present invention. The appearance and the choice of graphic objects may be varied to suit the needs of the intended users.
  • Referring to FIG. 10, one example of how the user interface 50 may be altered replaces the buttons 56, 58 with other objects. The buttons are merely display regions of the user interface configured to perform a function when selected with the screen pointer 62 and the selecting device 102. In the presently preferred embodiment of FIG. 9A, the selectors are represented by button icons. As shown in FIG. 10, these icons may be replaced with words or phrases 268 that are descriptive of the section that they are configured to display.
  • Another variation, shown in FIG. 11, uses a distributed user interface in which the buttons 288 are located in their own window that is detached from the display window 60. FIG. 11 illustrates the separate windows 50, 288 as they might appear on a monitor screen 274.
  • In another variation shown in FIG. 12, keys on the keyboard 110 may be configured as functional equivalents of the screen pointer 62 to select document section selectors 56, 58. FIG. 12 illustrates a monitor screen 274 connected to a keyboard 110 via connection 275. In one approach to using the keyboard, the selectors 56, 58 may be mapped to function keys 270 on the keyboard 110. In another approach which may be combined with the first approach, the browser 80 may first, highlight a selector in response to certain keys such as a TAB key 266, or an arrow key 264, and then select the highlighted selector 280 in response to another key such as the ENTER key 272.
  • The user interface 50 may also be implemented in an environment that lacks a GUI, such as a character-based system interface. In an example of such an implementation shown in FIG. 13, the selectors 56, 58 are words or phrases that have features such as a character-based border identifying them as selectors. The user then selects a selector using the keys on the keyboard as described above.
  • In another example of a character-based user interface 50, the selectors 56, 58 are not used at all and the entire screen is the display window. Function keys 270 on the keyboard 110 are implemented in place of the selectors. The function keys 270 may be mapped according to the labels indicated at 290.
  • It is to be understood that this specification is provided by way of illustration and that it is only the claims and their equivalents that define the invention.

Claims (34)

1. A system for displaying a plurality of web information, the system comprising:
a processor; and
memory, in communication with the processor, that stores:
operational instructions that, when executed by the processor, cause the processor to send data to display a plurality of selectors in a selector area by sending data comprising markup language codes that are configured to cause a browser in communication with the processor to retrieve graphics from a location external to the data comprising the markup language and external to the browser, wherein the plurality of selectors are automatically configured to correspond to respective portions of a plurality of web information regardless of what portion of the plurality of web information is being displayed;
operational instructions that, when executed by the processor, cause the processor to receive a selection of one of the plurality of selectors; and
operational instructions that, when executed by the processor, cause the processor to send data to display, at a same time as the plurality of selectors but outside of the selector area a portion of the plurality of web information that corresponds to the one of the plurality of selectors.
2. The system of claim 1, wherein the system is part of a computing environment that includes communication over a network, and wherein the processor is in communication with the network.
3. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send, over a network, at least one of the data to display the portion of the plurality of web information and the data to display the plurality of selectors.
4. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display a search string entry box.
5. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display a fly-by help message indicating a function of a selector of the plurality of selectors after a screen pointer is positioned over the selector of the plurality of selectors.
6. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display at least one additional selector in response to receiving the selection of the one of the plurality of selectors.
7. The system of claim 6, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display a second at least one additional selector in response to receiving a selection of the at least one additional selector.
8. The system of claim 7, wherein the at least one additional selector is associated with a sub-section of the plurality of web information, and wherein the second at least one additional selector is associated with a sub-section of the sub-section of the plurality of web information.
9. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display a menu selector, wherein selection of the menu selector results in a display of a menu of selection choices.
10. The system of claim 9, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display the menu selector in a same row as the plurality of selectors.
11. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display a text box to allow a user to enter a note that provides feedback regarding the portion of the plurality of web information.
12. The system of claim 1, wherein the memory further stores:
operational instructions that, when executed by the processor, cause the processor to send data to display the plurality of selectors in a row above the display window.
13. A method for displaying a plurality of web information, the method comprising:
sending data to display a plurality of selectors in a selector area by sending data comprising markup language codes that are configured to cause a browser to retrieve graphics from a location external to the data comprising the markup language codes and external to the browser, the plurality of selectors automatically configured to correspond to respective portions of a plurality of web information regardless of what portion of the plurality of web information is being displayed;
receiving a selection of one of the plurality of selectors; and
sending data to display, at a same time as the plurality of selectors but outside of the selector area, a portion of the plurality of web information that corresponds to the one of the plurality of selectors.
14. The method of claim 13 further comprising:
sending, over a network, at least one of the data to display the portion of the plurality of web information and the data to display the plurality of selectors.
15. The method of claim 13 further comprising:
sending data to display a search string entry box.
16. The method of claim 13 further comprising:
sending data to display a fly-by help message indicating a function of a selector of the plurality of selectors after a screen pointer is positioned over the selector of the plurality of selectors.
17. The method of claim 13 further comprising:
sending data to display at least one additional selector in response to receiving the selection of the one of the plurality of selectors.
18. The method of claim 17 further comprising:
sending data to display a second at least one additional selector in response to receiving a selection of the at least one additional selector.
19. The method of claim 18, wherein the at least one additional selector is associated with a sub-section of the plurality of web information, and wherein the second at least one additional selector is associated with a sub-section of the sub-section of the plurality of web information.
20. The method of claim 13 further comprising:
sending data to display a menu selector, wherein selection of the menu selector results in a display of a menu of selection choices.
21. The method of claim 20 further comprising:
sending data to display the menu selector in a same row as the plurality of selectors.
22. The method of claim 13 further comprising:
sending data to display a text box to allow a user to enter a note that provides feedback regarding the portion of the plurality of web information.
23. The method of claim 13 further comprising:
sending data to display the plurality of selectors in a row above the display window.
24. A computer-readable storage medium comprising:
operational instructions that, when executed by a processor, cause a processor to send data to display a plurality of selectors in a selector area by sending data comprising HyperText Markup Language (HTML) codes, with angle brackets around them, that are configured to cause a browser in communication with the processor to retrieve graphics from a location external to the data comprising the HTML codes and external to the browser, the plurality of selectors automatically configured to correspond to respective portions of a plurality of web information regardless of what portion of the plurality of web information is being displayed;
operational instructions that, when executed by the processor, cause the processor to receive a selection of one of the plurality of selectors; and
operational instructions that, when executed by the processor, cause the processor to send data to display, at a same time as the plurality of selectors but outside of the selector area, a portion of the plurality of web information that corresponds to the one of the plurality of selectors.
25. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send, over a network, at least one of the data to display the portion of the plurality of web data and the data to display the plurality of selectors.
26. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display a search string entry box.
27. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display a fly-by help message indicating a function of a selector of the plurality of selectors after a screen pointer is positioned over the selector of the plurality of selectors.
28. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display at least one additional selector in response to receiving the selection of the one of the plurality of selectors.
29. The computer-readable storage medium of claim 28 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display a second at least one additional selector in response to receiving a selection of the at least one additional selector.
30. The computer-readable storage medium of claim 29, wherein the at least one additional selector is associated with a sub-section of the plurality of web information, and wherein the second at least one additional selector is associated with a sub-section of the sub-section of the plurality of web information.
31. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display a menu selector, wherein selection of the menu selector results in a display of a menu of selection choices.
32. The computer-readable storage medium of claim 31 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display the menu selector in a same row as the plurality of selectors.
33. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display a text box to allow a user to enter a note that provides feedback regarding the portion of the plurality of web information.
34. The computer-readable storage medium of claim 24 further comprising:
operational instructions that, when executed by the processor, cause the processor to send data to display the plurality of selectors in a row above the display window.
US11/710,230 1996-05-17 2007-02-23 Structured document browser Abandoned US20080109720A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/710,230 US20080109720A1 (en) 1996-05-17 2007-02-23 Structured document browser

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US08/649,271 US5933841A (en) 1996-05-17 1996-05-17 Structured document browser
US09/304,425 US6442574B1 (en) 1996-05-17 1999-04-29 Structured document browser
US10/214,442 US20030079181A1 (en) 1996-05-17 2002-08-07 Structured document browser
US10/773,370 US20070101248A2 (en) 1996-05-17 2004-02-06 Structured document browser
US11/710,230 US20080109720A1 (en) 1996-05-17 2007-02-23 Structured document browser

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/773,370 Continuation US20070101248A2 (en) 1996-05-17 2004-02-06 Structured document browser

Publications (1)

Publication Number Publication Date
US20080109720A1 true US20080109720A1 (en) 2008-05-08

Family

ID=24604113

Family Applications (29)

Application Number Title Priority Date Filing Date
US08/649,271 Expired - Lifetime US5933841A (en) 1996-05-17 1996-05-17 Structured document browser
US09/304,425 Expired - Lifetime US6442574B1 (en) 1996-05-17 1999-04-29 Structured document browser
US10/214,442 Abandoned US20030079181A1 (en) 1996-05-17 2002-08-07 Structured document browser
US10/773,370 Abandoned US20070101248A2 (en) 1996-05-17 2004-02-06 Structured document browser
US11/126,840 Abandoned US20050216863A1 (en) 1996-05-17 2005-05-11 Structured document browser
US11/126,718 Abandoned US20050210378A1 (en) 1996-05-17 2005-05-11 Structured decument browser
US11/126,692 Abandoned US20050210377A1 (en) 1996-05-17 2005-05-11 Structured document browser
US11/126,865 Abandoned US20070136674A2 (en) 1996-05-17 2005-05-11 Structured document browser
US11/710,230 Abandoned US20080109720A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,627 Abandoned US20080082917A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,231 Abandoned US20080046810A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,629 Abandoned US20080072161A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,679 Abandoned US20080126964A1 (en) 1996-05-17 2007-02-23 Structured Document Browser
US11/710,606 Abandoned US20080072137A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,589 Abandoned US20080072176A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,260 Abandoned US20080071643A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,254 Abandoned US20080065985A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,262 Abandoned US20080082942A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,268 Abandoned US20080082916A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,241 Abandoned US20080082906A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,261 Abandoned US20080065973A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,243 Abandoned US20080065511A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,256 Abandoned US20080086702A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,255 Abandoned US20080065512A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,236 Abandoned US20080072149A1 (en) 1996-05-17 2007-02-23 Structured Document Browser
US11/710,275 Abandoned US20080065986A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,678 Abandoned US20080071615A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,263 Abandoned US20080082915A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,605 Abandoned US20080071644A1 (en) 1996-05-17 2007-02-23 Structured document browser

Family Applications Before (8)

Application Number Title Priority Date Filing Date
US08/649,271 Expired - Lifetime US5933841A (en) 1996-05-17 1996-05-17 Structured document browser
US09/304,425 Expired - Lifetime US6442574B1 (en) 1996-05-17 1999-04-29 Structured document browser
US10/214,442 Abandoned US20030079181A1 (en) 1996-05-17 2002-08-07 Structured document browser
US10/773,370 Abandoned US20070101248A2 (en) 1996-05-17 2004-02-06 Structured document browser
US11/126,840 Abandoned US20050216863A1 (en) 1996-05-17 2005-05-11 Structured document browser
US11/126,718 Abandoned US20050210378A1 (en) 1996-05-17 2005-05-11 Structured decument browser
US11/126,692 Abandoned US20050210377A1 (en) 1996-05-17 2005-05-11 Structured document browser
US11/126,865 Abandoned US20070136674A2 (en) 1996-05-17 2005-05-11 Structured document browser

Family Applications After (20)

Application Number Title Priority Date Filing Date
US11/710,627 Abandoned US20080082917A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,231 Abandoned US20080046810A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,629 Abandoned US20080072161A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,679 Abandoned US20080126964A1 (en) 1996-05-17 2007-02-23 Structured Document Browser
US11/710,606 Abandoned US20080072137A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,589 Abandoned US20080072176A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,260 Abandoned US20080071643A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,254 Abandoned US20080065985A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,262 Abandoned US20080082942A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,268 Abandoned US20080082916A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,241 Abandoned US20080082906A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,261 Abandoned US20080065973A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,243 Abandoned US20080065511A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,256 Abandoned US20080086702A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,255 Abandoned US20080065512A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,236 Abandoned US20080072149A1 (en) 1996-05-17 2007-02-23 Structured Document Browser
US11/710,275 Abandoned US20080065986A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,678 Abandoned US20080071615A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,263 Abandoned US20080082915A1 (en) 1996-05-17 2007-02-23 Structured document browser
US11/710,605 Abandoned US20080071644A1 (en) 1996-05-17 2007-02-23 Structured document browser

Country Status (3)

Country Link
US (29) US5933841A (en)
AU (1) AU3132697A (en)
WO (1) WO1997043723A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050216849A1 (en) * 1996-05-17 2005-09-29 Schumacher Robert M Structured document browser

Families Citing this family (205)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6339767B1 (en) 1997-06-02 2002-01-15 Aurigin Systems, Inc. Using hyperbolic trees to visualize data generated by patent-centric and group-oriented data processing
US5983245A (en) * 1996-12-27 1999-11-09 Apple Computer, Inc. Method and apparatus for implementing universal resource locator menus
AUPO489297A0 (en) * 1997-01-31 1997-02-27 Aunty Abha's Electronic Publishing Pty Ltd A system for electronic publishing
US7293228B1 (en) * 1997-01-31 2007-11-06 Timebase Pty Limited Maltweb multi-axis viewing interface and higher level scoping
US6785865B1 (en) * 1997-03-06 2004-08-31 Microsoft Corporation Discoverability and navigation of hyperlinks via tabs
JP3368804B2 (en) * 1997-07-08 2003-01-20 トヨタ自動車株式会社 Hypertext transmission method and hypertext transmission server device
US6178433B1 (en) * 1997-07-15 2001-01-23 International Business Machines Corporation Method and system for generating materials for presentation on a non-frame capable web browser
US6910184B1 (en) * 1997-07-25 2005-06-21 Ricoh Company, Ltd. Document information management system
GB2328297B (en) * 1997-08-13 2002-04-24 Ibm Text in anchor tag of hyperlink adjustable according to context
US6374271B1 (en) * 1997-09-26 2002-04-16 Fuji Xerox Co., Ltd. Hypermedia document authoring using a goals outline and a presentation outline
US6073136A (en) * 1997-10-30 2000-06-06 International Business Machines Corporation Mobile computer with minimized function display and maximized content display
US6574644B2 (en) * 1997-11-26 2003-06-03 Siemens Corporate Research, Inc Automatic capturing of hyperlink specifications for multimedia documents
US7596755B2 (en) 1997-12-22 2009-09-29 Ricoh Company, Ltd. Multimedia visualization and integration environment
US7954056B2 (en) 1997-12-22 2011-05-31 Ricoh Company, Ltd. Television-based visualization and navigation interface
US7124093B1 (en) 1997-12-22 2006-10-17 Ricoh Company, Ltd. Method, system and computer code for content based web advertising
JP4183311B2 (en) * 1997-12-22 2008-11-19 株式会社リコー Document annotation method, annotation device, and recording medium
US7257589B1 (en) 1997-12-22 2007-08-14 Ricoh Company, Ltd. Techniques for targeting information to users
US7263659B2 (en) * 1998-09-09 2007-08-28 Ricoh Company, Ltd. Paper-based interface for multimedia information
US20080028292A1 (en) * 1997-12-22 2008-01-31 Ricoh Company, Ltd. Techniques to facilitate reading of a document
US6665836B1 (en) * 1998-06-17 2003-12-16 Siemens Corporate Research, Inc. Method for managing information on an information net
US6658626B1 (en) * 1998-07-31 2003-12-02 The Regents Of The University Of California User interface for displaying document comparison information
US6266682B1 (en) * 1998-08-31 2001-07-24 Xerox Corporation Tagging related files in a document management system
US6562076B2 (en) 1998-08-31 2003-05-13 Xerox Corporation Extending application behavior through active properties attached to a document in a document management system
US7263671B2 (en) 1998-09-09 2007-08-28 Ricoh Company, Ltd. Techniques for annotating multimedia information
US7215436B2 (en) * 1998-09-09 2007-05-08 Ricoh Company, Ltd. Device for generating a multimedia paper document
US6582475B2 (en) 1998-09-09 2003-06-24 Ricoh Company Limited Automatic adaptive document printing help system
US7266782B2 (en) 1998-09-09 2007-09-04 Ricoh Company, Ltd. Techniques for generating a coversheet for a paper-based interface for multimedia information
US7281203B2 (en) * 1998-09-29 2007-10-09 Netscape Communications Corporation Selecting a DTD for transforming malformed layout expressions into wellformed ones
US6145000A (en) * 1998-10-06 2000-11-07 Ameritech Corporation System and method for creating and navigating a linear hypermedia resource program
US6656608B1 (en) * 1998-12-25 2003-12-02 Konica Corporation Electroluminescent material, electroluminescent element and color conversion filter
US6694320B1 (en) * 1999-03-01 2004-02-17 Mitel, Inc. Branding dynamic link libraries
US7966328B2 (en) 1999-03-02 2011-06-21 Rose Blush Software Llc Patent-related tools and methodology for use in research and development projects
US7716060B2 (en) 1999-03-02 2010-05-11 Germeraad Paul B Patent-related tools and methodology for use in the merger and acquisition process
US6310633B1 (en) * 1999-03-23 2001-10-30 Ricoh Company Limited Method and system for organizing document information
US20070094268A1 (en) * 2005-10-21 2007-04-26 Tabe Joseph A Broadband centralized transportation communication vehicle for extracting transportation topics of information and monitoring terrorist data
US6493703B1 (en) 1999-05-11 2002-12-10 Prophet Financial Systems System and method for implementing intelligent online community message board
US6515681B1 (en) 1999-05-11 2003-02-04 Prophet Financial Systems, Inc. User interface for interacting with online message board
US7162471B1 (en) 1999-05-11 2007-01-09 Maquis Techtrix Llc Content query system and method
US6571234B1 (en) 1999-05-11 2003-05-27 Prophet Financial Systems, Inc. System and method for managing online message board
US6804675B1 (en) 1999-05-11 2004-10-12 Maquis Techtrix, Llc Online content provider system and method
US6401094B1 (en) * 1999-05-27 2002-06-04 Ma'at System and method for presenting information in accordance with user preference
US6647534B1 (en) 1999-06-30 2003-11-11 Ricoh Company Limited Method and system for organizing document information in a non-directed arrangement of documents
US9053500B2 (en) * 1999-06-30 2015-06-09 Blackboard Inc. Internet-based education support system and method with multi-language capability
US7228492B1 (en) * 1999-07-06 2007-06-05 Ricoh Company, Ltd. 2D graph displaying document locations of user-specified concept of interest
US6366906B1 (en) * 1999-07-15 2002-04-02 International Business Machines Corporation Method and apparatus for implementing a search selection tool on a browser
JP4827275B2 (en) * 1999-08-10 2011-11-30 シャープ株式会社 Electronic book display device and recording medium recording computer program
US6356933B2 (en) * 1999-09-07 2002-03-12 Citrix Systems, Inc. Methods and apparatus for efficiently transmitting interactive application data between a client and a server using markup language
US7142196B1 (en) * 1999-10-12 2006-11-28 Autodesk, Inc. Geographical data markup on a personal digital assistant (PDA)
JP3558065B2 (en) * 1999-12-21 2004-08-25 セイコーエプソン株式会社 Content providing device and content using device
US7142205B2 (en) 2000-03-29 2006-11-28 Autodesk, Inc. Single gesture map navigation graphical user interface for a personal digital assistant
AU2001271763A1 (en) * 2000-06-30 2002-01-14 Zinio Systems, Inc. System and method for encrypting, distributing and viewing electronic documents
US7051084B1 (en) 2000-11-02 2006-05-23 Citrix Systems, Inc. Methods and apparatus for regenerating and transmitting a partial page
US7346842B1 (en) * 2000-11-02 2008-03-18 Citrix Systems, Inc. Methods and apparatus for incorporating a partial page on a client
US20020073163A1 (en) * 2000-12-12 2002-06-13 Fuji Xerox Co., Ltd. Systems and methods for supporting document centered discussion across heterogeneous devices and displays
US20020105548A1 (en) * 2000-12-12 2002-08-08 Richard Hayton Methods and apparatus for creating a user interface using property paths
US20020169803A1 (en) * 2000-12-18 2002-11-14 Sudarshan Sampath System and user interface for generating structured documents
US6963930B2 (en) * 2001-02-15 2005-11-08 Centric Software, Inc. Automatic transfer and expansion of application-specific data for display at a website
US6760047B2 (en) * 2001-02-26 2004-07-06 Microsoft Corporation Method for flagging and relating information in a computer system
US20030018663A1 (en) * 2001-05-30 2003-01-23 Cornette Ranjita K. Method and system for creating a multimedia electronic book
US7346546B2 (en) * 2001-06-07 2008-03-18 Gateway Inc. Purchasing interface with a task display
US20030041305A1 (en) * 2001-07-18 2003-02-27 Christoph Schnelle Resilient data links
GB2378785A (en) * 2001-08-18 2003-02-19 Robert Benjamin Franks Online trademark application system
US7363310B2 (en) 2001-09-04 2008-04-22 Timebase Pty Limited Mapping of data from XML to SQL
US7054841B1 (en) 2001-09-27 2006-05-30 I2 Technologies Us, Inc. Document storage and classification
US7149744B1 (en) * 2001-09-27 2006-12-12 I2 Technologies Us, Inc. Third party document storage and reuse
US7225146B2 (en) * 2001-09-27 2007-05-29 I2 Technologies Us, Inc. Method, system and article of manufacturing for dynamic database redirection using semantic taxonomy information
US10282765B2 (en) * 2001-09-27 2019-05-07 Jda Software Group, Inc. Order acceleration through user document storage and reuse
US7412404B1 (en) 2001-09-27 2008-08-12 I2 Technologies Us, Inc. Generating, updating, and managing multi-taxonomy environments
WO2003034173A2 (en) 2001-10-17 2003-04-24 Jorge Diniz Queiroga Loureiro Data management
US8046708B1 (en) * 2003-08-07 2011-10-25 The Mathworks, Inc. Reversed links from graphical diagram representation
US7281206B2 (en) * 2001-11-16 2007-10-09 Timebase Pty Limited Maintenance of a markup language document in a database
US7861169B2 (en) 2001-11-19 2010-12-28 Ricoh Co. Ltd. Multimedia print driver dialog interfaces
US7747655B2 (en) 2001-11-19 2010-06-29 Ricoh Co. Ltd. Printable representations for time-based media
US7149957B2 (en) 2001-11-19 2006-12-12 Ricoh Company, Ltd. Techniques for retrieving multimedia information using a paper-based interface
US7743347B2 (en) 2001-11-19 2010-06-22 Ricoh Company, Ltd. Paper-based interface for specifying ranges
US8635531B2 (en) 2002-02-21 2014-01-21 Ricoh Company, Ltd. Techniques for displaying information stored in multiple multimedia documents
US7703044B2 (en) * 2001-11-19 2010-04-20 Ricoh Company, Ltd. Techniques for generating a static representation for time-based media information
US8539344B2 (en) * 2001-11-19 2013-09-17 Ricoh Company, Ltd. Paper-based interface for multimedia information stored by multiple multimedia documents
US7495795B2 (en) * 2002-02-21 2009-02-24 Ricoh Company, Ltd. Interface for printing multimedia information
US7788080B2 (en) * 2001-11-19 2010-08-31 Ricoh Company, Ltd. Paper interface for simulation environments
US6976073B2 (en) * 2001-11-29 2005-12-13 Hewlett-Packard Development Company, L.P. Transparent remote data storage device and method
JP3888621B2 (en) * 2002-02-21 2007-03-07 インターナショナル・ビジネス・マシーンズ・コーポレーション Document processing system, document processing method and program
US7434162B2 (en) * 2002-06-06 2008-10-07 Speechcyle, Inc. Visual knowledge publisher system
US8086093B2 (en) * 2002-12-05 2011-12-27 At&T Ip I, Lp DSL video service with memory manager
US20040111750A1 (en) * 2002-12-05 2004-06-10 Stuckman Bruce E. DSL video service with automatic program selector
US7870593B2 (en) * 2002-12-05 2011-01-11 Att Knowledge Ventures, L.P. DSL video service with storage
US20040111754A1 (en) * 2002-12-05 2004-06-10 Bushey Robert R. System and method for delivering media content
US20040111748A1 (en) * 2002-12-05 2004-06-10 Bushey Robert R. System and method for search, selection and delivery of media content
US7739583B2 (en) * 2003-03-31 2010-06-15 Ricoh Company, Ltd. Multimedia document sharing method and apparatus
US7509569B2 (en) 2003-03-31 2009-03-24 Ricoh Co., Ltd. Action stickers for nested collections
US20070050696A1 (en) * 2003-03-31 2007-03-01 Piersol Kurt W Physical key for accessing a securely stored digital document
US7552381B2 (en) * 2003-03-31 2009-06-23 Ricoh Co., Ltd. Check boxes for identifying and processing stored documents
US7536638B2 (en) * 2003-03-31 2009-05-19 Ricoh Co., Ltd. Action stickers for identifying and processing stored documents
US7757162B2 (en) * 2003-03-31 2010-07-13 Ricoh Co. Ltd. Document collection manipulation
US7703002B2 (en) 2003-03-31 2010-04-20 Ricoh Company, Ltd. Method and apparatus for composing multimedia documents
AR045423A1 (en) * 2003-05-13 2005-10-26 Cephalon Inc COMBINATIONS OF ANALYTICS AND ANTIDEPRESSANTS
US20050034075A1 (en) * 2003-06-05 2005-02-10 Ch2M Hill, Inc. GIS-based emergency management
US20050015312A1 (en) * 2003-06-24 2005-01-20 Hoffman Ramona K. Method of selecting and purchasing office furniture
US9715678B2 (en) 2003-06-26 2017-07-25 Microsoft Technology Licensing, Llc Side-by-side shared calendars
US7716593B2 (en) 2003-07-01 2010-05-11 Microsoft Corporation Conversation grouping of electronic mail records
US8799808B2 (en) 2003-07-01 2014-08-05 Microsoft Corporation Adaptive multi-line view user interface
US7707255B2 (en) 2003-07-01 2010-04-27 Microsoft Corporation Automatic grouping of electronic mail
US7275159B2 (en) 2003-08-11 2007-09-25 Ricoh Company, Ltd. Multimedia output device having embedded encryption functionality
US8745222B2 (en) * 2003-08-15 2014-06-03 Blackboard Inc. Content system and associated methods
US10437964B2 (en) 2003-10-24 2019-10-08 Microsoft Technology Licensing, Llc Programming interface for licensing
US7464330B2 (en) * 2003-12-09 2008-12-09 Microsoft Corporation Context-free document portions with alternate formats
US7562292B2 (en) * 2003-12-30 2009-07-14 Lockheed Martin Corporation Systems engineering document prototyping system, program product, and related methods
US20050166143A1 (en) * 2004-01-22 2005-07-28 David Howell System and method for collection and conversion of document sets and related metadata to a plurality of document/metadata subsets
US20050195159A1 (en) * 2004-02-23 2005-09-08 Hunleth Frank A. Keyboardless text entry
US7779355B1 (en) 2004-03-30 2010-08-17 Ricoh Company, Ltd. Techniques for using paper documents as media templates
US7549118B2 (en) * 2004-04-30 2009-06-16 Microsoft Corporation Methods and systems for defining documents with selectable and/or sequenceable parts
US7418652B2 (en) * 2004-04-30 2008-08-26 Microsoft Corporation Method and apparatus for interleaving parts of a document
US7512878B2 (en) * 2004-04-30 2009-03-31 Microsoft Corporation Modular document format
US7359902B2 (en) 2004-04-30 2008-04-15 Microsoft Corporation Method and apparatus for maintaining relationships between parts in a package
US7487448B2 (en) * 2004-04-30 2009-02-03 Microsoft Corporation Document mark up methods and systems
US7383500B2 (en) * 2004-04-30 2008-06-03 Microsoft Corporation Methods and systems for building packages that contain pre-paginated documents
US8661332B2 (en) * 2004-04-30 2014-02-25 Microsoft Corporation Method and apparatus for document processing
US8363232B2 (en) 2004-05-03 2013-01-29 Microsoft Corporation Strategies for simultaneous peripheral operations on-line using hierarchically structured job information
US7755786B2 (en) 2004-05-03 2010-07-13 Microsoft Corporation Systems and methods for support of various processing capabilities
US20050246384A1 (en) * 2004-05-03 2005-11-03 Microsoft Corporation Systems and methods for passing data between filters
US7634775B2 (en) * 2004-05-03 2009-12-15 Microsoft Corporation Sharing of downloaded resources
US7440132B2 (en) 2004-05-03 2008-10-21 Microsoft Corporation Systems and methods for handling a file with complex elements
US7580948B2 (en) * 2004-05-03 2009-08-25 Microsoft Corporation Spooling strategies using structured job information
US8243317B2 (en) * 2004-05-03 2012-08-14 Microsoft Corporation Hierarchical arrangement for spooling job data
US7519899B2 (en) * 2004-05-03 2009-04-14 Microsoft Corporation Planar mapping of graphical elements
WO2005119519A2 (en) * 2004-06-02 2005-12-15 Blackboard Inc. Content and portal systems and associated methods
US8117542B2 (en) 2004-08-16 2012-02-14 Microsoft Corporation User interface for displaying selectable software functionality controls that are contextually relevant to a selected object
US8146016B2 (en) 2004-08-16 2012-03-27 Microsoft Corporation User interface for displaying a gallery of formatting options applicable to a selected object
US7703036B2 (en) 2004-08-16 2010-04-20 Microsoft Corporation User interface for displaying selectable software functionality controls that are relevant to a selected object
US7895531B2 (en) 2004-08-16 2011-02-22 Microsoft Corporation Floating command object
US8255828B2 (en) 2004-08-16 2012-08-28 Microsoft Corporation Command user interface for displaying selectable software functionality controls
US9015621B2 (en) 2004-08-16 2015-04-21 Microsoft Technology Licensing, Llc Command user interface for displaying multiple sections of software functionality controls
US7747966B2 (en) 2004-09-30 2010-06-29 Microsoft Corporation User interface for providing task management and calendar information
US7617450B2 (en) * 2004-09-30 2009-11-10 Microsoft Corporation Method, system, and computer-readable medium for creating, inserting, and reusing document parts in an electronic document
US7584111B2 (en) * 2004-11-19 2009-09-01 Microsoft Corporation Time polynomial Arrow-Debreu market equilibrium
US7617451B2 (en) * 2004-12-20 2009-11-10 Microsoft Corporation Structuring data for word processing documents
US7617229B2 (en) * 2004-12-20 2009-11-10 Microsoft Corporation Management and use of data in a computer-generated document
US20060136816A1 (en) * 2004-12-20 2006-06-22 Microsoft Corporation File formats, methods, and computer program products for representing documents
US7752632B2 (en) * 2004-12-21 2010-07-06 Microsoft Corporation Method and system for exposing nested data in a computer-generated document in a transparent manner
US7770180B2 (en) * 2004-12-21 2010-08-03 Microsoft Corporation Exposing embedded data in a computer-generated document
US8131736B1 (en) 2005-03-01 2012-03-06 Google Inc. System and method for navigating documents
US8326659B2 (en) * 2005-04-12 2012-12-04 Blackboard Inc. Method and system for assessment within a multi-level organization
US20060277452A1 (en) * 2005-06-03 2006-12-07 Microsoft Corporation Structuring data for presentation documents
US20070022128A1 (en) * 2005-06-03 2007-01-25 Microsoft Corporation Structuring data for spreadsheet documents
US7886290B2 (en) 2005-06-16 2011-02-08 Microsoft Corporation Cross version and cross product user interface
US20070005449A1 (en) * 2005-06-30 2007-01-04 Microsoft Corporation Optimized retail application user interface and architecture
US8239882B2 (en) 2005-08-30 2012-08-07 Microsoft Corporation Markup based extensibility for user interfaces
US9542667B2 (en) 2005-09-09 2017-01-10 Microsoft Technology Licensing, Llc Navigating messages within a thread
US7739259B2 (en) 2005-09-12 2010-06-15 Microsoft Corporation Integrated search and find user interface
US8627222B2 (en) 2005-09-12 2014-01-07 Microsoft Corporation Expanded search and find user interface
US7810021B2 (en) * 2006-02-24 2010-10-05 Paxson Dana W Apparatus and method for creating literary macramés
US8010897B2 (en) * 2006-07-25 2011-08-30 Paxson Dana W Method and apparatus for presenting electronic literary macramés on handheld computer systems
US8091017B2 (en) 2006-07-25 2012-01-03 Paxson Dana W Method and apparatus for electronic literary macramé component referencing
US8689134B2 (en) 2006-02-24 2014-04-01 Dana W. Paxson Apparatus and method for display navigation
US8605090B2 (en) 2006-06-01 2013-12-10 Microsoft Corporation Modifying and formatting a chart using pictorially provided chart elements
US9727989B2 (en) 2006-06-01 2017-08-08 Microsoft Technology Licensing, Llc Modifying and formatting a chart using pictorially provided chart elements
US20080148164A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Toolbox minimizer/maximizer
US20080147634A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Toolbox order editing
US20080148174A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Slide and fade
US20080147606A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Category-based searching
US20080270932A1 (en) * 2006-12-15 2008-10-30 Iac Search & Media, Inc. Toolbox editing
US20080148188A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Persistent preview window
US20080147653A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Search suggestions
US20080148192A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Toolbox pagination
US20080147708A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Preview window with rss feed
US8601387B2 (en) * 2006-12-15 2013-12-03 Iac Search & Media, Inc. Persistent interface
US20080148178A1 (en) * 2006-12-15 2008-06-19 Iac Search & Media, Inc. Independent scrolling
US20110179344A1 (en) * 2007-02-26 2011-07-21 Paxson Dana W Knowledge transfer tool: an apparatus and method for knowledge transfer
US8224815B2 (en) * 2007-05-21 2012-07-17 Perion Network Ltd. Interactive message editing system and method
US8201103B2 (en) 2007-06-29 2012-06-12 Microsoft Corporation Accessing an out-space user interface for a document editor program
US8484578B2 (en) 2007-06-29 2013-07-09 Microsoft Corporation Communication between a document editor in-space user interface and a document editor out-space user interface
US8762880B2 (en) 2007-06-29 2014-06-24 Microsoft Corporation Exposing non-authoring features through document status information in an out-space user interface
US9588781B2 (en) 2008-03-31 2017-03-07 Microsoft Technology Licensing, Llc Associating command surfaces with multiple active components
US9665850B2 (en) 2008-06-20 2017-05-30 Microsoft Technology Licensing, Llc Synchronized conversation-centric message list and message reading pane
US8402096B2 (en) 2008-06-24 2013-03-19 Microsoft Corporation Automatic conversation techniques
US8799353B2 (en) 2009-03-30 2014-08-05 Josef Larsson Scope-based extensibility for control surfaces
US9046983B2 (en) 2009-05-12 2015-06-02 Microsoft Technology Licensing, Llc Hierarchically-organized control galleries
US8332754B2 (en) 2009-11-04 2012-12-11 International Business Machines Corporation Rendering sections of content in a document
US8693353B2 (en) 2009-12-28 2014-04-08 Schneider Electric USA, Inc. Intelligent ethernet gateway system and method for optimizing serial communication networks
US10263827B2 (en) * 2009-12-31 2019-04-16 Schneider Electric USA, Inc. Information bridge between manufacturer server and monitoring device on a customer network
US20110214088A1 (en) * 2010-02-26 2011-09-01 Research In Motion Limited Automatic scrolling of electronic messages
US9361130B2 (en) 2010-05-03 2016-06-07 Apple Inc. Systems, methods, and computer program products providing an integrated user interface for reading content
US20110271228A1 (en) * 2010-05-03 2011-11-03 Zumobi, Inc. Systems, Methods, and Computer Program Products Providing an Article Selection Structure
US8302014B2 (en) 2010-06-11 2012-10-30 Microsoft Corporation Merging modifications to user interface components while preserving user customizations
US20110313906A1 (en) * 2010-06-21 2011-12-22 The Bank Of New York Mellon Computer-integrated securities financing system and method
US8589349B2 (en) * 2010-06-30 2013-11-19 International Business Machines Corporation Tracking and viewing revision history on a section-by-section basis
WO2012058000A1 (en) * 2010-10-26 2012-05-03 Barnes & Noble, Inc. System and method for streamlined acquisition, download and opening of digital content
AU2012281160B2 (en) 2011-07-11 2017-09-21 Paper Software LLC System and method for processing document
CA2840233A1 (en) * 2011-07-11 2013-01-17 Paper Software LLC System and method for processing document
EP2732381A4 (en) 2011-07-11 2015-10-21 Paper Software LLC System and method for searching a document
CA2840229A1 (en) 2011-07-11 2013-01-17 Paper Software LLC System and method for processing document
EP2555144A3 (en) * 2011-08-05 2013-04-17 Document Modelling Pty Ltd Structured document development, management and generation
JP5748279B2 (en) * 2011-09-08 2015-07-15 株式会社ドワンゴ Viewing target output device and operation method of viewing target output device
USD723057S1 (en) * 2012-08-07 2015-02-24 Microsoft Corporation Display screen with animated graphical user interface
AU350315S (en) * 2013-01-05 2013-08-23 Samsung Electronics Co Ltd Display Screen For An Electronic Device
AU350231S (en) * 2013-01-05 2013-08-21 Samsung Electronics Co Ltd Display screen for an electronic device
US20140223354A1 (en) * 2013-02-04 2014-08-07 Samsung Electronics Co., Ltd. Method and system for creating floating keys in a portable device
US20150242377A1 (en) * 2014-02-24 2015-08-27 Autodesk, Inc. Logical structure-based document navigation
USD865809S1 (en) 2015-05-29 2019-11-05 Avision Inc. Display screen or portion thereof with graphical user interface
USD837827S1 (en) 2015-05-29 2019-01-08 Avision Inc. Display screen or portion thereof with graphical user interface
US10467318B2 (en) 2016-02-25 2019-11-05 Futurewei Technologies, Inc. Dynamic information retrieval and publishing
US10726198B2 (en) 2017-10-17 2020-07-28 Handycontract, LLC Method, device, and system, for identifying data elements in data structures
US11475209B2 (en) 2017-10-17 2022-10-18 Handycontract Llc Device, system, and method for extracting named entities from sectioned documents
US10650186B2 (en) 2018-06-08 2020-05-12 Handycontract, LLC Device, system and method for displaying sectioned documents
JP7218170B2 (en) * 2018-12-20 2023-02-06 大王製紙株式会社 Disposable wearing article

Citations (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US39109A (en) * 1863-07-07 Improvement in metallic cartridges
US79181A (en) * 1868-06-23 Frederick t
US204275A (en) * 1878-05-28 Improvement in fence-posts
US210377A (en) * 1878-11-26 Improvement in devices for gaging the cutting of horseshoe-blanks
US210378A (en) * 1878-11-26 Improvement in rotary water-meters
US216863A (en) * 1879-06-24 Improvement in night-chairs
US216849A (en) * 1879-06-24 Improvement in needle-bars for sewing-machines
US4616336A (en) * 1983-05-11 1986-10-07 International Business Machines Corp. Independent image and annotation overlay with highlighting of overlay conflicts
US4752908A (en) * 1981-12-29 1988-06-21 International Business Machines Corporation Visualizable and descriptive data handling system
US4781785A (en) * 1987-11-13 1988-11-01 Owens-Illinois Plastic Products Inc. Apparatus for applying flexible plastic labels to round containers
US4829453A (en) * 1987-03-05 1989-05-09 Sharp Kabushiki Kaisha Apparatus for cataloging and retrieving image data
US5021989A (en) * 1986-04-28 1991-06-04 Hitachi, Ltd. Document browsing apparatus with concurrent processing and retrievel
US5129082A (en) * 1990-03-27 1992-07-07 Sun Microsystems, Inc. Method and apparatus for searching database component files to retrieve information from modified files
US5140521A (en) * 1989-04-26 1992-08-18 International Business Machines Corporation Method for deleting a marked portion of a structured document
US5142678A (en) * 1988-12-21 1992-08-25 International Business Machines Corporation Method for a requesting user to use a marker to associate a document with an end user action
US5146552A (en) * 1990-02-28 1992-09-08 International Business Machines Corporation Method for associating annotation with electronically published material
US5204947A (en) * 1990-10-31 1993-04-20 International Business Machines Corporation Application independent (open) hypermedia enablement services
US5253362A (en) * 1990-01-29 1993-10-12 Emtek Health Care Systems, Inc. Method for storing, retrieving, and indicating a plurality of annotations in a data cell
US5278980A (en) * 1991-08-16 1994-01-11 Xerox Corporation Iterative technique for phrase query formation and an information retrieval system employing same
US5297249A (en) * 1990-10-31 1994-03-22 International Business Machines Corporation Hypermedia link marker abstract and search services
US5329111A (en) * 1991-06-27 1994-07-12 Omron Corporation Image reader with adjustable contrast range
US5331547A (en) * 1993-01-29 1994-07-19 Clinical Multiphase Research, Inc. Process and computer system for control of interface software and data files
US5339091A (en) * 1986-07-07 1994-08-16 Semiconductor Energy Laboratory Co., Ltd. Paperless portable book
US5339433A (en) * 1992-11-19 1994-08-16 Borland International, Inc. Symbol browsing in an object-oriented development system
US5392387A (en) * 1992-12-17 1995-02-21 International Business Machines Corporation Method and system for enhanced data access efficiency in an electronic book
US5404506A (en) * 1985-03-27 1995-04-04 Hitachi, Ltd. Knowledge based information retrieval system
US5428776A (en) * 1991-03-12 1995-06-27 Wang Laboratories, Inc. System for composing a graphical interface to a relational database which displays a network of query and source icons
US5500929A (en) * 1993-08-30 1996-03-19 Taligent, Inc. System for browsing a network resource book with tabs attached to pages
US5517605A (en) * 1993-08-11 1996-05-14 Ast Research Inc. Method and apparatus for managing browsing, and selecting graphic images
US5530852A (en) * 1994-12-20 1996-06-25 Sun Microsystems, Inc. Method for extracting profiles and topics from a first file written in a first markup language and generating files in different markup languages containing the profiles and topics for use in accessing data described by the profiles and topics
US5546528A (en) * 1994-06-23 1996-08-13 Adobe Systems Incorporated Method of displaying multiple sets of information in the same area of a computer screen
US5551040A (en) * 1993-06-02 1996-08-27 Lucent Technologies Inc. Methods and apparatus for specifying the contexts of names in callback-style programming
US5557722A (en) * 1991-07-19 1996-09-17 Electronic Book Technologies, Inc. Data processing system and method for representing, generating a representation of and random access rendering of electronic documents
US5572643A (en) * 1995-10-19 1996-11-05 Judson; David H. Web browser with dynamic display of information objects during linking
US5623679A (en) * 1993-11-19 1997-04-22 Waverley Holdings, Inc. System and method for creating and manipulating notes each containing multiple sub-notes, and linking the sub-notes to portions of data objects
US5625781A (en) * 1995-10-31 1997-04-29 International Business Machines Corporation Itinerary list for interfaces
US5629846A (en) * 1994-09-28 1997-05-13 General Electric Company Method and system for document translation and extraction
US5634064A (en) * 1994-09-12 1997-05-27 Adobe Systems Incorporated Method and apparatus for viewing electronic documents
US5708826A (en) * 1995-05-16 1998-01-13 Fujitsu Limited Apparatus and method for converting presentation data
US5715314A (en) * 1994-10-24 1998-02-03 Open Market, Inc. Network sales system
US5717877A (en) * 1992-12-23 1998-02-10 Object Licensing Licensing Corporation Object-oriented data access framework system
US5768578A (en) * 1994-02-28 1998-06-16 Lucent Technologies Inc. User interface for information retrieval system
US5774109A (en) * 1995-12-29 1998-06-30 Franklin Electronic Publishers, Incorporated Electronic scrolling book with temporary interruptions
US5801702A (en) * 1995-03-09 1998-09-01 Terrabyte Technology System and method for adding network links in a displayed hierarchy
US5838906A (en) * 1994-10-17 1998-11-17 The Regents Of The University Of California Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document
US5867729A (en) * 1995-08-23 1999-02-02 Toshiba America Information Systems, Inc. System for reconfiguring a keyboard configuration in response to an event status information related to a computer's location determined by using triangulation technique
US5867161A (en) * 1995-08-08 1999-02-02 Walsh; Aaron E. Uniform mnemonic associations of computer resources to graphical images
US5877765A (en) * 1995-09-11 1999-03-02 Microsoft Corporation Method and system for displaying internet shortcut icons on the desktop
US5933841A (en) * 1996-05-17 1999-08-03 Ameritech Corporation Structured document browser
US5937417A (en) * 1996-05-07 1999-08-10 Sun Microsystems, Inc. Tooltips on webpages
US20010044751A1 (en) * 2000-04-03 2001-11-22 Pugliese Anthony V. System and method for displaying and selling goods and services
US20020057299A1 (en) * 1999-07-15 2002-05-16 Dobronsky Oren System and method for the dynamic improvement of internet browser navigability
US20020103789A1 (en) * 2001-01-26 2002-08-01 Turnbull Donald R. Interface and system for providing persistent contextual relevance for commerce activities in a networked environment

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US562679A (en) * 1896-06-23 Method of marking level-glasses or analogous articles
JP3175180B2 (en) * 1990-03-09 2001-06-11 キヤノン株式会社 Exposure method and exposure apparatus
US5248776A (en) * 1990-12-05 1993-09-28 University Of Georgia Research Foundation, Inc. Process for enantiomerically pure β-L-1,3-oxathiolane nucleosides
US5644737A (en) * 1995-06-06 1997-07-01 Microsoft Corporation Method and system for stacking toolbars in a computer display
US5781789A (en) * 1995-08-31 1998-07-14 Advanced Micro Devices, Inc. Superscaler microprocessor employing a parallel mask decoder
US5781785A (en) * 1995-09-26 1998-07-14 Adobe Systems Inc Method and apparatus for providing an optimized document file of multiple pages
WO2000058577A1 (en) * 1999-03-30 2000-10-05 Aab Building Systems, Inc. Bridging member for concrete form walls
EP1337065A1 (en) * 2002-02-13 2003-08-20 Telefonaktiebolaget L M Ericsson (Publ) Semi-reliable ARQ method and device thereof
US20050109720A1 (en) * 2002-12-18 2005-05-26 Rubbermaid, Inc. Method of merchandising an adjustable organizer system
MXPA03003959A (en) * 2003-03-18 2004-09-23 Invest Aplic S A De C V Use of egg yolk immunoglobulins for the treatment of infections caused by parasites in both humans and animals.
DE102004050755A1 (en) * 2004-09-09 2006-03-16 Robert Bosch Gmbh Method for pre-filling a low-pressure accumulator of a motor vehicle brake system
US20080065873A1 (en) * 2006-09-11 2008-03-13 Ronald Hall Dynamic livelock resolution with variable delay memory access queue
JP2008090434A (en) * 2006-09-29 2008-04-17 Toshiba Corp Information processor and e-mail reception method

Patent Citations (75)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US39109A (en) * 1863-07-07 Improvement in metallic cartridges
US79181A (en) * 1868-06-23 Frederick t
US204275A (en) * 1878-05-28 Improvement in fence-posts
US210377A (en) * 1878-11-26 Improvement in devices for gaging the cutting of horseshoe-blanks
US210378A (en) * 1878-11-26 Improvement in rotary water-meters
US216863A (en) * 1879-06-24 Improvement in night-chairs
US216849A (en) * 1879-06-24 Improvement in needle-bars for sewing-machines
US4752908A (en) * 1981-12-29 1988-06-21 International Business Machines Corporation Visualizable and descriptive data handling system
US4616336A (en) * 1983-05-11 1986-10-07 International Business Machines Corp. Independent image and annotation overlay with highlighting of overlay conflicts
US5404506A (en) * 1985-03-27 1995-04-04 Hitachi, Ltd. Knowledge based information retrieval system
US5021989A (en) * 1986-04-28 1991-06-04 Hitachi, Ltd. Document browsing apparatus with concurrent processing and retrievel
US5339091A (en) * 1986-07-07 1994-08-16 Semiconductor Energy Laboratory Co., Ltd. Paperless portable book
US4829453A (en) * 1987-03-05 1989-05-09 Sharp Kabushiki Kaisha Apparatus for cataloging and retrieving image data
US4781785A (en) * 1987-11-13 1988-11-01 Owens-Illinois Plastic Products Inc. Apparatus for applying flexible plastic labels to round containers
US5142678A (en) * 1988-12-21 1992-08-25 International Business Machines Corporation Method for a requesting user to use a marker to associate a document with an end user action
US5140521A (en) * 1989-04-26 1992-08-18 International Business Machines Corporation Method for deleting a marked portion of a structured document
US5253362A (en) * 1990-01-29 1993-10-12 Emtek Health Care Systems, Inc. Method for storing, retrieving, and indicating a plurality of annotations in a data cell
US5146552A (en) * 1990-02-28 1992-09-08 International Business Machines Corporation Method for associating annotation with electronically published material
US5129082A (en) * 1990-03-27 1992-07-07 Sun Microsystems, Inc. Method and apparatus for searching database component files to retrieve information from modified files
US5204947A (en) * 1990-10-31 1993-04-20 International Business Machines Corporation Application independent (open) hypermedia enablement services
US5297249A (en) * 1990-10-31 1994-03-22 International Business Machines Corporation Hypermedia link marker abstract and search services
US5428776A (en) * 1991-03-12 1995-06-27 Wang Laboratories, Inc. System for composing a graphical interface to a relational database which displays a network of query and source icons
US5329111A (en) * 1991-06-27 1994-07-12 Omron Corporation Image reader with adjustable contrast range
US5557722A (en) * 1991-07-19 1996-09-17 Electronic Book Technologies, Inc. Data processing system and method for representing, generating a representation of and random access rendering of electronic documents
US5278980A (en) * 1991-08-16 1994-01-11 Xerox Corporation Iterative technique for phrase query formation and an information retrieval system employing same
US5339433A (en) * 1992-11-19 1994-08-16 Borland International, Inc. Symbol browsing in an object-oriented development system
US5432903A (en) * 1992-11-19 1995-07-11 Borland International, Inc. Object browsing and a filter interface using a displayed dip switch in an object-oriented development sytem
US5392387A (en) * 1992-12-17 1995-02-21 International Business Machines Corporation Method and system for enhanced data access efficiency in an electronic book
US5717877A (en) * 1992-12-23 1998-02-10 Object Licensing Licensing Corporation Object-oriented data access framework system
US5331547A (en) * 1993-01-29 1994-07-19 Clinical Multiphase Research, Inc. Process and computer system for control of interface software and data files
US5551040A (en) * 1993-06-02 1996-08-27 Lucent Technologies Inc. Methods and apparatus for specifying the contexts of names in callback-style programming
US5517605A (en) * 1993-08-11 1996-05-14 Ast Research Inc. Method and apparatus for managing browsing, and selecting graphic images
US5500929A (en) * 1993-08-30 1996-03-19 Taligent, Inc. System for browsing a network resource book with tabs attached to pages
US5623679A (en) * 1993-11-19 1997-04-22 Waverley Holdings, Inc. System and method for creating and manipulating notes each containing multiple sub-notes, and linking the sub-notes to portions of data objects
US5768578A (en) * 1994-02-28 1998-06-16 Lucent Technologies Inc. User interface for information retrieval system
US5546528A (en) * 1994-06-23 1996-08-13 Adobe Systems Incorporated Method of displaying multiple sets of information in the same area of a computer screen
US5634064A (en) * 1994-09-12 1997-05-27 Adobe Systems Incorporated Method and apparatus for viewing electronic documents
US5629846A (en) * 1994-09-28 1997-05-13 General Electric Company Method and system for document translation and extraction
US5838906A (en) * 1994-10-17 1998-11-17 The Regents Of The University Of California Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document
US5715314A (en) * 1994-10-24 1998-02-03 Open Market, Inc. Network sales system
US5530852A (en) * 1994-12-20 1996-06-25 Sun Microsystems, Inc. Method for extracting profiles and topics from a first file written in a first markup language and generating files in different markup languages containing the profiles and topics for use in accessing data described by the profiles and topics
US5801702A (en) * 1995-03-09 1998-09-01 Terrabyte Technology System and method for adding network links in a displayed hierarchy
US5708826A (en) * 1995-05-16 1998-01-13 Fujitsu Limited Apparatus and method for converting presentation data
US5867161A (en) * 1995-08-08 1999-02-02 Walsh; Aaron E. Uniform mnemonic associations of computer resources to graphical images
US5867729A (en) * 1995-08-23 1999-02-02 Toshiba America Information Systems, Inc. System for reconfiguring a keyboard configuration in response to an event status information related to a computer's location determined by using triangulation technique
US5877765A (en) * 1995-09-11 1999-03-02 Microsoft Corporation Method and system for displaying internet shortcut icons on the desktop
US5572643A (en) * 1995-10-19 1996-11-05 Judson; David H. Web browser with dynamic display of information objects during linking
US5625781A (en) * 1995-10-31 1997-04-29 International Business Machines Corporation Itinerary list for interfaces
US5774109A (en) * 1995-12-29 1998-06-30 Franklin Electronic Publishers, Incorporated Electronic scrolling book with temporary interruptions
US5937417A (en) * 1996-05-07 1999-08-10 Sun Microsystems, Inc. Tooltips on webpages
US20080065985A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080071643A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080126964A1 (en) * 1996-05-17 2008-05-29 Schumacher Robert M Structured Document Browser
US20080086702A1 (en) * 1996-05-17 2008-04-10 Schumacher Robert M Structured document browser
US6442574B1 (en) * 1996-05-17 2002-08-27 Ameritech Corporation Structured document browser
US20080046810A1 (en) * 1996-05-17 2008-02-21 Schumacher Robert M Structured document browser
US5933841A (en) * 1996-05-17 1999-08-03 Ameritech Corporation Structured document browser
US20080065511A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065973A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065986A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065512A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080071644A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080072149A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured Document Browser
US20080082915A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080072161A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080072137A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080071615A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080072176A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080082916A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080082942A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080082917A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080082906A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20020057299A1 (en) * 1999-07-15 2002-05-16 Dobronsky Oren System and method for the dynamic improvement of internet browser navigability
US20010044751A1 (en) * 2000-04-03 2001-11-22 Pugliese Anthony V. System and method for displaying and selling goods and services
US20020103789A1 (en) * 2001-01-26 2002-08-01 Turnbull Donald R. Interface and system for providing persistent contextual relevance for commerce activities in a networked environment

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050216849A1 (en) * 1996-05-17 2005-09-29 Schumacher Robert M Structured document browser
US20070136674A2 (en) * 1996-05-17 2007-06-14 Sbc Properties, L.P. Structured document browser
US20080046810A1 (en) * 1996-05-17 2008-02-21 Schumacher Robert M Structured document browser
US20080065986A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065511A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065985A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065973A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080065512A1 (en) * 1996-05-17 2008-03-13 Schumacher Robert M Structured document browser
US20080072161A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080072137A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080072176A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080071644A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080071615A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080072149A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured Document Browser
US20080071643A1 (en) * 1996-05-17 2008-03-20 Schumacher Robert M Structured document browser
US20080082916A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080082942A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080082906A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080082915A1 (en) * 1996-05-17 2008-04-03 Schumacher Robert M Structured document browser
US20080086702A1 (en) * 1996-05-17 2008-04-10 Schumacher Robert M Structured document browser
US20080126964A1 (en) * 1996-05-17 2008-05-29 Schumacher Robert M Structured Document Browser

Also Published As

Publication number Publication date
US20050216849A1 (en) 2005-09-29
US20070136674A2 (en) 2007-06-14
US20080065511A1 (en) 2008-03-13
US20080046810A1 (en) 2008-02-21
US6442574B1 (en) 2002-08-27
US20050210377A1 (en) 2005-09-22
US20080072161A1 (en) 2008-03-20
US20050039109A1 (en) 2005-02-17
US20080082916A1 (en) 2008-04-03
US20080082915A1 (en) 2008-04-03
US20080065985A1 (en) 2008-03-13
US20080082906A1 (en) 2008-04-03
US20070101248A2 (en) 2007-05-03
US20080071644A1 (en) 2008-03-20
US20080082942A1 (en) 2008-04-03
US20050210378A1 (en) 2005-09-22
US20080065973A1 (en) 2008-03-13
US20080082917A1 (en) 2008-04-03
WO1997043723A1 (en) 1997-11-20
US20080072149A1 (en) 2008-03-20
AU3132697A (en) 1997-12-05
US20080065512A1 (en) 2008-03-13
US20050204275A2 (en) 2005-09-15
US20080071643A1 (en) 2008-03-20
US20080072137A1 (en) 2008-03-20
US5933841A (en) 1999-08-03
US20050216863A1 (en) 2005-09-29
US20080071615A1 (en) 2008-03-20
US20080086702A1 (en) 2008-04-10
US20030079181A1 (en) 2003-04-24
US20080126964A1 (en) 2008-05-29
US20080072176A1 (en) 2008-03-20
US20080065986A1 (en) 2008-03-13

Similar Documents

Publication Publication Date Title
US6442574B1 (en) Structured document browser
WO1997043723A9 (en) Structured document browser
US6429880B2 (en) Method and apparatus for binding user interface objects to application objects
US20010047373A1 (en) Publication file conversion and display
US20040030719A1 (en) Web page based dynamic book for document presentation and operation
US20090083661A1 (en) System and method for selectively displaying web page elements
US5982365A (en) System and methods for interactively generating and testing help systems
EP0926610A1 (en) Publication file conversion and display
GB2350990A (en) Initializing graphic user interface controls with extensible markup language-formatted data

Legal Events

Date Code Title Description
AS Assignment

Owner name: AT&T INTELLECTUAL PROPERTY 1, L.P., NEVADA

Free format text: CHANGE OF NAME;ASSIGNOR:SBC PROPERTIES, L.P.;REEL/FRAME:022457/0815

Effective date: 20030610

Owner name: AT&T INTELLECTUAL PROPERTY 1, L.P.,NEVADA

Free format text: CHANGE OF NAME;ASSIGNOR:SBC PROPERTIES, L.P.;REEL/FRAME:022457/0815

Effective date: 20030610

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: RPX CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY I, L.P.;REEL/FRAME:034091/0715

Effective date: 20141024