US6006236A - Virtual navigator that produces virtual links at run time for identifying links in an electronic file - Google Patents
Virtual navigator that produces virtual links at run time for identifying links in an electronic file Download PDFInfo
- Publication number
- US6006236A US6006236A US08/995,313 US99531397A US6006236A US 6006236 A US6006236 A US 6006236A US 99531397 A US99531397 A US 99531397A US 6006236 A US6006236 A US 6006236A
- Authority
- US
- United States
- Prior art keywords
- component
- components
- data structure
- links
- virtual
- 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.)
- Expired - Lifetime
Links
- 238000000034 method Methods 0.000 claims abstract description 19
- 238000004590 computer program Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 4
- 230000008520 organization Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
- G06F16/94—Hypermedia
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
Definitions
- This invention identifies components in an electronic file.
- An electronic document typically has information content, such as text, graphics, and tables, and formatting content that directs how to display the information content.
- Document publishing systems which include word processing systems and desktop publishing systems, may store electronic documents as hierarchical data structures. Such structures represent the information content and formatting content as nodes connected to one another in an ordered arrangement.
- a system traverses a data structure to gather data about the structure and to perform operations using that data. To traverse a hierarchical structure, the system follows a set of links from one node to another.
- a node attached to and above another node in the hierarchical structure is referred to as the parent of the latter node.
- a node attached to and below another node in the hierarchical structure is referred to as the child of the latter node.
- Nodes having the same parent are referred to as siblings.
- systems may identify the relationship between nodes in terms of next and previous links. Next and previous links ignore the familial relationships and deal with incremental positions of nodes within a document.
- the base links connect every node in the structure and define the structure's hierarchy.
- a system uses the base links to traverse the structure and discover the structure's organization.
- the structure's organization determines the order of processing for certain types of operations. For example, a spell checker may use the base links to examine each word in an electronic document from the beginning to the end of the document.
- the structure's organization also determines which nodes share behavior characteristics with other nodes. For example, a node may define paragraph characteristics that are inherited and refined by descendent nodes.
- a system can have sets of direct links to connect nodes in the same or in different branches of a hierarchical data structure.
- Direct links locate nodes that may have an effect upon each other under a certain set of circumstances. For example, if an author inserted a numbered section heading into a document, the system could use one set of direct links between numbered section heading nodes to find and renumber all subsequent section headings. Direct links are also useful in other situations, for example to identify components of a detailed outline, identify components of a brief outline, locate all index markers, and locate all bibliographic references.
- the invention is directed to a computer-implemented method for identifying links in an electronic file that is expressed as a data structure having components and base links.
- the base links define a structural relationship between the components.
- the method of the invention traverses the data structure using the base links and produces a virtual link between components in the data structure by recognizing a characteristic shared by the components.
- the virtual link is identified when needed at run-time.
- a function such as a renumbering function or a function that generates text, may be performed using each component that is virtually linked to another component.
- a plurality of traversal routines can sequentially execute to identify a virtual link between components.
- the data structure can be hierarchical and the traversal path used by the traversal routines can be expressed in terms of family, next, and previous structural relationships.
- the invention only requires one set of base links. Eliminating all other links between components (e.g., direct links) eliminates the need to regenerate those other links when the structure is altered. Furthermore, memory requirements are reduced because multiple sets of links are not stored.
- FIG. 1 is a block diagram of a computer platform suitable for supporting virtual navigators in accordance with the invention.
- FIG. 2 is a diagram of a hierarchy of components in an electronic document.
- FIG. 3A is a diagram showing base links and virtual links.
- FIG. 3B is a diagram showing base links and virtual links.
- FIG. 4 is a flow chart of the context in which a virtual navigator is used.
- FIG. 5 is an illustration of the cascading virtual navigators.
- FIG. 6 is a flow chart of the ordered-list virtual navigator.
- the electronic document publishing system 101 includes one or more virtual navigators 102 on disk or in main memory.
- the computer platform 100 includes a digital computer 104, a display 106, a keyboard 108, a mouse or other pointing device 110, and a mass storage device 112 (e.g., hard disk drive, magneto-optical disk drive, or floppy disk drive).
- the computer 104 includes memory 120, a processor 122, and other customary components, such as, memory bus and peripheral bus (not shown).
- An electronic document 130 contains information stored on a hard disk or other computer-readable medium such as a diskette.
- a human-perceptible version of the electronic document 132 is viewable on the computer display 106 or as a hardcopy printout obtained through operation on the electronic document by a computer program.
- the data structure 200 represents an electronic document.
- the components may be section headings, paragraphs, list items, and so forth.
- component 202 and component 205 may be paragraphs
- components 203 and 206 may be footnotes
- component 204 may be an index entry.
- the electronic document publishing system 101 uses base links to identify the interrelationship of all of the components in the hierarchical structure.
- Solid lines 250-256 between nodes 201-206 in FIG. 2 depict the familial, next, and previous links of the data structure 200.
- the familial links and the next and previous component links may be specified and stored as attribute/value pairs with each component.
- an attribute may be a parent link or a child link and a value may be a pointer to a parent node or child node.
- the system 101 uses virtual navigators 102 (FIG. 1) to locate specific components in the data structure.
- a virtual navigator is a software routine. As the name implies, a virtual navigator identifies an apparent path between components by traversing the data structure through the base links.
- FIG. 3A Shown in FIG. 3A are apparent path 357 and apparent path 358 between footnote component 203, index component 204, and footnote component 206.
- Footnotes 203 and 206 and index component 204 share the characteristic that they are anchored to another component, such as a paragraph, and are both a type of anchor component.
- An anchor virtual navigator produces the virtual link 357 between footnote component 203 and index component 204 by using base link 255, and produces the virtual link 358 between index component 204 and footnote component 206 by using base link 254, base link 252, and base link 256.
- Virtual link 359 is derived from virtual link 357 and virtual link 358.
- the footnote virtual navigator produced virtual link 359 using virtual link 357 and virtual link 358, which the anchor virtual navigator produced.
- the electronic document publishing system 101 provides a virtual navigator for each type of component that needs to be identified.
- virtual navigators 102 include a footnote virtual navigator that locates all footnotes, an ordered-list virtual navigator that locates all ordered lists, a numbered paragraph virtual navigator that locates all numbered paragraphs, and a paragraph virtual navigator that locates all paragraphs.
- a base virtual navigator class is the class from which all other virtual navigator classes are derived and thus all other virtual navigator classes inherit features from the base virtual navigator class.
- Each type of virtual navigator 102 is defined by its own class and each virtual navigator 102 is an object instantiated from that class. All virtual navigators 102 can inherit and use functions defined for any ancestral virtual navigator classes.
- Each virtual navigator 102 uses the base links of the hierarchical data structure or virtual links provided by other virtual navigators and identifies a set of components by recognizing common characteristics shared by the set of components.
- the virtual navigators 102 need not construct or store a data structure on a computer medium or in a computer memory after identifying a set of components.
- a chain of components is discovered dynamically and each component is used for a specific function at the time the component is discovered before the virtual navigator searches for another component in the chain.
- a virtual navigator may be used when an author adds, deletes, moves, or modifies in some way, one or more components in the data structure 200. If the modification affects the way in which other components are numbered, a renumbering routine may be called to renumber affected paragraphs. That routine may use a numbered paragraph virtual navigator, a footnote virtual navigator, or both, to identify components that need renumbering.
- a virtual navigator may be called when a new section heading is inserted between existing section headings in an electronic document.
- the virtual navigator identifies all numbered section headings from Section 3.0 through the end of the electronic document.
- a routine such as the routine that called the virtual navigator, renumbers the heading. Section 3.0 will become 4.0, Section 3.1 will become 4.1, and so on.
- the virtual navigators 102 use protocols based on traversal methods that obtain the parent, next child, previous child, first child, last child, and next and previous components. Each virtual navigator 102 implements at least one traversal routine tailored to a specific type of component and considers the linkage requirements for the component type. For example, a numbered paragraph virtual navigator has three traversal routines, "GetParent”, “GetNext”, and “GetPrev”, that recognize a numbered paragraph component. A paragraph virtual navigator has traversal routines "GetParent”, “GetNext”, “GetPrev”, “GetNextChild”, “GetPrevChild”, “GetFirstChild”, and “GetLastChild” that recognize paragraph components.
- FIG. 4 illustrates the use of a virtual navigator.
- the electronic document is stored as a hierarchical data structure 200 having base structural links (step 410).
- a virtual navigator is called to identify the components.
- a link between identified components is not stored, so the virtual navigator produces a virtual link between components as the components are identified (step 420).
- the virtual navigator derives the virtual link by calling other virtual navigators.
- the virtual navigators use the base links, which may simply be pointers from one component to another, of the hierarchical data structure to identify the particular set of components.
- a virtual navigator identifies a component having a specific characteristic (step 460), which will be discussed.
- the routine that called the virtual navigator may perform an operation using the identified component (step 470). After the operation is performed, the virtual navigator may be called again to search for another component having the specified characteristic.
- the cycle of calling the virtual navigator and performing a function is repeated until the calling routine determines that all components were identified. For example, the calling routine may need the entire hierarchical data structure traversed or only need to identify components in a specific branch.
- virtual navigators 102 call other virtual navigators that identify other types of components. Together, the virtual navigators can traverse the entire hierarchical data structure via the base links. For example, an ordered-list component requires a numbered paragraph component to be its parent component, and a numbered paragraph component requires a paragraph component to be its parent. In this case, an ordered-list virtual navigator calls a numbered paragraph virtual navigator, and the numbered paragraph virtual navigator calls the paragraph virtual navigator.
- Shown in FIG. 5 is a conceptual representation of three virtual navigators interacting with one another to identify ordered-list components using GetNext traversal routines.
- An ordered-list class is derived from a numbered paragraph class and a numbered paragraph class is a class derived from a paragraph class.
- the ordered-list virtual navigator obtains the next ordered-list component (step 460') by sequentially obtaining the next numbered paragraph until an ordered-list component is found (step 520). To obtain the next numbered paragraph, the numbered paragraph virtual navigator sequentially gets the next paragraph until a numbered paragraph is found (step 530). This cascading effect can continue up to the virtual navigator that identifies a component in the class from which all component classes are derived.
- the ordered-list virtual navigator's GetNext traversal routine 460' begins by getting the next numbered paragraph in the structure (step 521).
- the ordered-list virtual navigator's GetNext routine 460' calls the numbered paragraph virtual navigator's GetNext routine 520 (step 521).
- the ordered-list virtual navigator tests whether a numbered paragraph was returned (step 522) and whether the numbered paragraph is an ordered-list component (step 524). If an ordered-list component was returned, the ordered-list virtual navigator returns (step 526) and the calling routine can perform a prescribed function using the ordered-list component. For example, the function may increment a section number.
- the ordered-list virtual navigator continues to search for an ordered-list component. If a numbered paragraph was not returned, the entire structure was traversed and the ordered-list virtual navigator returns to the calling routine (step 526).
- the numbered paragraph virtual navigator's GetNext traversal routine 520 calls the paragraph virtual navigator's GetNext traversal routine 530 (step 531), tests whether a paragraph was returned (step 532), and if a paragraph was returned, tests whether the paragraph is a numbered paragraph (step 534). If the paragraph was not a numbered paragraph, the numbered paragraph virtual navigator's GetNext routine 520 repeats steps 531-534 until a numbered paragraph is returned or the numbered paragraph virtual navigator has traversed the structure.
- the paragraph virtual navigator obtains the next component because a paragraph is derived from a component.
- the paragraph virtual navigator's GetNext routine 530 is called to obtain the next component.
- the paragraph virtual navigator's GetNext routine calls the component virtual navigator's GetNext traversal routine (step 541) and tests whether a component was returned (step 542), and if so, whether the component is a paragraph (step 544). If the component was not a paragraph, the paragraph virtual navigator's GetNext routine repeats steps 541-544 until a paragraph is returned or the paragraph virtual navigator has traversed the structure.
- a virtual navigator can include the functionality of several virtual navigators. Additional object classes (e.g., containers), traversal functions, and navigators may be implemented. Virtual navigators can produce virtual links for linked data structures other than hierarchical data structures. Other functions may be performed after a component is identified, including generating bibliographies, endnotes, tables of contents, and indices.
Abstract
Description
Claims (21)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/995,313 US6006236A (en) | 1997-12-22 | 1997-12-22 | Virtual navigator that produces virtual links at run time for identifying links in an electronic file |
EP98310106A EP0924629A3 (en) | 1997-12-22 | 1998-12-09 | Virtual navigation |
CA002256281A CA2256281A1 (en) | 1997-12-22 | 1998-12-17 | Virtual navigation |
JP10363460A JPH11250107A (en) | 1997-12-22 | 1998-12-21 | Virtual navigation |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/995,313 US6006236A (en) | 1997-12-22 | 1997-12-22 | Virtual navigator that produces virtual links at run time for identifying links in an electronic file |
Publications (1)
Publication Number | Publication Date |
---|---|
US6006236A true US6006236A (en) | 1999-12-21 |
Family
ID=25541652
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/995,313 Expired - Lifetime US6006236A (en) | 1997-12-22 | 1997-12-22 | Virtual navigator that produces virtual links at run time for identifying links in an electronic file |
Country Status (4)
Country | Link |
---|---|
US (1) | US6006236A (en) |
EP (1) | EP0924629A3 (en) |
JP (1) | JPH11250107A (en) |
CA (1) | CA2256281A1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001025950A1 (en) * | 1999-10-05 | 2001-04-12 | Ejasent Inc. | Dynamic symbolic link resolution |
US20030126148A1 (en) * | 2001-11-21 | 2003-07-03 | Amicas, Inc. | System and methods for real-time worklist service |
US6745227B1 (en) * | 2000-07-20 | 2004-06-01 | International Business Machines Corporation | Method, article of manufacture and apparatus for providing browsing information |
US20050044075A1 (en) * | 2003-07-29 | 2005-02-24 | Microsoft Corporation | Method and apparatus for late-binding/dynamic pathname resolution |
US7000186B1 (en) * | 1999-05-03 | 2006-02-14 | Amicas, Inc. | Method and structure for electronically transmitting a text document and linked information |
US20090210356A1 (en) * | 2000-09-12 | 2009-08-20 | Abrams Peter C | Method, system and apparatus for providing pay-per-use distributed computing resources |
US20100306716A1 (en) * | 2009-05-29 | 2010-12-02 | Microsoft Corporation | Extending standard gestures |
US20110239111A1 (en) * | 2010-03-24 | 2011-09-29 | Avaya Inc. | Spell checker interface |
US10204149B1 (en) * | 2015-01-13 | 2019-02-12 | Servicenow, Inc. | Apparatus and method providing flexible hierarchies in database applications |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7509270B1 (en) | 1992-12-09 | 2009-03-24 | Discovery Communications, Inc. | Electronic Book having electronic commerce features |
AU692428B2 (en) | 1992-12-09 | 1998-06-11 | Sedna Patent Services, Llc | Set top terminal for cable television delivery systems |
US7721307B2 (en) | 1992-12-09 | 2010-05-18 | Comcast Ip Holdings I, Llc | Method and apparatus for targeting of interactive virtual objects |
US7168084B1 (en) | 1992-12-09 | 2007-01-23 | Sedna Patent Services, Llc | Method and apparatus for targeting virtual objects |
US7849393B1 (en) | 1992-12-09 | 2010-12-07 | Discovery Communications, Inc. | Electronic book connection to world watch live |
US9286294B2 (en) | 1992-12-09 | 2016-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content suggestion engine |
US7835989B1 (en) | 1992-12-09 | 2010-11-16 | Discovery Communications, Inc. | Electronic book alternative delivery systems |
US8073695B1 (en) | 1992-12-09 | 2011-12-06 | Adrea, LLC | Electronic book with voice emulation features |
US7861166B1 (en) | 1993-12-02 | 2010-12-28 | Discovery Patent Holding, Llc | Resizing document pages to fit available hardware screens |
US8095949B1 (en) | 1993-12-02 | 2012-01-10 | Adrea, LLC | Electronic book with restricted access features |
US7865567B1 (en) | 1993-12-02 | 2011-01-04 | Discovery Patent Holdings, Llc | Virtual on-demand electronic book |
US9053640B1 (en) | 1993-12-02 | 2015-06-09 | Adrea, LLC | Interactive electronic book |
US6789229B1 (en) | 2000-04-19 | 2004-09-07 | Microsoft Corporation | Document pagination based on hard breaks and active formatting tags |
WO2001082120A2 (en) * | 2000-04-19 | 2001-11-01 | Microsoft Corporation | Hypertext link destination index for an electronic document |
US7814408B1 (en) | 2000-04-19 | 2010-10-12 | Microsoft Corporation | Pre-computing and encoding techniques for an electronic document to improve run-time processing |
US7743330B1 (en) | 2000-06-19 | 2010-06-22 | Comcast Ip Holdings I, Llc | Method and apparatus for placing virtual objects |
US7908628B2 (en) | 2001-08-03 | 2011-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content coding and formatting |
US7793326B2 (en) | 2001-08-03 | 2010-09-07 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator |
GB2395300A (en) * | 2002-11-07 | 2004-05-19 | Chasseral Ltd | Providing access to component parts of a document |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5877766A (en) * | 1997-08-15 | 1999-03-02 | International Business Machines Corporation | Multi-node user interface component and method thereof for use in accessing a plurality of linked records |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5694594A (en) * | 1994-11-14 | 1997-12-02 | Chang; Daniel | System for linking hypermedia data objects in accordance with associations of source and destination data objects and similarity threshold without using keywords or link-difining terms |
-
1997
- 1997-12-22 US US08/995,313 patent/US6006236A/en not_active Expired - Lifetime
-
1998
- 1998-12-09 EP EP98310106A patent/EP0924629A3/en not_active Withdrawn
- 1998-12-17 CA CA002256281A patent/CA2256281A1/en not_active Abandoned
- 1998-12-21 JP JP10363460A patent/JPH11250107A/en not_active Withdrawn
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5877766A (en) * | 1997-08-15 | 1999-03-02 | International Business Machines Corporation | Multi-node user interface component and method thereof for use in accessing a plurality of linked records |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7000186B1 (en) * | 1999-05-03 | 2006-02-14 | Amicas, Inc. | Method and structure for electronically transmitting a text document and linked information |
WO2001025950A1 (en) * | 1999-10-05 | 2001-04-12 | Ejasent Inc. | Dynamic symbolic link resolution |
US20040243544A1 (en) * | 1999-10-05 | 2004-12-02 | Hipp Burton A. | Dynamic symbolic link resolution |
US7340444B2 (en) | 1999-10-05 | 2008-03-04 | Symantec Operating Corporation | Dynamic symbolic link resolution |
US6895400B1 (en) | 1999-10-05 | 2005-05-17 | Veritas Operating Corporation | Dynamic symbolic link resolution |
US6745227B1 (en) * | 2000-07-20 | 2004-06-01 | International Business Machines Corporation | Method, article of manufacture and apparatus for providing browsing information |
US8533674B2 (en) | 2000-09-12 | 2013-09-10 | Clouding Ip, Llc | Method, system and apparatus for providing pay-per-use distributed computing resources |
US20090210356A1 (en) * | 2000-09-12 | 2009-08-20 | Abrams Peter C | Method, system and apparatus for providing pay-per-use distributed computing resources |
US9559938B2 (en) | 2000-09-12 | 2017-01-31 | Clouding Corp. | Method, system and apparatus for providing pay-per-use distributed computing resources |
US7756724B2 (en) | 2001-11-21 | 2010-07-13 | Merge Healthcare Incorporated | System and methods for real-time worklist service |
US20030126148A1 (en) * | 2001-11-21 | 2003-07-03 | Amicas, Inc. | System and methods for real-time worklist service |
US20050044075A1 (en) * | 2003-07-29 | 2005-02-24 | Microsoft Corporation | Method and apparatus for late-binding/dynamic pathname resolution |
US20100306716A1 (en) * | 2009-05-29 | 2010-12-02 | Microsoft Corporation | Extending standard gestures |
US20110239111A1 (en) * | 2010-03-24 | 2011-09-29 | Avaya Inc. | Spell checker interface |
US10204149B1 (en) * | 2015-01-13 | 2019-02-12 | Servicenow, Inc. | Apparatus and method providing flexible hierarchies in database applications |
US11170024B2 (en) * | 2015-01-13 | 2021-11-09 | Servicenow, Inc. | Apparatus and method providing flexible hierarchies in database applications |
Also Published As
Publication number | Publication date |
---|---|
EP0924629A3 (en) | 2000-03-15 |
EP0924629A2 (en) | 1999-06-23 |
CA2256281A1 (en) | 1999-06-22 |
JPH11250107A (en) | 1999-09-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6006236A (en) | Virtual navigator that produces virtual links at run time for identifying links in an electronic file | |
US6781609B1 (en) | Technique for flexible inclusion of information items and various media types in a user interface | |
US6353817B1 (en) | Multi-user system for creating and maintaining a medical-decision-making knowledge base | |
US5897636A (en) | Distributed object computer system with hierarchical name space versioning | |
US7376668B2 (en) | Dynamic filtering in a database system | |
US7254784B2 (en) | User-driven menu generation system with multiple submenus | |
US7672960B2 (en) | Performing operations on a set of objects in a database system | |
JP3303926B2 (en) | Structured document classification apparatus and method | |
CA2434081C (en) | Data structures utilizing objects and pointers in the form of a tree structure | |
EP1387297A2 (en) | Translation of object property joins to relational database joins | |
US7668888B2 (en) | Converting object structures for search engines | |
CA2477661C (en) | Hybrid and dynamic representation of data structures | |
EP1556798A1 (en) | Adaptively interfacing with a data repository | |
US7024622B1 (en) | Keeping track of locations in electronic documents | |
US20030225759A1 (en) | Converting expressions to execution plans | |
Gedye et al. | The design and implementation of a version server for computer‐aided design data | |
Jones | Reasoning about interference in an object-based design method | |
Yu et al. | Metadata management system: design and implementation | |
Henrich | Document retrieval facilities for repository-based system development environments | |
Arctur et al. | Comparison and benchmarks for import of VPF geographic data from object-oriented and relational database files | |
Vercoustre | Structured editing—hypertext approach: Cooperation and complementarity | |
Soukup | Organized C: A unified method of handling data in CAD algorithms and databases | |
Knutson et al. | Multiparadigm design of a simple relational database | |
Kim et al. | OOHS: an object-oriented hypermedia system | |
JPH11219372A (en) | Data categorizing device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ADOBE SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YOUNG, JEFFREY E.;REEL/FRAME:008944/0641 Effective date: 19971215 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: ADOBE SYSTEMS INCORPORATED, CALIFORNIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 008944 FRAME: 0641. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:YOUNG, JEFFREY E.;REEL/FRAME:038748/0869 Effective date: 19971215 |